To homepage To homepage
Solved

ODX task scheduke is not working

  • 13 October 2023
  • 15 replies
  • 102 views
ignacio
Rank
Badge

I am working on a project with 3 environments Dev, UAT, and Prod. I scheduled ODX transfer task to run every 15 minutes.

But any scheduled tasks are not working, I have to run the transfer tasks manually

 

 

Regards 

icon

Best answer by ignacio 26 October 2023, 16:41

View original

15 replies

Bernarddb
Rank
Userlevel 1
Badge

@ignacio It sounds like your scheduler service is not enabled. In this case you would need to activate it and assign a service account to it. The steps how to do this are listed in the below article 
 

https://legacysupport.timextender.com/hc/en-us/articles/360029403391-Configure-the-Scheduler-Service

rory.smith
Rank
Userlevel 5
Badge +7

Hi @ignacio ,

 

in addition to checking that your ODX service is up (for 20.10.x) or your TimeXtender Execution service is up (for the new release), it is useful to check your Event Viewer > Windows Logs > Application for any messages from the service. It may be that there is error reporting there:

 

ignacio
Rank
Badge

Thanks for your help, 

My services are setting that I show you in the image below:

all is up and running

ignacio
Rank
Badge

on event log I have the same issue

 

 

rory.smith
Rank
Userlevel 5
Badge +7

Hi,

 

if you right-click your ODX in the TimeXtender UI and choose View Service Log, do any errors pop up? As far as I know the ODX Server Service handles ODX task execution, and the TimeXtender Scheduler Service handles execution of DSA/MDW/SSL.

Note that in the 20.10.x release you can only have one ODX instance attached to a project, all TX environments will transfer from that ODX into their DSA/MDW layers. This means that you need to be careful to manage the timing of data movements to avoid exhausting the connections available. See this article for more details: 

 

ignacio
Rank
Badge

 

rory.smith
Rank
Userlevel 5
Badge +7

Those errors seem to indicate you are either having an issue connecting to the cloud repository hosted bij TimeXtender for your ODX (in Azure SQL DB), or you are having an issue connecting to one of your own databases.

The complete contents of item 55063 - 55066 are probably worth looking into

ignacio
Rank
Badge

If I execute manually it is working fine. 

ignacio
Rank
Badge

Its works in an on-premise environment. Another error that I saw in the execution history log 

 

 

rory.smith
Rank
Userlevel 5
Badge +7

If you migrated or changed your architecture, you may need to run the ODX Configuration to claim a lock on the ODX. I am assuming you only have one ODX Server and one project linked against it with multiple TX environments.

A manual execution will work because the ODX Server is not communicating with the back-end to trigger scheduled executions and that seems to be at issue here.

 

Christian Hauggaard
Rank
Userlevel 6
Badge +5

Hi @ignacio As Rory mentioned, please try running the ODX Server Configuration, this should restart the ODX Service. Please let us know if this resolves the issue 

ignacio
Rank
Badge

Hi @Christian Hauggaard, I did it and it not working, I opened a ticket on Tx support

ignacio
Rank
Badge

Hi Team, 

 

the odx server is running with AD service account, what permission do I assign to this account? must be part of the administrators’ group?

 

Christian Hauggaard
Rank
Userlevel 6
Badge +5

@ignacio yes it should be part of the Administrator group

ignacio
Rank
Badge

Hi team, 

 

The problem was on the customer TX portal. The environments were changed. the production server had been set as sandbox, for that reason the schedule was not working.

 

 

Reply


Terms and ConditionsCookie settings