At times, a UDP process fails to execute on the server machine but it works properly when executed from command line on the same server machine. This article does not attempt to solve the problem but to provide a way to diagnose the problem.
Article ID: 42235
Updated On:
Products
Issue/Introduction
Issue:
At times, a UDP process fails to execute on the server machine but it works properly when executed from command line on the same server machine. This article does not attempt to solve the problem but to provide a way to diagnose the problem.
The root cause of this problem derives from the way SCM Broker operates running as a service. Most often, the service runs under local system account and it 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.
In order to diagnose the problem, the UDP process would need to be executed under the same local system account.
Environment:
CA Harvest SCM Broker on Windows platform.
Resolution:
1. log on to SCM broker server machine with a valid account
2. follow these steps:
· Download psexec.exe from Sysinternals.
· Place it in your C:\ directory
· Logon as a standard or admin user and use the following command:
cd \
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. Type whoami; it will say 'system"
3. run UDP process. It should fail with the same error message as reported when run by SCM Broker(server side).
Environment
Component:
Feedback
