This issue occurs if all the following conditions are true:
* You run the batch job on a Windows Server 2003-based member server.
* The batch job runs as a non-interactive process.
* The batch job is configured to run under the context of an account that is not a member of the Administrators group.
In Windows Server 2003, the Users group does not have Read and Execute permissions to the command processor (Cmd.exe). By default, the Cmd.exe program has the following permissions settings:
* The Interactive implicit group and the Service implicit group have Read and Execute permissions.
Note On a member server, the TelnetClients group also has Read and Execute permissions. On a domain controller, the Batch implicit group also has Read and Execute permissions.
* The Administrators group and the System implicit group have Full Control permissions
Method 1
Grant the Cmd.exe program Read and Execute permissions for the user account that the batch job runs under. To do this, follow these steps:
1. Click Start, and then click Windows Explorer.
2. Locate and then right-click the Cmd.exe file. The Cmd.exe file is located in the %windir%\System32 folder.
3. Click Properties.
4. Click the Security tab.
5. Click Add.
6. In the Enter the object names to select box, type the user name that the batch job runs under, and then click OK two times.
Note When you add the user, the user is automatically granted Read and Execute permissions.
7. Click Yes when you are prompted to continue.
Method 2
Grant Read and Execute permissions for the Cmd.exe file to the Batch group. This permits all batch processes to run the command processor. To do this, follow these steps:
1. Click Start, and then click Windows Explorer.
2. Locate and then right-click the Cmd.exe file. The Cmd.exe file is located in the %windir%\System32 folder.
3. Click Properties.
4. Click the Security tab.
5. Click Add.
6. In the Enter the object names to select box, type Batch, and then click OK two times.
7. Click Yes when you are prompted to continue.
