Microsoft KB Archive/935641

= Error message when you use Computer Management after you upgrade the computer to Windows Server 2003: &quot;Snap-in failed to initialize&quot; =

Article ID: 935641

Article Last Modified on 5/1/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



SYMPTOMS
After you upgrade a computer that is running Microsoft Windows 2000 Server to Microsoft Windows Server 2003, you receive the following error message when you use Computer Management:

Snap-in failed to initialize

Name: System Information Extension

LSID:{}

Note When you click OK to close the error message, Computer Management starts.

Additionally, when you try to use Task Scheduler, you may receive one of the following error messages:

Error 2

Could not start the Task Scheduler service on local computer.

Error 2: The system can’t find the file specified.

Error 126

Error 126: The specified module could not be found.

When this problem occurs, the following event is logged in the System log: Event ID 7023

Source: Service Control Manager

Description: The Task Scheduler service terminated with the following error:



CAUSE
This problem occurs if some DLL files are missing or damaged.



RESOLUTION
To resolve this problem, reregister the Msinfo32.dll file, and then reregister the Schedsvc.dll file if it is required. To do this, follow these steps:  Make sure that the Msinfo32.dll file is in the &quot;C:\Program Files\Common Files\Microsoft shared\MSInfo&quot; folder. If the Msinfo32.dll file is missing, copy the Msinfo32.dll from another computer. Then, paste it in this folder.

Alternatively, you can use the Msinfo32.dll file that is included in hotfix 310928. For more information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

310928 You cannot open an .nfo file

 Reregister the Msinfo32.dll file. To do this, follow these steps:  Click Start, click Run, type Regsvr32 &quot;c:\program files\common files\microsoft shared\msinfo\msinfo32.dll&quot;, and then click OK.

Note Include the quotation marks when you type this command. When you receive a message that states that DllRegisterServer in Msinfo32.dll succeeded, click OK.  Make sure that Task Scheduler works. If you still experience the problem, reregister the Schedsvc.dll file. To do this, follow these steps:  Click Start, click Run, type Regsvr32 &quot;%SystemRoot%\System32\ schedsvc.dll&quot;, and then click OK.

Note Include the quotation marks when you type this command.</li> When you receive a message that states that DllRegisterServer in Schedsvc.dll succeeded, click OK.</li></ol> </li></ol>

Keywords: kbtshoot kberrmsg kbexpertiseinter KB935641

-

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

© Microsoft Corporation. All rights reserved.