Ask questions about Jobs & Executions within TimeXtender
Recently active
Installed data integration and ingest services 7361.1 I cannot start the Timextender execution services also not after I download the config file and replaced it
Hi everyone,We are currently using TimeXtender 20.10.45. After performing a multiple environment transfer from our dev to our test environment, some tables disappear (physical tables, not R or RT tables). I had to create these tables manualy. How is this possible, and could it be related to the version?
Hi all,Our TimeXtender is currently growing and growing, which is a good thing. However, I’m experiencing performance issues during TimeXtender execution and would appreciate guidance on both technical optimization and cost-efficient scaling.As my execution packages become unpredictable regarding execution times, i’m running into issues with PowerBI starting it’s refresh without TX being finished.TimeXtender Version: 7158.1 TX O&DQ Version: 26.1.0.23 ODX: Azure Data Lake Gen2 Execution VM: OS: Windows Server 2022 Datacenter Azure Edition Size: Standard D8s v5 (8 vCPUs, 32 GB RAM) Production Instance: SQL Server Storage Azure SQL Database: Tier: General Purpose (Provisioned) Compute: 2 vCores Storage: 65 GB I’m currently integrating data from about 15 sources, distributed across 5 ERP systems.I played around with execution package threads some time ago and i’m using 12 parallel threads for a while now. This package as a total task count of 540. During execution (mainly data load
Hi Team, Hope you are well!!We have received CVE-2024-21907 Kenna Vulnerability in SUN ODX Servers to upgrade SSIS from version 15.0.4440.1 to version 15.0.4455.2. Could you please confirm whether we can update this to the latest version? The SSIS package used for integration, I am not really sure if this will affect the existing integration.?
Hi,Is there some documentation available for the metadata in the exmon database, on how the DB model works? We would like to create some useful queries for troubleshooting purposes, to find problems in the run.(I found this old thread where the last post asked the same question: Exmon run stats into PowerBI | Community. Don't know if it was answered somewhere else) Thanks! Willem
I am having some issues with the transfer step when loading incremental using direct read. The problem seems to be that the generated procedures do not utilize indices on the underlying tables, resulting in full PK scans for every run.I was especially having problems when running on azure general compute. Switching to hyperscale helped some, but the transfer step still uses approx 40sec scanning ~90m rows causing bottlenecks. When using ADO.NET I could set an index on the incremental rule-field speeding up the search to <1sec.The execution-plan generated by TX looks like this: Here we get a PK index-scan even when there is an index on dw-timestamp.Testing on a subset of the data (~10mill rows): Adding the option(recompile) to the procedure results in the procedure using the dw-timestamp index: Is there a good reason for why these procedures are generated without the recompile flag?Is it something that could be added in a later release?And is there a way to work around this other tha
Hello,TimeXtender 20.10.31.64ODX: 20.10.31We are currently running a database on hyperscale with 12vcores and premium memory optimized hardware. ODX is a data lake.We are running execution packages on 4 threads and we want to reduce our odx transfer times as that is out biggest impact right now.This is an example of a load. I am seeing long ODX transfer times for very small tables that I cant find the cause of or explain.We have alot of small tables (see example below) that is taking 1-3 minutes, while some tables doing data cleansing on 1million + rows is doing it in the same amount of time. See this small table that is 400 rows, no transformations and only 10 columns. I can see we are peaking log io at 100% during certain periods.However, that seems to be during the later parts of the loads and not during odx transfer in the start. Is there any thing that can cause this or possibility to improve it?Thank you,Victor
Hi team, I want to create a new enviroment variable that I used to do in the old version, but with new version it changed. The idea that create a new enviroment varible, and configure on execute package, the variable check dev enviroment or prod enviroment and if it prod the execute package will run. My Version isHow can I do that?
We have recently updated a TimeXtender version from 20.1047 to 20.10.74 and was successful for Development and QA but after updating Production the SSIS Packages are not executing. Development and QA have the same version of SQL as Production. The execution of SSIS Packages is setup through External tasks. The only relevant information I have found so far regarding this issue is here (https://legacysupport.timextender.com/hc/en-us/articles/360000169786-Troubleshooting-Upgrade-Issues) but am not sure how the steps under heading ‘Cannot deploy or execute SSIS packages’ would resolve the issue. Anyone else run into this?
Hi,We are trying to access ODX execution history (backlog / queue / duration / errors) for log analytics purposes.We understand from documentation and release notes that the local ODX backlog (Backlog.sqlite) has been removed / moved in newer ODX versions, and that execution metadata is now handled differently.However, we are currently unable to locate where this information can be accessed programmatically.Additionally, in the TimeXtender Portal, we do not see the menu optionAdmin → Security / Permissions, so we are unable to: verify roles/permissions access or inspect the API for execution data Could you please help clarify: Where ODX execution history (status, start/end time, duration, errors) is stored in newer ODX versions Whether this data is accessible via: the TimeXtender Repository database, and if so, which tables/views are recommended the TimeXtender API, and what permissions are required Why Admin → Security / Permissions is not visible in our portal, and wha
I am struggling with Circular References.Finished executing project 'Discovery_Hub' Execution Package 'Report Booking' Execution failed Start Time : 8/21/2025 11:52:42 AM End Time : 8/21/2025 11:52:42 AM on server: TX-SERVER-DEV -Execute Execution Package Report Booking 'Failed' 'Execute DSA DSA_F.Management Data Cleansing Rules' has a circular relation with the following steps: 'Execute DSA DSA_TX.sub_agrDIM_RentContract Data Cleansing Rules' 'Fill Aggregate Table DSA_TX.sub_agrDIM_RentContract' 'Execute DSA DSA_F.RentContract Data Cleansing Rules'The execution job Report Booking uses DSA_F.Management, but not DSA_TX.sub_agrDim_RentContracts.I have also tried excluding DSA_TX.sub_agrDim_RentContracts from the execution job, but it still fails. What i find strange is that when i run the following tables individually, i do not get any errors:DSA_F.Management DSA_TX.sub_agrDIM_RentContract Also, DSA_TX.sub_agrDIM_RentContract is not the part of Report Booking prespective Only when i ru
Hello,TimeXtender version 20.10I have a customer that previously had only one project (lets call it Project A). However they have now taken out certain parts of that project into new ones (Project B and Project C).Previously to be most effective we could run everything in project A in one execution package. Now with there being 3 projects in total this can’t be done (as far as I know). B + C needs to complete before project A can run. We want to run it as part of one scheduled trigger so the only way I have found to do it is as follows:Project B runs => when done triggers project C package with external step => project C package runs => when done triggers project A package with external step.Most optimally would be for B + C to run at the same time and then trigger A, but we do not want to create a complex custom solution with command prompt/powershell scripts or building logic off the repository which is the only way I can think of achieving that.Anyone have a similar case th
This is the error I am facing when executing any Prepare package (no issue with executing Ingest packages) from the Orchestration portal: Error I have tried resolving the problem with troubleshooting below, but I still get the same error: Suggested troubleshootingAny further suggestions on how to handle the issue?We run Data Integration 6935.1 and Ingest 6935.1 Thanks
When running an execution and it fails in a Tabular, isn't it possible to continue executing the other tables (which are of course not a source for the failing Tabular). Now in our process the execution stops, but the tabular is just a last step for a few tables, not for all other tables.
We have a table which is guarded on deployment and on execution. When we run a manual execute on this table we get the message that this table is guarded, therefore not executed. This table is in a nightly execution and we don't expect this table will be executed because of the guard on execution. But we are dumbfounded that during the nightrun it is executed (and runs in an error). What are we doing wrong?
Hello, I’m looking for a query/view/stored procedure that can be used to query the data lineage / data flow.I would like to have the source to target mapping etc in a report/overview instead of in the GUI.So, I can easily report on the tables that are used to build the table in the next layer. Anyone an idea? Thank you,Gert
Dear Sir,Our client upgraded TX to version 6766.1.Now their scheduled job executions stop working.They are having an issue with thier Scheduled Jobs.Running the jobs manually works fine.Please help, is there a specific Log to check in TX to understand what is causing the issue ?Does an upgrade solve this known issue ?We have released a bug fix for this in 6698.1. Please upgrade, and see the below release notes for reference:TimeXtender Desktop 6698.1Hope to hear from you.Regards,Arthur
Hi,It seems that Exmon/TX Orchestration has hung in some way.Nothing is running in the ODX But in TX Orchestration a job is still running and block everything else in the same package. Is there a way for me to “reset” this manually or is this a support case?I have restarted the ODX service but that did noting.
How can I stop this exmon execution? Restarting or terminating the execution service did not resolve the issue.
TimeXtender Data Integration 6848.1Ingest Service 6848.1 We are experiencing issues with ingest transfer (from ingest instance to prepare instance) in our warehouse, where executions that normally take a couple of minutes get stuck on Ingest Transfer task for hours at a time. This mostly occurs when the table we execute in the prepare instance has mappings to a data source that at the same time executes in the ingest instance (even though that specific table does not execute at that time).Both the Ingest instance and the Prepare instance use SQL Server storage, hosted on the same VM as the data integration service and the ingest service. The Prepare instance uses ADO.net transfer. There are no suspended queries on the SQL Server while the execution is stuck. I’ve also checked perfmon for CPU performance: the CPU averages 80 % and the processor queue length averages 6 (ranges from 0 to 16) during executions that get stuck. Our VM has 4 vCores.The SQL Server has 32 GB maximum server memo
Hi support,I am experiencing some strange behaviour when the Scheduler service wants to start execution packages. The following is happening:the schedule is supposed to start at every full hour. I know that it can take up to 2 minutes for an execution to actually start. Until last monday 18:00 everything was fine. The packages started within 2 minutes and were finished within 10 minutes. After last monday 18:00, we are experiencing a delay in the start. Almost anytime the packages starts, it takes a 12 minutes delay. It also looks like the execution takes way longer than 10 minutes. However, when I look at the gantt chart, I see it still takes up to about 10 minutes to finish. According to the screenshot below it was supposed to start at 03:00, it actually started at 03:12 but if you look closely at the actual times in the gantt chart it only started at 03:34 to finish at 03:42, which is still only 8 minutes. It is TX v20.10.39.64. The database is Azure SQL, sometimes we use 100% CPU
I wanted to clean the jobs in TX Integration version 6822.1. When I deleted the last job, the folder disappeared and i am not able to add a job anymore. anyone has a solution for this issue?
Hello, When you have multiple endpoints configured in the portal and endpoint B uses dynamic values from endpoint A, the the data on demand functionality doesn't work for tables that need endpoint B. Tables derived from A get the data on demand just fine. The exception message says: "OnDemand execution failed for data source '<datasource>' table '<table>' was not executed” I encountered this in a customer environment and then tried to replicate it locally in my sandbox setup. To my surprise, the data on demand worked in my sandbox. However, I had an older version of TX installed. I updated to the latest version on my local laptop and then encountered the exact same problem. This would suggest that it’s a bug in the new version. My version number for TX is 6848.1.
As of this week we encounter several errors in TimeXtender Data Integration (6766.1) and the TimeXtender Serice Configuration. When we add a execution package in deliver instances, deploy the deliver instance, and want to add this execution in the service configuration, we get this error when we try to save:We have access to this folder and can edit this file.Next error that arises is the invalid jobs in our tx data integration:Everything worked correct last several weeks, we didn't change anything. Any idea on how to solve these probles?
Hi all,We are unable to run two execution packages concurrently on the same instance. They are scheduled using Jobs. The packages have no common tables involved. We have made sure to check the other package under “Concurrent packages” under Edit Execution Package (and deploying after).Is running packages concurrently supposed to work when scheduled using Jobs?Will it be supported with Orchestration?Thanks for any input!Version: 6766.1
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.