Jobs & Executions

The scheduler stopped working in production. Yesterday I restarted but it still not running.How can I fix this issue?I have gone through the below document.Scheduled Execution issues - Did it not start, did it fail, or is my execution still running? – TimeXtender SupportOn my computer the recovery options were disabled. 

I want my transfer to MDW job to run only when my ODX transfer task has completed without any errors. What happens sometimes now is that for some reason there is an error in the extraction and some tables are empty, they then get pushed to the MDW and our reports break because the tables are empty. I see that you can use instance variables but I don’t  see that option on my ODX. How can I set this up?

Hello, I would like to set up a jobs on a hourly schedule for the first week of the month (and daily for the rest of the month). Is there a way to allow for more complex scheduling-rules for the Jobs ?

Hi Support, We are experiencing an issue with the prioritization in our execution package. Our trip table is updated with an update script using data from the number_per_trip table.However, the trip table is loaded before the numbers_per_trip table. This results in missing new data in the trip table as the number_per_trip table has not yet been loaded before the script action is executed. We would like to change the loading order of these tables and have tried to do this by adding prioritization. This has no effect on the load whatsoever. I cannot find out what the problem is.Are there any settings blocking the prioritization feature or are we using the feature in the wrong way?See settings below.

Hi,We have a SSL execution that works properly when started from the SSL Executions panel (right click - Execute).But it fails when executed from a Job. The message in the Job log:The log entry in the SSL Execution panel: Version 6221.1 Any ideas?BRAnders

We have a setup with 3 environments (Dev/Test/Prod) running in the legacy version, with a BU Based ODX, DSA, MDW and Several SSLs. Based on a on-prem SQL Server setup. Fairly common I guess.We are multiple developers on a shared project, making changes daily to the project, and therefore needs some QA process. Our target is to have changes and new functionality running on Test for a week before transfering to production. In addition to out centralised BI org, we support the data needs of analysts in the different departments. For this we have established replica databases of ODX and MDW. The analysts can read these replicas without interfering with the centralised data processing (The primary reason for the replicas). Along with the data read access, we have a database the analysist have the rights create objects in (typically views and stored procedures). The analyst environment will only be exposed on our prod platform.We would like to provide a better SLA for

