Hi, Is there a way to access an ODX that went offline after upgrading TX? Or would you need to install the ODX version that is equal to the new TX version?
Hi! This week I have been trying to upgrade a client of ours to TX 20.10.66.64 and in this process we have come quite far. We are able to deploy & execute all layers in a project, except for the Semantic layer. The error message TX shows us is below: The account that is mentioned in the parts that I have blurred out is an account that has never existed, nor is mentioned in any connection in the project. The databases used in this semantic layer are all on a SQL server that worked correctly before the upgrade of TX. Note: TX was not only upgraded, but also installed on a different application server. Created a new endpoint in the existing semantic layer, when trying to deploy and execute this, same error message appeared. Deploy steps all succeeded, it fails on the execution step. Has someone seen this error message or experienced this before?
Hello, TimeXtender 20.10.51 I’m looking for support with an issue we’re experiencing where execution packages are running but no tasks are being completed while causing 100% usage on the repository. After deploying to production, we ran a package manually and noticed it not proceed past the above step. The “current tasks completed” stayed at 0, and no data was being loaded, even after waiting up to 30 minutes. We tried running it multiple times, but nothing changed. Running individual tables worked fine. We checked the SQL database usage for the DSA to be sure, and it wasn't being affected—no data was loading as expected. While troubleshooting, we found that the repository (a standard 100 DTU Azure SQL database) was hitting 100% data IO and DTU usage. One query, in particular, was using nearly all the available resources. It was this query: (@ObjectId uniqueidentifier)SELECT [StepId], AVG(DATEDIFF(s, [Start], [End])) AS [AvgSeconds] FROM [dbo].[ExecutionPackageLogDetails] WHERE [Object
Hi, We've updatet our Data Integration version from 6766.1 to 6963.1. Which means we had to update our outdated providers. So we followed the steps mentioned in this post Change data source provider | Community (timextender.com). This results in an error when we try to full load changed data source. It keeps giving is the error: “The schema …. already exists on the SQL storage and cannot be used” Which actually means we can’t update our providers/ data sources. We have to create new ones en have to map all our tables in de odx. Anyone else facing this problem and have a solution for this?
I'm using dynamic values function in the TX REST connector 9.1.0.0. I use id's from another endpoint to loop through in my second endpoint path. This works well when I use “From Endpoint Table” but now I want to add a filter to only get the id's with a flag “hasresponse=true”. I've read the page but I still get an error with my Endpoint query. “No such table” the error message says. I've tried several things like adding a schema. But all with the same response. Is there something wrong with my syntax? Error:
2 likes
1 like
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.