SCOM reporting MP errors on Primary Sites
We use SCOM to monitor our servers and SCOM is reporting issues with our MPs on our Primary sites. I logged into one of our Primary servers and noticed that there is No CCM folder. It's not under C:\windows it's not under c:\windows\system32
and it's not under c:\windows\syswow64
There is a c:\windows\ccmsetup folder and it shows the client installed last Aug.
I remember reading that Management Point info was stored in the CCM\logs on the servers. Yes/no? Would this be causing the SCOM alerts about the MP?
I also looked in the \\ServerName\c$\Program Files (x86)\Microsoft Configuration Manager\Logs and checked out the MPMSI.LOG and MPSetup.log. The only thing I see there is in the MPSetup.LOG. It says:
<02-22-2012 15:33:42> Installation was successful, but a reboot is required.
Any hints/clues would be great.
mqh7
February 27th, 2012 1:09pm
Hey mqh7,
What issues are being reported? Are the clients able to communicate with the MP fine?
Moiz
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2012 1:35pm
here is the error from SCOM
Source: SCCMPri01.us.corp.com
Path:
Alert Rule: ConfigMgr 2007 Status: Site Component Manager failed to install the Management Point component because its Microsoft Installer File (MP.MSI) could not install it
Created: 2/24/2012 11:02:00 AM
SCCMPri01 - ConfigMgr 2007 Status: Site Component Manager failed to install the Management Point component because its Microsoft Installer File (MP.MSI) could not install it. A new monitored SMS status message on machine SCCMPri01 from component SMS_MP_CONTROL_MANAGER
with message ID 4951 was found in the site EU2 database. The status message contains message properties Machine Name: SCCMPri01 Module Name: SMS Server Component: SMS_MP_CONTROL_MANAGER Message ID: 4951 Win32 Error: 0 Top Level Site Code: Database Record ID:
139139
mqh7
February 27th, 2012 1:49pm
If your MP do not work. I presume you will soon know.
What do you see in MPControl.Log
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2012 5:48pm
The mpcontrol.log looks ok, no errors that I can see. But it has been doing a "Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK" every 30 seconds for a long time.
I looked at the Site Status and for my primary in question I looked at the SMS_MP_CONTROL_MANAGER and it has the same warning over and over....
MP could not find some class or property definitions when processing Hinv as they are apparently missing in sms_def.mof. Unknown classes and properties have been ignored and a MIF file generated with all the classes and properties that could be found.
Possible cause: This might indicate that the report has become obsolete due to a new HW inventory policy or that a customer's private definitions haven't been properly propagated to the sms_def.mof at the PSS.
Solution: See if the missing classes or properties are genuinely missing in the current sms_def.mof and find out why the client put them in the xml report.
I read this http://ihateyou1603.blogspot.com/2010/05/smsmpcontrolmanager-warnings-5416-5418.html is that the one and only fix for this error?
mqh7
February 28th, 2012 6:10pm
Try to :
Remove the Management Point Role.Remove the BITS component.Reinstall the BITS Component.Reinstall the Management Point Role.
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2012 1:26am
Dear Mqh7,
Were you able to get your problem solved?Regards, Ahmad
March 3rd, 2012 11:39pm
no, it is still a problem. I've removed the MP and added it back and that did not fix the issue. mqh7
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2012 2:33pm
Are you still haveing the sms_def.mof errors also or just thescom problem?
May 9th, 2012 8:53pm