community 
Authoring Resource driver writing to a text file (or not when in production)
We have an older Resource driver (written in Authoring) that writes a log file to c:\Temp, but doesn't when running AutoLoad in production. I checked on the CS server and where the RM client was running. I get no errors about permissions. That's why I'm trying to write to c:\Temp, open permissions.
This works fine when testing in Authoring client.
Any ideas anyone?
thanks,
Marcus Porterfield
Does the Quali server have an Execution Server installed on the same machine? All commands spawn from Execution Servers, not the Quali server. The Quali server just handles the distribution of tasks to Execution Servers to handle. You can influnce it with Execution Server Selector attributes:
Thanks
Just adding, the Server will keep sending commands to the same execution server once it picked one for a resource, to be able to re-use the driver that is already running there.
When it's a python driver, it takes some time to deploy it and get all of its requirements, so reusing it for next executions can reduce the execution time.
Sometimes, as Chris mentioned, there are other factors to where the driver will get executed, like when using the Execution Server Selector attributes.
Thanks, Chris and Yaniv. Adding the Selector attribute helped.
I was wondering why it seemed to like that one ES better than the others, Yaniv. Now I understand.
Make sure that the folder c:\temp exists already and has permissions for write. When you run it within the Authoring Client, it is running under the permissions of your current user. When it gets executed by the server, it executes with different user permissions.
Chris, both SYSTEM and Administrators have Full Control, I'm running RM as a TestShell user only, there is no associated Windows user for my TS/CS account. On the server what Quali Process should I check for its user?
No, Yaniv I did not check the ES. I did not know that AutoLoad was distributed. Also, I never see a log file so I would expect to see one sometimes. Checking Execution Servers...
thanks,
Marcus
OK found the log file. It is getting put onto the same execution server every time.
Not on the CS server.
So this is being run from AutoLoad in the Resource Manager. Why would it always run on the same execution server and not the CS server?
Marcus