I’ve created a query table that suddenly started to fail. When I press Validate everything is fine.I can even preview the table in the sourceI can also run the query on the source. But when I execute the table, with the same user as above I get this message:  Here’s the query:SELECT        t1.[TRANSACTIONCURRENCYAMOUNT]      ,t1.[ACCOUNTINGCURRENCYAMOUNT]      ,t1.[R

We have 2 jobsJob 1 runs at 11pm and normally runs 1 hour. Job 2 runs at 1am and must run after Job 1 completes, this job usually runs for 6 hours. On occasions Job 1 runs 3 hours and this causes job 2 to miss it start window. How can I adjust the schedule so that Job 2 has 2 criteria?   1-Job 1 completes   2-Has to start after 1am

Hi,We are currently migrating cubes from Power BI report Server ( On-premises) to Power Bi premium.Those cubes are not maintained in TX & refreshes are triggered through a SSIS package called by TX at the end of the ETL execution process.In the new implementation (where the tabular models are still not maintained in TX), we will be using XMLA endpoints & would like to trigger partitions refresh from within TX without using a SSIS package.What would be the best approach to tackle this, taking into account we’re running on an Azure platform (so TX VM and Azure SQL DB for DWH) ?We were thinking of using an ADF pipeline or use REST api calls, but this isn’t supported by TX version 20.10.x.  Any ideas on possible alternatives ? ThanksPeter

When associating instances to an Execution Server in 6221.1 I noticed that the message displaying locked instances has a slight grammar mistake: “The following instances that currently locked by another machine” should probably be something like “The following instances are currently locked by another machine”.   

Hi,We dont always get the notification e-mails when execution fails. Do you know what could be causing?Thanks.Kerem 

We have a Dynamics 365 Finance and Operations system, where we have the Data-lake export running (for over 1 year). THe setup is similar to Josephs sketch solution for the following question:Dynamics 365 F&O Data Lake as a TX source | Community (timextender.com)We have it running quite stable on one of our boxes, but are struggling with stability on a pre-production box.The goal is to use Azure AD Integrated Authentication, and the user running the scheduler has been given access to the Serverless SQL Database (tested in SSMS)First we experienced some missing prerequisites when using Azure AD auth:Execute ODX d365fo_dl.ACOJournalTable_BR ADO.NET Transfer:Error:Failed      -Execute ODX d365fo_dl.ACOJournalTable_BR ADO.NET Transfer 'Failed'          Unable to load adalsql.dll (Authenticati

We are seeing a situation where the next scheduled execution of a package does not start and the event is logged that this is because the previous execution is still running. However, when we closely look at finish times for these executions, the actual finish time is on average 8 minutes before the start of the next execution. I've been told that there can be a delay of a couple of minutes between the task itself actually finishing and the moment the process that executed the task is ended as well. However, 8 minutes and sometimes even up to 13 minutes seems too long.Anybody any ideas on why this occurs and what could be done about it? We're currently running TX version 20.10.25.

When I launch a job directly with the Execute menu option, I get several lines in the execution log without information to know what it is.  

Something it’s missing in this phrase:  

As you can see in the next screenshots, the “View execution log” feature doesn’t works correctly: 

Hi Support, Mount Anvil have a Incremental project to run the incremental load of the finance system data. Changing the incremental execution rule on a table called G/L Budget Entry from the 'Modified At' field to the 'Last Date Modified' field is preventing the execution from running. The 'Modified At' field is in a date\time format and the 'Last Date Modified' field is just a date only format that appears to be causing the execution failure. The error messages caused are below: Finished executing project 'Incremental' Execution Package 'Update Project' Execution failed Start Time : 24/01/2023 16:31:05 End Time : 24/01/2023 16:32:33 on server: MAV01APP01 -Execute Execution Package Update Project 'Failed' -Execute Business Units 'Failed' -Execute Business Unit Business Unit 'Failed' -'One or more errors occurred.' -Execute JetBCStage_I 'Failed' -'One or more errors occu

Hi I’m having problems executing a table from a Cdata source Sharepoint list that has exceeded 5000 rows. Do you have any tips for resolving this issue? Best regardsFrederik

Hi,I have the following setup in my Dev/Prod environments:ODX Shared, all on my live environment DSA / MDW separate for each environmentA daily refresh starts with ODX and on success moves to DSA. So far so good.On the ODX step, there's a Usage condition for Environment (project variable) = ‘Prod’.I added this because I don't want to start 2 refreshes of the same ODX from both Prod&Dev.However, the Dev environment goes straight into the DSA refresh because the ODX ‘starts’ and finishes instantly. Meaning the DSA only gets a few thousand rows from the still-refreshing ODX (largest table has 2000 rows where I'd expect 2million+).Is my assumption correct in using the Usage condition? How can I use the same Execution packages for Dev/Prod while still using the same ODX ?Thanks for any help!

When adding a job I see a checkbox 'Hide objects that can't be added’.  After I uncheck this checkbox I see that my execution schedules for both the data warehouse and the semantic layer can't be added to the job. Could you please tell me what might be causing this?And in general I'd like to know when an object can't be added to a job.

It would be great if in the Multi Environment Transfer Step it would be possible to refresh the Data source as well.Currently I have to add new tables in Dev en Prod environment on a weekly basis (chaning ERP systems).It happens that a table is added in Dev, but that table is not yet avialable in Prod. So when I transfer the project and deploy I do not get a warning that the table does not exists. So after deployment, the schedule will run in morning and it will fail on the missing table.Only after a refresh of the Data source the project recognises the missing table and gives a warning. Now I have to in Dev transfer project and deploy to Prod and then open the Prod environment itself to refresh data source in order to check if all tables are available or not.

I’ve a job like this:The Job’s schedule it’s: When the job finishes the execution log it’s wrong, there’re several tasks, but no one with schedule start type and without details:  

Hi, When executing and deploying a project it does every single table and change, not just the changes I have made since the last deployment. In other projects, it only deploys the selected tables or changes made. But in our biggest project (deployment takes roughly 15 minutes each time) it does all or nothing.Even when in a perspective it still does every other table that exists in the entire project.Other projects don't do this and I can't seem to find the setting that changes this for the big project. Does anyone know how to set this up?Thanks!

The services of 6117.1 worked fine, but after upgrading to 6143.1, I'm not able to start the TimeXtender Execution service. Receive the error:Windows could not start the TimeXtender Execution 6143.1 service on Local ComputerError 1064: An execption occured in the service when handling the control request.In the Event log not more info then the error above.Anyone an idea what is causing this and how to solve this?

Hi all,I've recently implemented Incremental load. Pretty great.I have also built an Execution Package to run each week, where I have added all Incremental tables to the Full load tab.The Execution package sends me a Notification on Success.Both the email, as the Execution History show that the package takes 0 seconds to run. It does run and fires the notification, but nothing actually happens.I would also expect DW_TimeStamp in all Incremental tables to be equal (or at minimum, last run time of Full load).How can I troubleshoot this?Thanks!