Strict Standards: Non-static method Settings::setHostName() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\AutoConfig.php on line 20

Strict Standards: Non-static method Settings::addHostAlias() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\AutoConfig.php on line 22

Strict Standards: Non-static method Settings::setSiteRoot() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\AutoConfig.php on line 28

Strict Standards: Non-static method Settings::setDsn() should not be called statically in C:\website\www.networksteve.com\exchange\_site\Config.php on line 16

Strict Standards: Non-static method Settings::setTitle() should not be called statically in C:\website\www.networksteve.com\exchange\_site\Config.php on line 19

Strict Standards: Non-static method Settings::setDescription() should not be called statically in C:\website\www.networksteve.com\exchange\_site\Config.php on line 20

Strict Standards: Non-static method Settings::setSiteRoot() should not be called statically in C:\website\www.networksteve.com\exchange\_site\Config.php on line 24

Strict Standards: Non-static method Settings::setShowDeleted() should not be called statically in C:\website\www.networksteve.com\exchange\_site\Config.php on line 31

Strict Standards: Non-static method Settings::setRecentTopicsDuration() should not be called statically in C:\website\www.networksteve.com\exchange\_site\Config.php on line 36

Strict Standards: Non-static method Settings::test() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Init.php on line 28

Strict Standards: Non-static method Skin::test() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Init.php on line 29

Strict Standards: Non-static method Settings::getSkin() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Skin.php on line 102

Strict Standards: Non-static method Settings::getSiteRoot() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Init.php on line 32

Strict Standards: Non-static method Settings::getDsn() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Init.php on line 35

Strict Standards: Non-static method Form::field() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Init.php on line 39

Strict Standards: Non-static method Form::fieldExists() should not be called statically, assuming $this from incompatible context in C:\website\www.networksteve.com\exchange\_lib\Entity\User.php on line 92

Strict Standards: Non-static method Form::fieldExists() should not be called statically in C:\website\www.networksteve.com\exchange\topic.php on line 15

Strict Standards: Non-static method Form::field() should not be called statically in C:\website\www.networksteve.com\exchange\topic.php on line 17

Strict Standards: Non-static method Settings::getShowDeleted() should not be called statically, assuming $this from incompatible context in C:\website\www.networksteve.com\exchange\_lib\Entity\Topic.php on line 138

Strict Standards: Non-static method Entity_Post::queryPosts() should not be called statically in C:\website\www.networksteve.com\exchange\topic.php on line 21

Strict Standards: Non-static method Settings::getShowDeleted() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Entity\Post.php on line 111

Strict Standards: Non-static method Skin::showHeader() should not be called statically in C:\website\www.networksteve.com\exchange\topic.php on line 23

Strict Standards: Non-static method Skin::includeFile() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Skin.php on line 46

Strict Standards: Non-static method Settings::getSkin() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Skin.php on line 91
Exchange 2003 - Error in MAD Monitoring 9097 & Windows Management Instrumentation (Network Steve Forum)
Exchange 2003 - Error in MAD Monitoring 9097 & Windows Management Instrumentation
Hi, i have a problem with the Tracking Tool and the Windows Management Instrumentation. When i click in the System Manger - Administrative Groups - My Group - Servers - MyServer1 - Properties, i see the error: An error occurred during a call to Windows Management Instrumentation ID no: 80041013 Exchange System Manager Event Type: Error Event Source: MSExchangeSA Event Category: Monitoring Event ID: 9097 Date: 19.01.2011 Time: 10:55:52 User: N/A Computer: BSEX1 Description: The MAD Monitoring thread was unable to connect to WMI, error '0x8004100e'. For more information, click http://www.microsoft.com/contentredirect.asp. The articel "Error "0x8004100e" and event ID 9097 occur when you run the System Attendant in Exchange Server 2003" did not help for my exchange server :-(. http://support.microsoft.com/kb/288590/en-us Any tips anyone? :) Thanks
January 19th, 2011 2:56am

Please go thru below post for same kind of error, Its need bit of scripting.. http://www.petri.co.il/forums/showthread.php?t=4204 http://www.mrtweak.com/exchange-server/exchange-wmi-errors-wmi-repository-clear-reinstall-script/ http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/ce15132b-8f3a-4193-af06-1a2b65c833a8/Anil
Free Windows Admin Tool Kit Click here and download it now
January 19th, 2011 3:13am

If the above thing didnt work, connect with PSS. You need to un-register the WMI and re-register it.
January 19th, 2011 3:16am

