Ask questions about legacy TimeXtender products and upgrading
Recently active
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 CorporationUser: 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
Hi,I am using legacy TimeXtender 20.10.40.64, and am attempting to set up email notifications for execution package failures.I have been given the information for the destination (email load balancing relay):IP: 150.xx.xx.1Port: 25The destination firewall supposedly has all necessary ports open, although I don’t have direct access to check this. When I test the notification, I receive the error “The SMTP server does not support authentication.” (see the picture below). The app registration on Azure has the following API permissions (all delegated and granted admin consent):Microsoft Graph User.Read Microsoft Graph Mail.Send Microsoft Graph SMTP.Send I haven’t been able to find any information about the error message and what could be causing it. Any help or pointers for troubleshooting this further would be appreciated. Best regards,Pontus
Hi,We have upgraded our TXT environment from 20.10.14 to 20.10.43 last week.Install and repository/existing projects upgrade went well.We can save the project. The new scheduler service runs correctly. Execute action is ok. However, we encounter an exception during table deployment task (BU/STAGE or DWH table):Failed to connect to server XXX (Azure Managed Instance)Method not found: 'System.Net.Http.Headers.HttpResponseHeaders Microsoft.Identity.Client.MsalServiceException.get_Headers()'. The connection settings (Repository/STAGE/DWH) seem correct (positive test connection): same Azure Managed Instance.We have checked the .NET framework version - it seems recent 4.8.03761Thanks for your help. Best regardsMatthieu
Hello TimeXtender, Yesterday we've upgraded our PROD environment from 20.10.25 to 20.10.43. Install went fine and upgrading of the repository as well. However, when we went to validate the upgrade by carrying out a deploy and execute of an arbitrary table in the DSA we received the following error message: The type initializer for 'Microsoft.Data.SqlClient.InOutOfProcHelper' threw an exception.Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Do you have any experience with this error message? Might be good to note that we first carried out the upgrade on our DEV environment and we did not receive the same error message there. We've also tried to rule out that the error was table specific by carrying out a deploy & execute on different tables/layers, but the error persisted. Best regards, Luuk Bouman
We are still using the legacy version of TimeXtender while we are waiting for the migration tool. Our new Data Engineer needs to learn how to use this version of Timextender (20.10.40.64) and he does this by following the old Discovery Hub training courses.https://timextender.teachable.com/courses/enrolled/240391https://timextender.teachable.com/courses/enrolled/217568https://timextender.teachable.com/courses/enrolled/259790 However the links to the videos in these courses are no longer valid, for example https://youtu.be/DuS0VvGZ1aE in the course Follow Along: Working With Multiple Users - 4:15 | TimeXtender Academy (teachable.com). Are these videos available somewhere else so he can follow the legacy training courses properly?
Hi,We wonder if someone of you already ran into this issue, and perhaps have an idea on how to solve it ?Setup :TX 20.10.38 using Azure SQL DB for DWH and ADLS gen2 for ODX Server. ADF used to load data from ODX Server into DSA. All databases have private endpoint, so SelfHosted Integration Runtime is used by ADF.Issue :From time to time (random - not always on the same tables - for both incremental and full load tables) we notice that the ADF pipeline takes the normal amount of time to load data from ODX to DSA R-table. However the cleansing takes 0 (zero) seconds and the record count log reports 0 (zero) records in the R-table. ADF nor TimeXtender Execution report an error.In the ODX Service Log we often notice this error : Failed to encrypt sub-resource payload… (not on exact the same moment as the execution - so not sure it has something to do with the issue)Work-around : ADO.netWe had a simular issue last year and started using ADO.net to load data from ODX Server into DSA. We
Hello Im trying to upgrade from Discovery Hub 17.12.10.64 to Timextender 20.10.41When I try to configure the ODX, Im asked to provide a client secret from portal.timextender.com/odx. However I cannot login on that page using my credentials Furtheremore, Im following this guide Upgrade ODX and TimeXtender from a previous version – TimeXtender Support , but is there anything I should be aware of, when upgrading such an old version?
There's loads of documentation about AAS and PowerBI Premium tabular models being mostly identical in use. Currently we are using 2 expensive AAS servers to host our development and testing semantic models. Transferring these 2 environments to a PPU environment within PowerBI would save allot of money. Within the current version of TimeXtender there is a separate option to select a Premium Tabular model instead of AAS. This is something the legacy version does not have. But why would TimeXtender need to know the difference. In working with either Premium or AAS their XMLA connection is exactly the same. Setting a migration from AAS to Premium and then simply exchanging the links within the environment properties seems like a simple enough plan. As i found in the following link the important part would be having an updated library to do this data transfer. https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=azure-analysis-services-currentOther than this i don't see
v20.10.36.64When setting up the relation between two tables, is there a way to use a project variable as the “Value” when the “Fixed Value” option is used?
Hi,Can we only download TX 20.10.x on the Legacy support page?https://legacysupport.timextender.com/hc/en-usI can't find it through the new Support.timextender.com site under Product updates, there I can just find the new SaaS solution.Thanks.
Hi all,When deploying our tabular model/endpoint (Azure Analysis Services), we get a strange error: "This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row".In the error message we don't see which table or row this relates to and we don't know if this error relates to a datawarehouse table or a repository table. All our datawarehouse tables in this tabular model contain data and 'look good'. In addition, this error occurs in one of our environments and not in the other environments. Has anyone experience with this error? Any thought on how we can debug this one?Thanks.
v20.10.36.64Hi,I have set up a simple script action as follows to set the LAST_CHANGE_DATETIME column to the ENTRY_DATETIME value if it is NULL.Script action This works fine when selecting from the table in SSMS:SSMS results using same script actionThe script is set as a pre-script to the ADO.NET transfer on the execute step, but when I execute the table, the following error appears:Incorrect syntax near 'LAST_CHANGE_DATETIME'.Can I implement this simple script action as a pre-script? The idea is that I can then use a fully populated LAST_CHANGE_DATETIME column for incremental loads on my ledger table.Thanks,Richard
I have used the data export tool to export to .csv files. However I can not do it straight from the Business Unit. Is that a feature that can be added? Or maybe not included in client license. The client wants a few tables from source to be transfered to Azure Data Lake as a csv file and do some tranformation there.
We have an upgraded MS Dynamics 365 environment, from which we publish to an Azure SQL database. When I attempt to attach an existing project to it to synchronize data source (using a SQL data source connector as the project normally does) I can connect with a test connect, but then after building the selection tree, TimeXtender throws the error “The given value of type String from the data source cannot be converted to type nvarchar of the specified target column. String or binary data would be truncated." Since it isn’t yet part of project execution but rather a TimeXtender comparison operation, I’m somewhat befuddled as to how to proceed. I’m not sure if this belongs in data sources or desktop, so took a guess on placement.
Hi.I want to create a global Data Source Database for a multiple Text File import. But there seems to be no available type?Do i just use the single text file option?
Once in a while my scheduled job does not finish without an error. It just stops doing anything.My event log states that around the time my job stopped running, both the server and the scheduler started.I do not find anything in the logs where it says the server and scheduler stopped running, so I have no idea why they restarted.Would the server/scheduler being down explain why the job stops running rather than failing and providing an error?Does anybody experience the same? Any ideas where I can find more information on why the server/scheduler stopped or restarted? And possibly how I can prevent this of course?
We would like to possibly switch from ADO.NET to SSIS. At the moment, both the TX application (ODX is not being used) and the SQL server are on the same box using ADO.NET. We want to split off TX to its own server and use SSIS instead of ADO.NET. Has anybody done this and can share the high level steps? Or even how you think it might be best accomplished? Specifically, once the application server is up and running with all the pertinent software, how would one make this transition?
I just upgraded from Discovery Hub 20.1.6.64 to TimeXtender 20.10.26.64and upgraded the repository. Everything works well with the deploy and execute, but when I try to restart the service, I get an error in the event log. Service cannot be started. System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 Could someone please assist?
I am following the TimeXtender Basics course and at a certain point I am asked to create a new Global Database (specifically Datawarehouse) through the following steps:Create Global Database for DSAIn the Tools menu select Environment Properties Click New Global Database Type in DSA in the Name box Select Data Warehouse in the Type drop-down list and click OK Click the settings text box Type localhost in the Server text box Type TX_DSA_DEV in the Catalog text box Right click the settings text box, select Create Database and click OK, when notified of successful creationHowever at step 7. I get stuck as there is no catalog row. Does someone know how to fix this issue? I'm on version 20.10.23.64
Hello,I tried creating a new TX Dictionary project on our Tableau Server, but I'm running into some problems with opening the Tableau-file and replacing the data source.First of all, the stept to replace the datasource aren't up-to-date anymore with the new Tableau Desktop versions. In the new versions you have to open the new datasource before you can replace it. Not a big problem, just a mention so you can possibly change this.The problems come when I replaced the datasource. All sheets are empty and a few fields keep giving an error. The error states that the field doesn't exist in the database.I'll assume the missing fields are the reason for the empty sheets, as you can see here below:Can you help me with this problem?Kind regards,Damien van Kan
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.