Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SP3 crashed server

Status
Not open for further replies.

haxx77

MIS
Mar 6, 2001
77
US

During the first few minutes of the install of SP3 I got a blue screen. The blue screen comes up regardless of what I try ( safe mode , etc .)

The error is:

kmode_exception_not_handled.

Now what.
 
SP3 UPGRADE FAILURE

Several readers asked for assistance with a Windows 2000 Service Pack 3 (SP3) setup failure that produces the error message "An error in updating your system has occurred. When you click OK, Windows is not upgraded to SP3 and you can no longer install programs that use the Windows Installer (.msi packages)."



When this error occurs, any later attempts to use Windows Installer to install software (e.g., SP3, a Microsoft Office update, or any software that uses winstall technology) will produce a message that says "The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed...."



This failure occurs because the latest version of Windows Installer (version 2.0.2600.2), packaged with SP3, doesn't install or run on a system on which the Distributed COM (DCOM) default impersonation level is set to Anonymous. Even worse, after an SP3 installation fails, the system retains the SP3 version of Windows Installer, but the installer won't function properly even if you restart the upgrade. To reinstall SP3 successfully, you need to change the DCOM impersonation level to Identify, and you need to delete the problem Windows Installer file (msisip.dll). To change the DCOM impersonation level, open a command prompt and type



dcomcnfg



If some objects aren't registered, the command will prompt you to register them. Then the utility displays the DCOM Configuration Properties window. Click the Default Properties tab, change the setting in the Default Impersonation field to Identify (click the down arrow for this field to view all valid settings), and click OK to exit.



To delete the problem Windows Installer file, locate and delete (or

rename) the file \%windir%\system32\msisip.dll. After taking this corrective action, you should be able to complete an SP3 upgrade. For more information, read the Microsoft article "Service Pack 3 Update Is Unsuccessful When DCOM Impersonation Level Is Set to Anonymous" at .



WEB-EXCLUSIVE ARTICLES: The following items are posted on the Windows & .NET Magazine Web site. For the complete story, use the following link and scroll to the appropriate article.




* SP3 PERFORMANCE MONITOR HOTFIX FOR NON-ENGLISH VERSIONS

A bug in how Windows 2000 Service Pack 3 (SP3) updates Performance Monitor counters causes the counter names to display with unrecognizable characters at the end of each counter name. Learn more about this problem at the following URL:




* A BUCKETLOAD OF WINDOWS EXPLORER BUGS

Windows Explorer has several bugs that Windows 2000 Service Pack 3

(SP3) doesn't correct. Visit the following URL for a list of the misbehaviors and bug fixes, all of which are available only from Microsoft Product Support Services (PSS).




* POST-SP3 COM+ HOTFIX ROLLUP 21

Microsoft released the Windows 2000 post-Service Pack 3 (SP3) COM+ hotfix rollup package on June 4. Find out more about the rollup and how to get it at the following URL:




* NETWORK CONNECTION MANAGER SECURITY HOTFIX

Find out about a flaw in the Windows 2000 Network Connection Manager and how to fix it.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top