hi thanks for the answer. hmm, i become the following error message on the Script: An error occurred while opening the namespace for object 1 defined on lines 3 - 10: Error Number: 0x8004100e, Facility: WMI Description: Invalid namespace C:\>net stop winmgmt The Windows Management Instrumentation service is stopping. The Windows Management Instrumentation service was stopped successfully. C:\>c: C:\>cd C:\WINDOWS\system32\wbem C:\WINDOWS\system32\wbem>rd /S /Q repository C:\WINDOWS\system32\wbem>regsvr32 /s C:\WINDOWS\system32\scecli.dll C:\WINDOWS\system32\wbem>regsvr32 /s C:\WINDOWS\system32\userenv.dll C:\WINDOWS\system32\wbem>mofcomp cimwin32.mof Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: cimwin32.mof MOF file has been successfully parsed Storing data in the repository... Done! C:\WINDOWS\system32\wbem>mofcomp cimwin32.mfl Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: cimwin32.mfl MOF file has been successfully parsed Storing data in the repository... Done! C:\WINDOWS\system32\wbem>mofcomp rsop.mof Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: rsop.mof MOF file has been successfully parsed Storing data in the repository... Done! C:\WINDOWS\system32\wbem>mofcomp rsop.mfl Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: rsop.mfl MOF file has been successfully parsed Storing data in the repository... Done! C:\WINDOWS\system32\wbem>for /F %s in (’dir /b /s *.dll’) do regsvr32 /s %s C:\WINDOWS\system32\wbem>for /F %s in (’dir /b *.mof’) do mofcomp %s C:\WINDOWS\system32\wbem>for /F %s in (’dir /b *.mfl’) do mofcomp %s C:\WINDOWS\system32\wbem>mofcomp -n:root\cimv2\applications\exchange wbemcons.mof Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: wbemcons.mof MOF file has been successfully parsed Storing data in the repository... An error occurred while opening the namespace for object 1 defined on lines 3 - 10: Error Number: 0x8004100e, Facility: WMI Description: Invalid namespace Compiler returned error 0x8004100e C:\WINDOWS\system32\wbem>mofcomp -n:root\cimv2\applications\exchange smtpcons.mof Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: smtpcons.mof MOF file has been successfully parsed Storing data in the repository... An error occurred while opening the namespace for object 1 defined on lines 4 - 16: Error Number: 0x8004100e, Facility: WMI Description: Invalid namespace Compiler returned error 0x8004100e C:\WINDOWS\system32\wbem>mofcomp exmgmt.mof Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: exmgmt.mof MOF file has been successfully parsed Storing data in the repository... Done! C:\WINDOWS\system32\wbem>mofcomp exwmi.mof Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959 Copyright (c) Microsoft Corp. 1997-2001. All rights reserved. Parsing MOF file: exwmi.mof MOF file has been successfully parsed Storing data in the repository... Done! C:\WINDOWS\system32\wbem>net start winmgmt Chris
Free Windows Admin Tool Kit Click here and download it now
January 19th, 2011 4:47am

Hi, Please also perform the following steps to troubleshoot the issue. 1. Create a new text file and copy the following commands to the new created txt file, and then save it as WMI.bat file. Please double click the WMI.bat file. net stop winmgmt c: cd %windir%\system32\wbem rd /S /Q repository regsvr32 /s %systemroot%\system32\scecli.dll regsvr32 /s %systemroot%\system32\userenv.dll mofcomp cimwin32.mof mofcomp cimwin32.mfl mofcomp rsop.mof mofcomp rsop.mfl for /f %%s in (’dir /b /s *.dll’) do regsvr32 /s %%s for /f %%s in (’dir /b *.mof’) do mofcomp %%s for /f %%s in (’dir /b *.mfl’) do mofcomp %%s mofcomp -n:root\cimv2\applications\exchange wbemcons.mof mofcomp -n:root\cimv2\applications\exchange smtpcons.mof mofcomp exmgmt.mof mofcomp exwmi.mof net start winmgmt After that, please verify WMI service and verify the symptom again. If the issue persists, please move on the next steps. 2. Please upgrade all Service Pack and updates for Exchange 2003. 3. Register relevant DLL files via the following article: http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/42691/Exchange-System-Manager-and-WMI Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
January 20th, 2011 11:07pm

Hi, thanks for the information. How it works now :) sc config winmgmt start= disabled net stop winmgmt cd %windir%\system32\wbem rename repository repository.old sc config winmgmt start= auto for /f %s in ('dir /b *.dll') do regsvr32 /s %s for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s cd D:\Exchsrvr\bin\ exmgmt.exe /uninstall exmgmt.exe /install regsvr32 /s exwmi.dll regsvr32 /s cdowf.dll regsvr32 /s cdowfevt.dll cd %windir%\system32\wbem mofcomp.exe -class:forceupdate C:\WINDOWS\system32\WBEM\exmgmt.mof mofcomp.exe C:\WINDOWS\system32\WBEM\exwmi.mof mofcomp.exe -n:root\cimv2\applications\exchange C:\windows\system32\wbem\wbemcons.mof mofcomp.exe -n:root\cimv2\applications\exchange C:\windows\system32\wbem\smtpcons.mof mofcomp.exe -n:root\cimv2\applications\exchange C:\winnt\system32\wbem\msgtrk.mof Thanks chris
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2011 8:04am


Strict Standards: Non-static method Settings::getRecentTopicsLimit() should not be called statically, assuming $this from incompatible context in C:\website\www.networksteve.com\exchange\_lib\Entity\Topic.php on line 120

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics

Strict Standards: Non-static method Skin::showFooter() should not be called statically in C:\website\www.networksteve.com\exchange\topic.php on line 121

Strict Standards: Non-static method Skin::includeFile() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Skin.php on line 56

Strict Standards: Non-static method Settings::getSkin() should not be called statically in C:\website\www.networksteve.com\exchange\_lib\Skin.php on line 91