Microsoft KB Archive/134425

= Event ID 7000: %1 Not A Valid Windows NT Application =

Article ID: 134425

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Server 3.5
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 3.1
 * Microsoft Windows NT Workstation 3.5
 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Advanced Server 3.1

-



This article was previously published under Q134425



IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" help topic in Regedt32.exe.



SYMPTOMS
When you restart Windows NT and attempt to run an application, service, or install a network protocol, one of the following system events appears in Event Viewer:

Event ID: 7000

Source: Service Control Manager

Type: Error

Description: The service failed to start due to the following error: : %1 not a valid Windows NT Application.

-or-

Event ID: 7000 Source: Service Control Manager Type: Error Description: The service failed to start due to the following error: The system cannot find the file specified.

-or-

When you try to manually start a service from the Services tool in Control Panel, you may receive the following error message:

Could not start the service on \\ 0193: %1 is not a valid application.



CAUSE
This problem occurs if a service component required for Windows NT, an application, or a network protocol, is corrupted or missing.

-or-

The problem can also occur if the folder location of the executable contains spaces in the directory name (long filename). An example would be when the executable is located in the \Program files\ folder.



RESOLUTION
To correct this problem if the file is missing, manually expand the service component file. For example, if the in Event ID 7000 is MUP, expand MUP.SY_ from the Window NT CD-ROM to MUP.SYS in the %SystemRoot%\SYSTEM32\DRIVERS folder.

To correct this problem if the file is located in a folder with a long file name, modify the registry key containing the executable path to be enclosed in quotation marks or change the executable to use the standard 8.3 (tilde ~) path notation.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

For example:

 Run Registry Editor (Regedt32.exe), and then navigate to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\[name of service]

 Double click the ImagePath value, and then change the Value Data of ImagePath by adding quotation marks around the complete path, including the executable name. For example: "C:\Program Files\{executable}".

Additional query words: prodnt 3.10 transport

Keywords: KB134425

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.