General Q&A

Hi. Is it possible to move my current community account to my new e-mail address? I could not find anywhere to update this on my profile.

Recently we have been running into big problems with our production repository database becoming completely unresponsive after completing an environment transfer, actually leading to scheduled executions not starting the following night. It has happened twice in the last two weeks but never before during the 3 years that we’ve been working with TX. The issue is seemingly resolved having switched to a vCore model on the production repository, but we are at a loss as to the root cause of this problem. We have of course read all the relevant knowledge base articles/community discussions that talk about why the repository may become generally slower over time (execution logs have been deleted, yes) -however, for us it has not been gradually deteriorating but suddenly. Also, we believe our projects are not that big (see below) to warrant the export-import procedure. Setup TX version 20.10.25.64 Multiple environment setup (Dev + Prod), TX running on single Azure VM and all databases are Azur

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, 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?

Hi! I have just installed TX 20.10.66.64 on a new server for a customer and following the steps of the “Configure Multiple Environments” article. Created a service account and setup the Windows Services through TimeXtender. Logged in on TimeXtender with the Service account for prod and linked it to the prod repository (which is on a different server). Now I'm trying to setup the production environment in TimeXtender. I opened Environment properties and clicked New Environment, gave it a name and filled in the address of the server (and instance) containing the prod repository. Filled in the ports. When clicking OK to close the Add Environment window I almost immediately get the error from the printscreen below: Has anyone come across this before?

Hi! I am currently investigating something for a customer of ours. They just switched their Telephony system to Teams Telephone and want to use a dashboard in Power BI to show the current queue of callers. The data can be extracted from Teams Telephone by MS Graph API. This customer has a TimeXtender environment in production, so adding a new datasource (TimeXtender REST connection to the MS Graph API) will not be the hardest part. But, they want the dashboard to show (near) real-time data. Is it possible for TimeXtender to take in data, prepare it for the report and refresh the semantic layer within seconds and then start again? I am aware MS have created a plugin for Teams to show these numbers in a dashboard of their own in the application, but our customer would like to know if it is possible to create this in Power BI using TimeXtender. Kind regards, Richard

Hi, I am trying to set up a new Ingest Instance with Microsoft Fabric Storage. I am following Christian Hauggaard’s guide for Integrating TimeXtender Data Integration with Microsoft Fabric, but i am stuck on step 2. Create Storage for Ingest Instance. (Link: Fabric Lakehouse Ingest Instance storage (Public Preview) | Community) The guide describes using a non-MFA user when authenticating, but i am stuck using my Azure AD user with MFA enabled. When i try to create storage in TimeXtender Data Integration i get the attached error message, and when i check the sign-in logs for my app registration in Azure there is an ‘interrupted’ sign-in attempt with error code 50076 (User needs to perform multi-factor authentication). Error message details Is there any way to resolve this issue with the current MFA-requirement on my user?

Hi, I'm having some issues with renaming a table. There's a an incremental table in my MDW, containing 60 million rows. I'm trying to rename the table whilst keeping all data.I've tried several combinations (deploy, deploy & execute, deploy with differential deployment unchecked, etc.). But it keeps throwing the same error during the "Deploy Direct Read Transfer" stage of the deployment. In SSMS I can see that the table was in fact renamed correctly. The error is: fact_example to fact_example_oldInvalid object name 'mdw.fact_example'. Yes, I know that's an invalid object name because you've just renamed that table... At some stage I actually managed to lose all data which is quite unfortunate. There are a few supernatural key fields, there is a clustered columnstore index, no (custom) table inserts, no relations. Any ideas what could be causing this? I've got no idea where to look.Version is 20.10.66.

Hi! A customer I am working for recently did an upgrade to TX Classic 20.10.66.64. After switching all data sources from ODX to Business Units not all datatypes are set correctly in TimeXtender. Especially the columns containing the datatype “time(7)”. When you check the fields in the new datasource the datatype for that field is shown as unknown, while sql recognizes the source as a “time(7)” field. We were able to resolve this with the overrule datatype option, but would like to have it investigated to check if this is desirable. TimeXtender: SSMS: Datasource: Any Source ADO.net Dataprovider: SQLClient Data Provider (.Net Framework data provider)

Hi Just installed TX 20.10.66.64 on a new server for a customer and connected to the server where the txrepository is kept, all without any problems. Now I need to setup the Prod environment and therefore start the service I created for that, but this keeps showing an error message: From the application log of the server:

Dear Customers,We would like to update you regarding the potential impact of CVE-2025-30065, a recently disclosed vulnerability affecting certain versions of the Apache Parquet library. Our product uses Parquet.Net for reading and writing Parquet files. This library is implemented in .NET and is not affected by CVE-2025-30065, which specifically targets the parquet-avro module in the Apache Parquet Java ecosystem. Therefore, there is no exposure to this vulnerability within the core functionality of our application. Microsoft Fabric and Azure Data Factory We initially flagged potential risk in those environments based on observations that Microsoft Fabric and Azure Data Factory (ADF) make use of Apache Parquet version 1.13.1, which is one of the versions known to be vulnerable to CVE-2025-30065. However, we have since received official clarification from Microsoft confirming: They do not ship the parquet-avro module. The CVE does not apply to their runtime. This significantly reduces t

