UDPs fail from Workbench but succeed from command prompt
Article ID: 42235
Updated On:
Products
Issue/Introduction
At times, a UDP process fails to execute when running it from Workbench but it works properly when executed from command line on the broker machine. This article does not attempt to solve the problem but to provide a way to diagnose the problem.
Environment
Harvest Software Change Manager v12.x and higher
Cause
The root cause of this problem derives from the way SCM Broker operates when running as a service. Most often, the service runs under local system account on Windows, or a specific "owner" userid on Unix and Linux, and this is what makes difference. When user logs on to the broker machine it uses different account. Therefore, the very same UDP process is being executed under different accounts on the same SCM Broker server machine.
Resolution
In order to diagnose the problem, the UDP process would need to be executed under the same local system account on Windows or the same "owner" userid on Unix and Linux.
For Windows, log on to SCM broker server machine with a valid account and follow these steps:
- Download psexec.exe from the Microsoft Sysinternals Suite. Place it in your C:\ directory
- Open a command prompt window and cd to the root C:\ folder. This places you in the root directory of your drive, where psexec is located.
- Use the following command:
psexec -i -s cmd.exe
where -i is for interactive and -s is for system account. - When the command completes, a cmd shell will be launched. The command "whoami" should return "nt authority\system"
- Run the UDP process. It should fail with the same error message as reported when run from Workbench.
For Unix and Linux, log on to the SCM Broker server machine with the same userid as the one which "owns" the SCM folder and processes. From the command prompt, run the UDP process. It should fail with the same error message as reported when run from Workbench.
Additional Information
Executing a UDP process when it is a stand-alone UDP can be done with the "hudp" command.
Or, you can directly execute the script or command the UDP is configured to run by reviewing the properties of the UDP process in the Harvest Administrator Tool and running that with any corresponding parameters from the psexec command prompt.
More information on troubleshooting problems with UDPs can be found here:
Feedback
