Issue scheduler Dev/Test

Hi,

the basic approach is here: Configure Multiple Environments in TimeXtender Classic | Community

One easy thing to forget is that the account running your scheduler service needs to open the TImeXtender application to set up the repository and ODX connection, assuming you have the environment settings and Server services running.

Thanks for your anwser.

I think i skipped this step:
 

- Assign Each Service User to the Associated Environment's Project Repository

for our dev enviroment.

Is it possible to have one SA account voor two enviroments? So i would like to use it for our dev and test scheduler.

Hi,

each user (including service users) has one config with one repository setting. You can only use the same user if you have separate VMs. As a developer you can change the repository settings to connect to a different environment, but a service account cannot do that.

While there may be creative ways to work around that, that will make your setup more fragile.

Hi Rorry,

Thank you for your anwser. I just executed step:  Assign Each Service User to the Associated Environment's Project Repository

I logged in as a different user (SA_TimeXtender_Test). I made a new scheduler services with this account.

Unfortunately, our Dev Execution Package does not pick up the scheduler service. Below is an example of our services: (2. The new Dev scheduler, which is not being picked up by our dev repo 1. Our scheduler which is being picked up by our test repo).

How can i make our dev execution package pick up the new (2) Dev scheduler?

Thank you for your anwser.

Hi,

I would have a look at Event Viewer and see what happens there - you might want to reach out to your TX Partner if you are a customer as this is probably much easier to solve in a Teams session than in posts 😁

Hi ​@Timmm 

There is also the issue that both environments essentially run the same schedules. It may not be able to start the same executions simultaneously. I would normally make a environment variable and create unique execution packages for each environment to run so they can run at the same time.

You will see if this is the case by looking at the event viewer, like explained above.