Microsoft KB Archive/945763

= Installation of Windows 2003 Service pack fails when WMI breaks =

Article ID: 945763

Article Last Modified on 11/30/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-



Source: Microsoft Support



RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.



Action


Result
The installation of Windows 2003 Service pack failed, and you received the following error:

&quot;An error in updating your system occurred. click ok to continue&quot;

In the SVCPACK.Log file, you see lines similar to the followings:

1142.453: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe C:\WINDOWS\system32\wbem\wlbsprov.mof

1142.860: Return Code = 3

1142.860: Starting process: C:\WINDOWS\system32\wbem\mofcomp.exe C:\WINDOWS\system32\wbem\cimwin32.mof

1145.375: Return Code = 3

609.688: DoInstallation:RunInfProcesses for ProcessesToRun Failed

609.688: Service Pack 2 Setup encountered an error: An error in updating your system has occurred.



Cause
This normally happens when there are issues with WMI.



Resolution
1. If the WMI service is not started, try to start it. Then test to see if the issue is resolved.

2. Troubleshoot the WMI issue. For more information about how to do this, visit the following Microsoft Web site:

http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx

Workaround:

A workaround to this is to rebuild the WMI Repository.

Warning: This is not suitable if there is critical data stored in the WMI namespace because rebuilding will lose the data. Also, the namespaces of non-Windows products are not rebuilt using the steps below. For example, Exchange WMI namespaces would not regenerate after rebuilding, and this may require a reinstallation of Exchange.

1. Back up the WBEM folder (%windir%\system32\wbem) and then copy the WBEM folder from a freshly installed computer with the same version and service pack level.

2. Run the following steps in a command prompt:

cd %windir%\system32\wbem

for /f %s in ('dir /b *.dll') do regsvr32 /u /s %s

for /f %s in ('dir /b *.dll') do regsvr32 /s %s

wmiprvse /regserver

winmgmt /regserver



MoreInformation
For more information about Windows Management Instrumentation, refer to the link below:

http://www.microsoft.com/technet/community/en-us/management/wmi_faq.mspx



DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

Keywords: kbnomt kbrapidpub KB945763

-

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

© Microsoft Corporation. All rights reserved.