Article ID: 247929
Article Last Modified on 3/2/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Datacenter Server
This article was previously published under Q247929
SYMPTOMS
When you try to use the service recovery functionality in Windows 2000 Services Manager to execute a batch or script file, you may be unable to do so.
CAUSE
This issue can occur if you do not specify an appropriate program to execute the script or batch file.
RESOLUTION
To work around this issue:
- Click Start, click Programs, and then click Administrative Tools.
- Click Services, and then double-click the appropriate service.
- Click Recovery, and then select the appropriate response from either the First failure box, the Second failure box, or the Subsequent failures box.
- Type in the appropriate executable followed by the full path and file name of the file you want to execute.
NOTE: If you want to run a batch file, type the forcedos.exe command in the Program box, and then typemyfile.bat in the Command line parameters box, wheremyfileis your file name.
If you want to run a script file, type one of the following commands for Microsoft Visual Basic scripts, wheremy scriptis the name of your script.wscript.exe
my script.vbs
wscript.exemy script.js (for Java scripts) - Click OK, and then close Services Manager.
STATUS
This behavior is by design.
MORE INFORMATION
The Windows 2000 Service Control Manager is a Microsoft Management Console (MMC) snap-in. This new feature replaces the Control Panel/Services functionality used in previous versions of Windows NT and provides the capability of customizing recovery options for a service that has failed.
For more information about using Windows 2000 Services Manager, consult the Using Services topic in Windows 2000 Help.
Keywords: kbenv kbprb KB247929
