WLE 9.0, Cannot run command. A required privilege is not held by the client.

Avatar
CKing
  • updated
I looked at other solutions for this problem but none of them have worked.

I've had WLE running for some time without issue. We recently moved to new web servers so I copied the existing profiles and updated the paths to the log files on the new servers and new schedules were put in place for the new profiles. I can run the profiles manually under my user id or the service account and they run as expected.

When running them under the scheduler, I get the error "Cannot run command. A required privilege is not held by the client." Under Schedule Options, the service account is specified. The scheduler service is also being run under the service account. The service account itself is in AD and is a member of administrators on the WLE server as well as the web servers.

What am I doing wrong?
Replies 4
Avatar
0
Michael
It looks like a permission or network problem. You should try to run the program from a different account (e.g. your account) by specifying it in the schedule settings. You should also check that the program is installed on a local drive, maybe there is a problem with accessing the network when running the program.
Avatar
0
CKing
The program is installed on the local drive of the server. It worked just fine previously when it was accessing the old servers so nothing with the installation itself has changed, only the servers it is now analyzing logs on. The paths to the servers are in UNC format and while logged in with the service account using the same UNC works to access the log files locations.
Avatar
0
Michael
Could you show a screenshot from your schedule log here or send it to support@weblogexpert.com ?
Avatar
0
Michael
Strange, according to the logs it seems that the scheduler cannot run the program, so the error occurs even before the program tries to analyze the logs. It seems that the files in the installation folder have some permissions that doesn't allow the scheduler to run them under the specified account.

You can try to set the scheduler to analyze the sample log. If the same error occurs, it will mean that the problem is really with the program installation. You may try to install the program to a different drive or change the account settings. You can also try to use the Windows Task Scheduler instead of the built-in scheduler, you just need to specify the same command that is shown in the scheduler log (and additional details on the command line mode are available in the program help).