Symptoms
The Windows SBS Manager service is stopped with EventID 7034 every half an hour on SBS 2011.
-------------------------------------------
System log shows: Error 8/6/2013 11:00:19 AM Service Control Manager 7034 None
Log Name: System
Source: Service Control Manager
Date: 8/6/2013 11:00:19 AM
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: LSSERVER.ls.local
Description:
The Windows SBS Manager service terminated unexpectedly. It has done this 4 time(s).
-----------------------------------------
Cause
a corrupt WMI on a client computer
Resolution
Check the MonitoringDataCollection.log which is under C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs and found that it indicates a corrupt WMI on a client computer. The clues are like this:
----------------------------------------
2013-09-11T15:00:29.644036 : Exception caught when gathering computer DWALTERS01.domain.local's WMI information. It is being rethrown.
2013-09-11T15:00:29.659636 : System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.WMIInformation.GatherWMIItemCollection(WMIItemCollection results, ConnectionOptions conn, String computerName, String fileName, Boolean computerIsOnline, Logger log)
at Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.WMIInformation.<>c__DisplayClass5.<>c__DisplayClass7.<CollectWMIInformation>b__3(Object state)
-----------------------------------------
Note: System.IO.FileNotFoundException as mentioned in event logs.
Therefore, to resolve this issue, we can try:
Step 1: Go to DWALTERS01.domain.local's computer
=========
a. Right-click the My Computer icon and select Manage. (Alternate: Click Start, Control Panel, Administrative Tools, Computer Management.)
b. Left-click the <kbd>[+]</kbd> next to Services and Applications to expand the tree view.
c. Left-click on WMI Control.
d. Now, right-click on the same WMI Control item and select Properties.
f. If WMI is working properly, you will see "Successfully connected to <local computer>".
g. If WMI is broken, you will see one or more error messages in the dialog.
Step 2: Repair WMI on the computer reporting errors :
======
Run the following command line as elevated permission to reregister WMI Modules:
sc config winmgmt start= disabled
net stop winmgmt
cd %windir%\system32\wbem
for /f %s in ('dir /b *.dll') do regsvr32 /s %s
wmiprvse /regserver
net start winmgmt
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
Run the following command line to rebuild WMI Repository:
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 *.mof *.mfl') do mofcomp %s
More information:
WMI: Rebuilding the WMI Repository
Step 3: Please reset the parameters of Windows SBS Manager:
a. Double-click Windows SBS Manager, and then in the Properties dialog box, click the Recovery tab.
b. In First failure and Second failure, click Restart the Service.
c. In Set Subsequent failures, click Take No Action.
d. In Reset fail count after, type 1.
e. In Restart service after, click 5
Step 4: Go back on your server then wait for the next schedule of Datacollectorsvc (every 30mn)
Note: If it is OK, the MonitoringDataCollectionxxxxxxxxx.log should be clean and no more errors in the event logs.