Hi @Bitmetric_Maarten
Are you on the newest release?
Do you have both prod and dev versions of the execution package on the dev instance?
Hi Thomas,
We are on 6221.1
The funny thing is that the Execution packages work just fine. It are the ODX transfer jobs which give the error.
Hi @Bitmetric_Maarten
We had a thing about this issue in that version, hence why I asked about it.
It might be this issue
18688: Jobs sometimes select the wrong instance when using copy instances
Fixed an issue with Jobs sometimes using the wrong instance in a "copy instance" setup. The execution packages in the job would use the first available instance across the copied instances when creating the job.
So if you upgrade to the newest release and see if it still behaves like this it would be something to look at.
@Bitmetric_Maarten
It is actually more simple.
- Install the two programs (ODX and TX)
- Disable ODX and Execution services or just uninstall them.
- Run the ODX Server Configuration and then the Execution Configuration.
- Open new version of TX and log in.
- Open each instance and click OK to any suggested updates.
The only thing I could think of regarding 6221 to 6346, is that the Jobs area may have some issues.
Like you may have to recreate them.