joemonkey
Posts: 202
Score: 2
Joined: 2/28/2007
From: Kentucky
Status: offline
|
I have a secondary site that is acting as a Client Access Point, Component Server, Protected DP, Management Point, and Site Server. The SMS Agent Host service will not start, get an error that it stopped immediately after starting. SMS console shows these errors over and over again for SMS_MP_CONTROL_MANAGER:
MP could not write out CCM setting to WMI. The operating system reported error 2147942406: The handle is invalid.
Possible cause: MP didn't get installed properly.
Solution: Ensure MP setup succeeded; if not, reinstall MP
MP could not update its settings to the new values. The operating system reported error 2147942406: The handle is invalid.
Possible cause: MP may be overloaded.
Solution: Reapply the setting at a later time.
SMS Executive detected that this component stopped unexpectedly.
Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly.
Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
I am hesitant to just reinstall the MP as the event log on the server itself has some non-related SMS errors I think we need to fix first, such as these errors every few seconds:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{1A9FFCE9-10C1-40BC-9815-B20C1DC2D156}
to the user server\IWAM_server SID (S-1-5-21-1830910100-3609409641-3265200446-1004). This security permission can be modified using the Component Services administrative tool.
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.
Windows cannot find the machine account, The clocks on the client and server machines are skewed. .
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
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.
The COM+ sub system is suppressing duplicate event log entries for a duration of 86400 seconds. The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\COM3\Eventlog.
Seems to me WMI is hosed on that box. Should I uninstall it as a MP, try to repair WMI, then reinstall?
|
Printable Version
Secondary site - multiple errors, need help fixing - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread