Jobs & Executions

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 DayIs 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

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.1In 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?

how is it possible to have the job stuck with status “waiting”, and if I try to manually run the job, I get the error “job is already queued“i’m running TX version 6675  

HiFollowing an upgrade to the latest version of TimeXtender (6675.2) on one of our customers environments I have since had a problem where some of my scheduled jobs do not run at their scheduled times. When digging about I noticed in the event viewer the following;Rerunning the [TimeXtender Execution Server Configuration 6675.2] tool has since resolved this particular issue but I still have issues with the scheduled jobs.I have also deleted and recreated the problematic jobs but this did not resolve the issue.Running the jobs manually work fine.Please advise on next steps

 Ik have one job running and then started a second job manually.However for some reason the second jobs keep waiting.The both run on the same execution server but why does not it start a second job. Is there a setting which prevents the second job from starting or happens this only if you start multiple jobs manually?  

I’m in version 6590.1I manually started a job. However when I look in the execution log from that job I don’t see an active running job.If I look at the executions then I can see in that log that an execution is runnning.What do I need to do to be able to see the current running job or is it a bug that running jobs are not visible? (then the status ‘Running’  which you can toggle does not make much sense in the ‘view execution log’  window).greetings, Roy

Hi,I activated Trace to text file.I get logging in the file when deploying and executing objects manually. But nothing when running Jobs.Is it possible to use Tracing when running jobs. If so, what have I missed.BRAnders

Hi Team,  I am getting the follwing error while executing the table. Please note i do not have a column named ‘ORDER’. I have no idea what it is refering to.  

I have been playing around with the on-demand load and set up some SQL Sources to use this. When I right-click Execute a table in MDW that loads from an on-demand source (TimeXtender SQL Source, ADO.Net transfer) I do not see any new extract to ODX - so I decided to run a Job: I subsequently right-clicked a Job that reloads my MDW layer and chose Execute. If I try to Execute again I get a message “The job xxx is already queued”, it does not ever seem to Execute the job however.Is there somewhere where I can see the job queue?

Good morningYesterday on the development vm I created a job to be executed on a production vm (which has the related instance marked  in the execution server). However it did not run last night.Is it necessary to log in in TimeXTender desktop in the production vm for the job to become active on that vm?

I have a job that reloads a DWH instance that seems to be stuck on ‘Active’. This job is months old and may have been killed by a VM being shut down automatically.  This job blocks executions with a ‘Job already queued’ error.Is there any way to remove this from the queue?  

Hello,I have a data export object/task. I have created an execution package that runs this export. When I start this execution via a schedule it fails with this error (table does not exist):Execute ReaturnPortefeu:Info:Initialized -Execute ReaturnPortefeuExecute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_Export:Info:Initialized -Execute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_ExportFill Data Export Table 'vw_ReaturnPortefeuille_Export':Error:Failed -Fill Data Export Table 'vw_ReaturnPortefeuille_Export' 'Failed' The table vw_ReaturnPortefeuille_Export does not exist!When I start the execution manually (right click and execute) it works without issue.Execution logThe source table for the export

When choosing a execution job, just a single execution job, it’s grayed out and I’m not able to choose it.it’s deployed and the execution jobs works, when I run it manually.I’m running Timextender version 6590.1

I have set up two completly new enviorments in AZURE.Project name is same in both (i also have tried to append _PROD in Production) Why is this an issue? How do i come around this? 

Hello, I added an execution package to my production instance. I want to add it to a certain job, but that job cannot find my package. In fact, it finds all packages except for the one I just added. How can this be?  

Hello,In Timextender there is a report called ODX Execution Log (see image). I was wondering in which tables the underlying data is stored.My company has a dashboard / chat bot that we use to check on our nightly DWH executions. For this we use the tables ExecutionPackageLogs, ExecutionPackageLogDetails, Projects, etc.I want to expand these reports with data regarding the ODX Transfer Tasks. I checked most of the tables in the metadata database (e.g. ScheduleJobs, ScheduleJobLogs) but I was not able to find it.  

Recently we identified that our Azure SQL Database Backup Costs for our TimeXtender environment are very high, almost even higher then the regular storage costs itself. We now try to minimize these Backup Costs. We already minimized the Backup Retention policies:Now, when analysing some Backup data in the Azure Portal we found that the Log Backup Storage Size is growing the the multiple TeraBytes, even though our PROD database uses around 28GB.  Does anybody know how we can further analyse and minimize these backup costs and data? I foun

I want to start an Execution Package at another server. I have attached the PS1 script. This script is working on the TimeXtender server. But not on our Qlik server. We use the same credentials. Also the credentials have access to the timextender.exe and the shares mentioned in the script on our Qlik server.I think the parameters package name and project name are not recognized when starting the script on an other server. Can you help me out to start an execution package on an other location then the timextender server? 

Hi, We are running Timextender 6536.1 with execution server 6536.1 on on-premise sql server 2019.We seems to be having some strange behaviour with the “Manage schedule” option in with editing a job. Whenever we open the schedule it seems to trigger the job itself. I don't know if others experienced the same. I also don't know if it is related to Timextender 6536.1 since we had to do a lot of updates and configuration changes to the server lately due to a tempdb problem. Below I added a screenshot of the option, it applies to any job not only the odx one I'm highlighting.