The issue seems to be that if we have a roaming profile for the settings of the program like appsense
It seems that the actual program uses the roaming folder. But the scheduler uses the local folders for settings and executing.

Is this something that could be enhanced. So that we can still use the profile of appsense and have tasks running and picking up the correct virtual path for the tasks variables ?

When I had the settings of appsesnse changed that it should not sync that folder, (which I wouldn’t want as I would like the redundancy) the task got created in the local folder but when it came to running it it couldn’t connect to the database. (sounds like it is using the other settings from the connection properties which I did not stop from going to appsense)

As far as I have seen it is not about access to the directory. It is the path that the program is using to get the credentials and the information to run. Vs the path to the folder that the scheduler is using. They don’t match up.

And sounds to me that this could be solved with a environment path variable or something like that.

As the program itself connects to the db just fine but when the schedular tries to connect it doesn’t find the correct credentials. That is already after having some parts of the program not being synced on appease. So it sounds to be that this is the soul of the issue. Is when users are using a virtual profile the system and the scheduler are not in sync to use always not matter how it is executed it should always go the virtual profile and settings.


It may well be that with one environment variable it should be solved.