Skip to main content
Solved

Invalid jobs and error on service configuration save

  • January 29, 2025
  • 4 replies
  • 35 views

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?

Best answer by rory.smith

Hi,

the file access error can occur if the user your services run under does not have rights on the file. You can grant all VM users rights to the file in question. This sometimes pops up if you upgrade TDI/TIS and seems to be coupled to policies applied to the VM.

If you add an Execution package to an instance that is already allocated to an ExecutionEngine service and subsequently Deploy or do a “Save as deployed version”, you may need to right-click the Jobs folder in the leftmost column and refresh those before being able to see the package.

View original
Did this topic help you find an answer to your question?

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • January 29, 2025

Hi ​@r.miltenburg 

Try to remove the file mentioned in the error. After this stop both the Execution service and the Ingest service and run the configuration of both.

See if it resolves the issue.


Hi ​@Thomas Lind 

This fix seems to work. But we still face some other problems with adding new executions.

 

I've added a new execution in one of my deliver instances. Deployed the instance, refreshed tx. Opened service configuration to add this execution package. But it isn't visible, so i can't add the execution to a job?


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • January 29, 2025

Hi,

the file access error can occur if the user your services run under does not have rights on the file. You can grant all VM users rights to the file in question. This sometimes pops up if you upgrade TDI/TIS and seems to be coupled to policies applied to the VM.

If you add an Execution package to an instance that is already allocated to an ExecutionEngine service and subsequently Deploy or do a “Save as deployed version”, you may need to right-click the Jobs folder in the leftmost column and refresh those before being able to see the package.


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • January 30, 2025

Hi ​@r.miltenburg 

Yeah as Rory mentions a refresh is needed and save as deployed or forcing a deploy then it should be visible.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings