Create process error: Error #1314: A required privilege is not held by the client.

Note: User account running RunAs must be assigned "Act as part of the operation system" rights.
User account used to run the process must be assigned "Logon as a batch job" rights.

I have checked the Local Admin Policy and the user has been granted both rights as well as
Log on Locally.

Permissions are cashed. If you changed them recently restart the server or flush them reload them using Local Security Policy tool.

: Create process error: Error #1314: A required privilege is not held by the
: client.

: Note: User account running RunAs must be assigned "Act as part of the
: operation system" rights.
: User account used to run the process must be assigned "Logon as a batch
: job" rights.

: I have checked the Local Admin Policy and the user has been granted both
: rights as well as
: Log on Locally.

Prior to posting here, the server was restated numerous times as well as verifing the
permissions after the restart.

: Permissions are cashed. If you changed them recently restart the server or
: flush them reload them using Local Security Policy tool.

Do you specify user in domain\user format or without domain?
If you want to run it as a local user you should use either ".\user" or "computer_name\user" without quotes as the user name.

You can always test this stuff by manually running runas.exe from the 24x7 home dir. If it works from DOS prompt it will work from 24x7 job.
For example, "runas.exe .\administrator password notepad.exe"

: Prior to posting here, the server was restated numerous times as well as
: verifing the
: permissions after the restart.

I am using domain/user... we are not using local users

Also we have everything set as you have speficied and do not
need to have your condescending tone of your last paragaraph
as far as we can tell your software isn't working correctly.

Now can you provide assistance or NOT.

: Do you specify user in domain\user format or without domain?
: If you want to run it as a local user you should use either
: ".\user" or "computer_name\user" without quotes as the
: user name.

: You can always test this stuff by manually running runas.exe from the 24x7
: home dir. If it works from DOS prompt it will work from 24x7 job.
: For example, "runas.exe .\administrator password notepad.exe"

Please accept my apologies if I offended you in any way. There is nothing personal.

In the first message I suggested to restart the server.

In the second message I suggested to verify you specify name in user/domain format and test it using runas.exe.

Please enlighten me on what was offensive there? The suggestion to restart the server or try runas.exe?

Now, back to business, you mentioned first that you gave these permissions locally, then you said that you are using domain user for the run as. May I suggest that you give the required privileges to the domain user?

: I am using domain/user... we are not using local users

: Also we have everything set as you have speficied and do not
: need to have your condescending tone of your last paragaraph
: as far as we can tell your software isn't working correctly.

: Now can you provide assistance or NOT.

The issue was the way you suggested to use the runas.exe... Maybe it is just
the number of issues we have been having with this product...

Anyway lets just get this fixed.

I will be elevating this to the actual Network Group here tomorrow, so
maybe they will be better at this than I.

: Please accept my apologies if I offended you in any way. There is nothing
: personal.

: In the first message I suggested to restart the server.

: In the second message I suggested to verify you specify name in user/domain
: format and test it using runas.exe.

: Please enlighten me on what was offensive there? The suggestion to restart
: the server or try runas.exe?

: Now, back to business, you mentioned first that you gave these permissions
: locally, then you said that you are using domain user for the run as. May
: I suggest that you give the required privileges to the domain user?

Please tell us about your other issues and we will try to find appropriate solutions for them. The purpose of this message board is to help, answer questions and provide design suggestions.

In regard to the permissions issue, you can use the Active Directory management tools to give the necessary permissions to the domain users. The basic procedure is the same as in the Local Security Policy applet. Please ensure you set right permissions for both users - the scheduler runner and the job runner. As with local changes the server should be either restarted or logged off/on

: The issue was the way you suggested to use the runas.exe... Maybe it is just
: the number of issues we have been having with this product...

: Anyway lets just get this fixed.

: I will be elevating this to the actual Network Group here tomorrow, so
: maybe they will be better at this than I.

I have had our Network engineers double check the local security polices that
I have applied and they have verified that all are set correctly.

When we use the Microsoft RunAS everything works correctly, howeverm with the
version distributed with 24x7 it keeps indicating that we are missing the
permissions.

Any other ideas?

: Please tell us about your other issues and we will try to find appropriate
: solutions for them. The purpose of this message board is to help, answer
: questions and provide design suggestions.

: In regard to the permissions issue, you can use the Active Directory
: management tools to give the necessary permissions to the domain users.
: The basic procedure is the same as in the Local Security Policy applet.
: Please ensure you set right permissions for both users - the scheduler
: runner and the job runner. As with local changes the server should be
: either restarted or logged off/on

Can you confirm that permissions have been given to the domain account, which you are trying to use for the job, not to the local one and this is done using Active Directory?

I mean that permissions are not set in the "local security polices," but on the domain level.
In other words if the accounts are local to the machine (please don't confuse them with domain accounts) the local policies must be set, if the accounts are domain accounts then domain user accounts must be set.

Can you provide an example of what you are trying with the command line RunAs.exe and what you are getting back as the error or status messages?

PS. I guarantee that after the right things get set in the right place you will see RunAs working properly.

: I have had our Network engineers double check the local security polices that
: I have applied and they have verified that all are set correctly.

: When we use the Microsoft RunAS everything works correctly, howeverm with the
: version distributed with 24x7 it keeps indicating that we are missing the
: permissions.

: Any other ideas?

We have done as you asked this was applied thru a GPO for the user.

Still no luck.

: Can you confirm that permissions have been given to the domain account, which
: you are trying to use for the job, not to the local one and this is done
: using Active Directory?

: I mean that permissions are not set in the "local security
: polices," but on the domain level.
: In other words if the accounts are local to the machine (please don't confuse
: them with domain accounts) the local policies must be set, if the accounts
: are domain accounts then domain user accounts must be set.

: Can you provide an example of what you are trying with the command line
: RunAs.exe and what you are getting back as the error or status messages?

: PS. I guarantee that after the right things get set in the right place you
: will see RunAs working properly.

Please describe in detail which accounts are used for the scheduler and for the job and how they are entered. An example using runsas.exe and notepad would also welcomed.

: We have done as you asked this was applied thru a GPO for the user.

: Still no luck.