WinMgmt could not initialize the core parts

[Bob]

I had to replace my "windows\system32\config\system" registry three days ago
I using the procedure found in KB306038. The file located at
C:\WINDOWS\repair was dated about 12 hours earlier. I notice today that I've
been getting the following errors ever since. Below are the first errors.

I noticed the problem when DFSR posted the error "Cannot access the local
WMI repository" and WSUS ver 3.0 (wsus.msc) failed with "snap-in not
responding" and "can't connect to the WSUS server".

Any ideas on how I can resolve this? Thanks!

-----------------------------------------------------------------------------------------------
Event Type: Error
Event Source: WinMgmt
Event Category: None
Event ID: 28
Date: 5/10/2007
Time: 11:05:10 AM
User: N/A
Computer: RC-SERVER-4
Description:
WinMgmt could not initialize the core parts. This could be due to a badly
installed version of WinMgmt, WinMgmt repository upgrade failure,
insufficient disk space or insufficient memory.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 5/10/2007
Time: 11:05:22 AM
User: N/A
Computer: RC-SERVER-4
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report
server database.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------------------------------------------

[Ken Zhao [MSFT]]

Hello Bob,

Thank you for using newsgroup!

From your post, it appears that the WMI installation of this computer is
corrupt. Please try to reset the WMI installation using the following
procedure:

1. Stop the WINMGMT (Windows Management Instrumentation) service.
2. Move all the files under the WBEM Repository directory (located in the
\%Windir%\System32\WBEM directory) to a temp folder. In fact we can delete
the files here as well. Moving the files is just a backup for the files
here.
3. Restart the WINMGMT (Windows Management Instrumentation) service.
4. If the files in the WBEM Repository directory are not created by
restarting the WMI service, restart the computer and these files should be
created.

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://www.microsoft.com/security>
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| Thread-Topic: WinMgmt could not initialize the core parts
| thread-index: AceVijQQdI7DMtItRQ6EF08uNq0dUg==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?Qm9i?= <86c6c2e6-2146512712@news.postalias>
| Subject: WinMgmt could not initialize the core parts
| Date: Sun, 13 May 2007 11:12:01 -0700
| Lines: 48
| Message-ID: <C5D405E2-01C0-4206-9A5C-28F8E962728E@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.general
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.general:12851
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.general
|
| Hi,
|
| I had to replace my "windows\system32\config\system" registry three days
ago
| I using the procedure found in KB306038. The file located at
| C:\WINDOWS\repair was dated about 12 hours earlier. I notice today that
I've
| been getting the following errors ever since. Below are the first errors.
|
| I noticed the problem when DFSR posted the error "Cannot access the local
| WMI repository" and WSUS ver 3.0 (wsus.msc) failed with "snap-in not
| responding" and "can't connect to the WSUS server".
|
| Any ideas on how I can resolve this? Thanks!
|
----------------------------------------------------------------------------
-------------------
| Event Type: Error
| Event Source: WinMgmt
| Event Category: None
| Event ID: 28
| Date: 5/10/2007
| Time: 11:05:10 AM
| User: N/A
| Computer: RC-SERVER-4
| Description:
| WinMgmt could not initialize the core parts. This could be due to a
badly
| installed version of WinMgmt, WinMgmt repository upgrade failure,
| insufficient disk space or insufficient memory.
|
| For more information, see Help and Support Center at
| http://go.microsoft.com/fwlink/events.asp.
----------------------------------------------------------------------------
-------------------
| Event Type: Error
| Event Source: Report Server Windows Service (MSSQLSERVER)
| Event Category: Management
| Event ID: 107
| Date: 5/10/2007
| Time: 11:05:22 AM
| User: N/A
| Computer: RC-SERVER-4
| Description:
| Report Server Windows Service (MSSQLSERVER) cannot connect to the report
| server database.
|
| For more information, see Help and Support Center at
| http://go.microsoft.com/fwlink/events.asp.
----------------------------------------------------------------------------
-------------------
|
| --
| Bob
|

[Bob]

I tried your procedure, but it didn't work. There were two files located in
the \%Windir%\System32\WBEM directory. They were msfeeds.mof and
msfeedsbs.mof. Both are still in my recycle bin. After a reboot, the
\%Windir%\System32\WBEM directory is still empty and the errors are still
posting.

Any ideas what to do next?

[Bob]

I deleted the wrong folder.
You clearly said \%Windir%\System32\WBEM, but I did \%Windir%\WBEM. I put
the files back and deleted the correct files this time.

To be clear, this is what I finally did.
1. net stop WINMGMT
2. Restored C:\WINDOWS\WBEM\msfeeds.mof
3. Restored C:\WINDOWS\WBEM\msfeedsbs.mof
4. Deleted C:\WINDOWS\system32\wbem\Repository\$WinMgmt.CFG
5. Deleted the five files in folder C:\WINDOWS\system32\wbem\Repository\FS
6. Register all DLLS in %SystemRoot%\System32\wbem by doing the following
from the cmd prompt:
a) cd C:\WINDOWS\system32\wbem
b) for /f %s in ('dir /b *.dll') do regsvr32 /s %s
7. Restarted system.

Result is I no longer get the WinMgmt Event ID: 28 error. THANKS!

BUT I'm still getting other WMI type errors.

Here's an RSoP error followed by one from DFSR.
-----------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1090
Date: 5/14/2007
Time: 3:22:35 PM
User: NT AUTHORITY\SYSTEM
Computer: RC-SERVER-4
Description:
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An
attempt to connect to WMI failed. No more RSoP logging will be done for this
application of policy.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------
Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 6104
Date: 5/14/2007
Time: 3:29:51 PM
User: N/A
Computer: RC-SERVER-4
Description:
The DFS Replication service failed to register the WMI providers.
Replication is disabled until the problem is resolved.

Additional Information:
Error: 2147749902 (100e)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
----------------------------------------------------------------------------------------------

[Ken Zhao [MSFT]]

Glad to hear that your original issue has been resolved. For other WMI
issues, please submit other posts so that our engineer will follow this.

[Tony Barkdull]

The WMI process is not starting or is corrupt. To reinstall the WMI files, click Start > Run and type in:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

You will need a Windows XP CD.

Open the Control Panel, Administrative Tools, Computer Services, Computers, My Computer, DCOM Config. Click yes on any prompts to record AppID data

Click Start / Run and type wbemtest, click connect twice to confirm WMI is working properly. If it is not, Restart and retest.

You use a Windows XP CD for a WBEM reinstall on Windows Server 2003?

[Lanwench [MVP - Exchange]]

Hi, Amol - you've posted this as a brand new message, not a reply to an
existing post - so it's unlikely anyone will know what you refer to.
Remember that this is a newsgroup, not a forum.

[tbarkdull]

For Windows 2003 Server, use the CD for 2003.

If you follow the procedure above for XP and the wbemtest fails, check the errors in the event log. Repeat the procedure. I have rarely had to do so.

[eldios13]

In Local Area Connection Properties, the Advance tab cannot be displayed. The next error appears:

"Windows cannot display the properties of this connection. The Windows Management Instrumentation (WMI) information might be corrupted. To correct this, use System Restore to restore Windows to an earlier time(called a restore point). System restore is located in the System Tools Folder in Accessories."

To FIX it in XP:

The WMI process is not starting or is corrupt. To reinstall the WMI files, click Start > Run and type in:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

You will need a Windows XP CD (or just the i386 folder).

You will also need some extra files that you can find in any PC with XP installed in:
C:\WINDOWS\system32\wbem

After done, restart and it should be working.