Jobs & Executions

Hello, TimeXtender version 20.10 I 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 they

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 troubleshooting Any 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.1 Hope 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 me

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

It seems like we have packages within a process which are stuck on “running”: Exmon DG Desktop If I check the “Process Queue” in the webportal, like this post suggested, I can’t find anything running. Is there another way to stop these packages? Or maybe they are not running at all, the desktop application just says so. We’ve tried to restart the virtual machine where the services are running. We’re running TimeXtender Data Governance 23.3.0.40 (aka Exmon) and TimeXtender Data Integration 6814.1.

Is it possible cancel a Job in some of these status?

All Execution packages with a schedule do not start at the time given. It starts always seconds to minutes later than the schedule indicates. Why doesn't it start according to the schedule? It happens with almost all packages. It also varies by package. The same package can start seconds later or 2 minutes later. For example: in the screenshots you can see that the package always starts later than 05:00 as scheduled.

Hi all, I have a customer that has to deal with an unreliable source system. During transfering specific query tables, it sometimes fails. As there is no retry option on this level, at least we can do right now is to inform the customer that things went wrong. Unfortunately the TimeXtender API does not tell us there is anything wrong with this run. The “State” is 2, and all the child “JobExecutionLogs” child entries below the job itself all have the “Severity” value of 0. Does someone recognize this situation? Anything we can do differently to inform the customer?

Good Day Is there a way to be notified when a scheduled Execution Package does not run on the scheduled time? We had a scheduled package not able to run due to a lock on a table but were not aware as there was no error on the job since it was not able to start. Would like to be made aware of these issues instead of having to check each day to see if scheduled jobs ran. Kerry

I have a generic stored procedure that does some custom post processing based on the table that has just been reloaded (Executed). The stored procedure takes a parameter "TableName". I've created a Script Action that executes the stored procedure. I need this Script Action to run as a Post Step after the last execution step is run for one of several tables. I can create one script action per table with the tablename hardcoded, but I've got a lot of tables to work with and would really prefer do this as a parameter containing the current table name. Is the currently executing table name available in a system parameter somewhere and/or is there a way to create one that can be referenced by a script action?

when running a execution package message The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. version 20.10.46.64 how to solve?

Dear comunity and support, This morning my Job scheduling broke and it does not seem to go online anymore. I'm running the new 6221 version and I have three issues: I have an ‘invalid’ job. I've reset the services and re-added the instances to the Execution server but nothing seems to fix it. At first I was not able to add Data warehouse execution packages to a job, but then I read that you can't schedule ODX and Data warehouse executions in one job. So i stopped the ODX Server service on windows and was then able to add the jobs and run them. This was going fine until I showed my collegues. How can I fix the job? I cannot add Data warehouse executions to my Job. Most of the time I cannot see the packages. I find the packages when I deselect the ‘Hide objects that can't be added’, but I cannot add them. During a brief time I was able to add them, when i stoped the ODX Server Service, but this must have been a fluke as I cannot imagine that I have to stop services to get a certain resul

Hi, I get this error while loading the latest version of a project. I also tried to load an ealier version of the project, but was not allowed to save it as the latest - getting the same error. What should I do? - Gabrielle

Hi, We are facing the (known) error of Execution status Unknown/Running. After a few months of no problems. We are currently on version: 6284.1 In TimeXtender Classic I always fixed this by deleting the log rule in the Repository Administration, but in TimeXtender Data Integrator, this is not possible anymore, causing the next schedules to not execute anymore. I restarted the execution service and deleted the corresponding TimeXtender task via Task manager. Anyone knows if this is enough to let the next execution run succesfull? Or knows how to delete this unknown/runnign execution log rule? Regards, Devin

I have two questions: Why does it take logner for en Execution-job to run when trigged manually as compare to when it runs on schedule? I have an execution job which runs in 8 mins on schedual. When i run it manually it takes 16-25 minutes to run. I have a couple of supernatural keys in my keystore in DSA. There has been a change in a table that creates one of these keys. The question is: When an execution package is run, does it also updates the supernatural key? Lets say my supernatural key is based on ACCOUNT_NR and CLIENT_ID. Someone in the accounts deparment changes the ACCOUNT_NR column. What is the recocmended method to update my supernatural key? If i reset a supernatural keys, is it enough to just deply that key and then execute and deploy the tables that key is used in, or do i have to deploy the whole keystore?