Legacy & Upgrades

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

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!

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

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

Hi, I am using TX 20.10.45.64. Can you tell me when support for this version will end?

Dear Sir, The migration Tool is giving me this dialog. Is there anything I can do ? Regards, Arthur ExecuteBulkInsertQueryStep Failed at Step BusinessUnits.Adding to table [dbo].[ODXConnects] Violation of PRIMARY KEY constraint 'PK_ODXConnects'. Cannot insert duplicate key in object 'dbo.ODXConnects'. The duplicate key value is (47f7cfb0-0337-40bc-b508-79172aec7258, 99999999). The statement has been terminated. Details: SQL Server: 'sql-instances-prod-002.database.windows.net' SQL Procedure: '' SQL Line Number: 1 SQL Error Number: 2627 Violation of PRIMARY KEY constraint 'PK_ODXConnects'. Cannot insert duplicate key in object 'dbo.ODXConnects'. The duplicate key value is (47f7cfb0-0337-40bc-b508-79172aec7258, 99999999). ...

Good morning We used the migration tool to upgrade from 20.10 to the saas version.In the comparison of records in the MDW we miss out on the custom data which we use to insert -1 and -2 records. Old situation: After migration: This is very inconvenient as this requires adding all custom data once more.

I did the upgrade to 6675. I can login to the new version but my colleagues get the error below.We are all admins on the vm’s.

Dear Sir, I am working with a client to migrate TX to latest version (from legacy to latest). Now, they want to migrate to a TX Standard license, wich will give you 4 Datawarehouse Instances. Question: Is is possible in this scenario to run 4 Datawarehouse instances in Development and 4 Datawarehouse instances in Production in the latest TX version. All together 8 dwh instances. Is that allowed within the TX Standard license package ? Or do we have to configure 2 dwh instances in Development and 2 dwh in Production to meet the TX Standard license requirements (4 Datawarehouse Instances) ? Hope this makes any sense 😆 Thank you in advance for looking into this. Regards, Arthur

Dear Sir, I am working with a client to migrate TX to latest version (from legacy to latest). Now, they have a lot of Data Exports (CSV files) in their projects, about 50 all together. Client wants to migrate to a TX Standard License, wich will give you 18 Data Product Instances. Question: Does a Data Export (CSV files) count as a Data Product Instance ? Does my client has to move to a TX Premium license ? Or is there an alternative for this. Many thanx for looking into this 😀. Regards, Arthur

Hello, We are still running on TX 18.6.8.64 version and SQL server 2014. Now they want us to upgrade to SQL server 2022 so it makes sense to also upgrade TX. Questions: can I upgrade from 18.6.8.64 to latest TX version in 1 go ? is SQL server 2022 working fine with latest TX version ? Thanks, Ronny

When deploying the project in the PROD environment (through multiple environment transfer) we get the following error.: Source: System.Memory Type: System.IO.FileLoadException Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at System.MemoryExtensions.AsSpan(String text) at Microsoft.Data.LocalDBAPI.GetLocalDbInstanceNameFromServerName(String serverName) at Microsoft.Data.SqlClient.SqlConnectionString..ctor(String connectionString) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous) at Microsoft.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(DbConnectionPoolKey key, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions) at Microsoft.

Looked for this in the documentation, but couldn’t find it - is TimeXtender 20.10.X compatible with Windows Server 2022?

I have setup an Execution Package and am running a number of Perspectives in the order they need to build in the project. I then call 2 External Steps, which are Execution Packages in other TX Projects in the same environment. I am having an issue where when a step fails in the project, the build then continues onto the External steps whereas I would like the entire package to fail. I thought this would be accomplished by selecting the FailPackage action on Failure Handling but it is not working. Do I need to set this up a different way to get this to work? (I have hidden sensitive data in my screenshot)

Dear Sir, I am assisting one of our clients with a TimeXtender upgrade from 20.10.45 to version 6521.1. I gave them a small demo today and showed them the Migration Tool to support the upgrade proces. Then the client asked me if the Migration Tool is capable to Migrate over a 100 TX-projects all at the same time…. Yes, you are reading this correctly, our client has over a 100 TimeXtender projects. So, I am looking for a way to Administrate all of these projects in the Environments Page (see picture) and please advice how to speed up the TX Upgrade proces for our client. If we can’t automate the migration-proces it’s going to be a lot of work. I hope you can shine a light on this one, because I am still in the dark. Thanx in advance. Regards from Amsterdam, Arthur

Any news on SQL Server 2022 Compatibility? Expected release date?

Hi all, Just creating this as a follow up to the thread here. We are currently using TimeXtender 20.10.X, and our infrastructure team is preparing to upgrade to SQL Server 2022. We need to know as a matter of some urgency whether or not this version of TimeXtender is compatible with the most recent version of SQL Server!

Hello Support, We are receiving the following error in one of clients TX environment version 20.1.6.64 when attempting to activate using offline license file. If you need assistance, please submit this with your ticket. License code cannot be empty. Details: License code cannot be empty.Module: timeXtenderSystem.Exception at TimeXtender.DataManager.TXWizardController.DoNext() at TimeXtender.DataManager.TXWizardDialog.btnNext_Click(Object sender, EventArgs e) Time: 2023-09-28 10:45:28UTC: 2023-09-28 14:45:28Title: Discovery Hub 20.1.6.64Application: 20.1.6.64Repository: 20.1.6.64 (in Azure)SQL Server: Microsoft SQL Azure (RTM) - 12.0.2000.8 Sep 18 2023 12:22:37 Copyright (C) 2022 Microsoft Corporation User: freshtxsrvDomain: NAOS: Microsoft Windows Server 2019 DatacenterOS version: Microsoft Windows NT 6.2.9200.0Machine name: xxxxx013CPU count: 2Build: 64 bit

We have multiple TimeXtender projects that use the same databases for their ODX/DSA/MDWs. What is the best way to use tables from one project in another one of the other projects? "Add External SQL Connection" seems to be an option, should this still be used if the table we want to connect to is in the same database?

Good morning, What is the status of the upgrade wizard or tool to migrate TimeXtender to the new version 6xxx? We are waiting for it for quite a long time now and the only status i can find in this community is from 4 month ago that it still is not available yet. Customers are even beginning to think about other data estate solutions becasue of the silence from your side and the uncertainty of when it becomes available. Can we please have more clarity on the timelines regarding this tool?

Dear Sir, Is it possible to migrate from TX version 20.10.40.64 to TX version 6221.1 ? Is there a migration tool/assistant or migration documentation available for this ? Thank you in advance for looking into this. Regards, Arthur