Hi! A customer I am working for has been wanting to upgrade their TimeXtender version to the new V25 / Classic. According to this article: Important information regarding TimeXtender 20.10 (V20), TimeXtender Data Integration (TDI), and TimeXtender Classic (V25 / Classic) the release would be end of march. But until now there has been no update on this new version. Would it be possible to get an update on the release date so they can decide which version to upgrade to?

is it possible, as the title says .. to Copy and entire semantic layer to a new semantic layer, or copy the exsisting tables with relations from 1 semantic layer to a new one ?

Hi, I am working with TimeXtender and have an SSAS tabular on-premise on a virtual machine as the endpoint. I want to publish my Power BI dashboard to the Power BI service. However, when I attempt to publish, I receive a message indicating that the connection to the data source is broken. How can I resolve this issue? We do not have Power BI Premium licenses, hence the use of SSAS. Looking forward to your response. Best regards, Dean

Hi, I'’ m upgrading from 20.10.52 to 20.10.63 and are waiting for a long time (over a hour) message “please wait while the application is preparing for first use” and after a while a message “installer not reponding “ with a retry or cancel. Is this normal behaviour?

I am currently working with TimeXtender Data Integration and would like to leverage the tables created there within TimeXtender Data Quality. Could someone provide a detailed explanation or step-by-step guide on how to achieve this integration?

Hi, our version is 20.10.52.64. Noticed the the Cdata connectors are disappeared for new connections, so want to upgrade to newest version. According to me that is 20.10.63.64 if I'm correct. Are there things to take into account when upgrading to this version? Can I just run the upgrade script from my version to this newest version? Also, is this new version a good version if i eventually want to upgrade to TimeXtender Saas in the future? I've read Download TimeXtender 20.10 – TimeXtender Support, so i know from the "backlog issue” Just want to get confirmed i'm doing the right steps, things, version upgrade :-) thanks!

At one point you had a link to describe how to write a custom data source so it will show up in the list of Custom Data Sources in TX. Can you link me to that documentation?

Hi, I have a virtual machine that is currently hosting the ODX service and I would like to get my local machine up and running with TX desktop. I have installed the application but am getting an error that can be found below. I have looked through the documentation regarding this but it seems that the legacy documenation is all I can find with anything relevant. In the screen shots it is asking to review settings in the ODX tab and the Project repository tab which are non existent in the latest TX version I am using. I only see General and Customer editors when looking at Tools>options. ERROR> A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) Details: SQL Server: 'sql-instances-prod.database.windows.net'SQL Error Number: 64

I have a table (table A) with a lookup field from table B (using the default relation between A and B). This works fine. Table B is then renamed because of a spelling error, deployed and executed. Good. Table A still seems to be OK: the relationship between A and B looks fine and the data cleansing procedure (Advanced -> Customize Code -> Data Cleansing Procedure) contains table B with its newly updated name. However, table A won't execute because the deployed version of the data cleansing procedure still references table B's old name. The simple fix is to force a deployment of table A, but I think TimeXtender should have noticed that a deployment was needed (red table name). Seems like a bug to me. Legacy version 20.10.50.64 Details: SQL Server: 'my-mdw-database.example.com' SQL Procedure: 'MDW_TR.usp_table_A_Clean' SQL Line Number: 65 SQL Error Number: 208 Invalid object name 'MDW.table_B_old_name'.

Dear Sir, One of our customers wants to keep working with TX classic into the future. Question: Till when is the 20.10 TimeXtender Classic supported ? Customers have to migratie sooner of later right ? Is there a deadline ? Or is TimeXtender Classic still supported for say the next 10 years ? Hope you can shine a light on this. 😀 Regards, Arthur

We are suddenly having issues with opening last saved project in TimeXtender. The error says: An error occurred while fetching data from the database.Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. Location: Table: SelectionRuleFieldsForeignKeyConstraint DataFields_SelectionRuleFields requires the child key values (5b2c48b9-abad-4a3b-a9b2-002fedfc582a) to exist in the parent table.. We have tried to go back to the project that we saved before the lastest one. We are able to open that it not able to save it. The errror says: An error occurred while saving the project to the database. An error occurred while fetching data from the database.Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. Location: Table: SelectionRuleFieldsForeignKeyConstraint DataFields_SelectionRuleFields requires the child key values (5b2c48b9-abad-4a3b-a9b2-002fedfc582a) to exist

Hello TimeXtender Support, We are looking to upgrade the ODX server at the customer. Currently the ODX service is installed on the PROD server. We first want to install the new version of the ODX service on the DEV, basically run a sandbox project to ensure everything is running fine and then upgrade the ODX service on PROD. Now, I've been told by Rory that there is a change that running a newer version of the ODX service will impact the metadata in the ODX repository in a way that is irreversible. I want to make sure that we can first try the new version of the ODX service in the DEV environment without impacting the ODX repository, so we can go back to the previous situation if anything problematic pops up and don't impact PROD. My question is: can we safely install a sandbox version of the ODX service on the DEV server and have it call home without irreversibly changing our ODX repository between these two versions? ODX Service 20.10.37>ODX Service 20.10.57 Hilsen, Luuk Bouman

In the TimeXtender Classic training, I only see 4 modules, while Peter Jensen (element61) sees 5 modules. See below screenshots. We are wondering why Peter has a module named ‘Business units’ that I don’t see.