Scripts deployed to computer do not run (Userinit events 1000 and 1001)
Updated: March 2, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
A logon, logoff, machine startup, or machine shutdown script deployed to the computer through Group Policy does not run.
The event logs may show one of the following Userinit events:
Event ID 1000
Message: Could not execute the following script %1. %2.
Event ID 1001
Message: Could not locate the script command lines in the Group Policy object.
These Userinit events may be caused by one of the following issues:
Network problems that prevent the computer from accessing the domain controller or the network location of the script executable files
Invalid script command lines
Replication problems on the domain controller
Network errors that occur during script execution can cause these errors. In this case, troubleshooting and resolving the network problems will resolve this error. For information about troubleshooting network issues, see Fixing Group Policy networking issues.
A script may also be inaccessible because of file sharing violations. In this case, the administrator of the network share on which the script resides must determine which users or computers are locking the file and close their connection to the file. To perform this diagnosis, you can use file system tools (such as net.exe).
For information about file sharing violations and replication issues, see FRS Encounters "ERROR_SHARING_VIOLATION" Errors When It Tries to Replicate Data That Is Still in Use on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=43053).
Script command lines errors
Run the command line listed in the event log, using the directory from which the script originates as your default directory. The script directory is either the user\scripts or the machine\scripts directory, depending on whether the script is a logon/logoff script or a machine startup/shutdown script. You can use the Group Policy Management Console (GPMC) to find the GPO containing this path. If the policy is a computer policy, use an account that has access to the network location listed in the script.
If the command line execution fails, investigate this as you would investigate any error related to running a command. For example, look for typographical mistakes in the path or the specification of a relative path that is not present on the local computer.
To change an incorrect path, use GPMC to edit the GPO for which you want to modify the path, and type the correct path. To fix this problem, you must be a network administrator with rights to the GPO.
Domain Controller replication issues
When scripts are stored on the domain’s sysvol share, replication problems can cause the script to not be present or to have incorrect access permissions. For information about troubleshooting replication issues, see Group Policy does not replicate.