Jump to content


Sign in to follow this  
Iroqouiz

Management Point not responding to HTTP requests (error 500)

Recommended Posts

*PROBLEM SOLVED, CHECK MY LAST POST*

 

Hey,

 

Perhaps someone could help me with this. My Management Point is freaking out. Everything has been working fine up until a few days ago. Started getting the following error:

 

"MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error."

 

I set up a new web service (Maik Koster's) like a week ago, which has been working. A few days go by and suddenly my clients didn't receive a policy when doing OSD. Saw MP was critical. Can't really find any information about this when it comes to SCCM 2012, only 2007. Don't think it's IIS. I can access it via IE and run, for instance, GetCollectionMembers.

So that leaves the MP to have some issues with SQL? Haven't touched that since installing the server.

Should add that I removed the MP role yesterday, rebooted the server, and then installed it again. That made it work until midnight. At least it was all green in Site Status and Component Status.

Any tips?

Share this post


Link to post
Share on other sites


@Iroqouiz - On your SQL server check the following > Go into SQL Server Configuration Manager / Network

Configuration / Protocols for MSSQLSERVER / TCP/IP and make sure its set to "enable".

 

Try Restarting the SMS Agent host service.

Share this post


Link to post
Share on other sites

Hey, thanks for the tip. When I opened SQL CM I got this error message:

 

0435.09112708CannotconnecttoWMIproviderSQLServerConfigurationManagerInvalidclassmofcompMOF_5F00_thumb_5F00_555AD87C.jpg

 

Ran this command in an elevated cmd:

 

mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

 

After that I could start SQL CM. Checked, and TCP/IP is Enabled. Restarted the SMS service also. Didn't solve my problem though.

 

I forgot to mention that I've experimented with my configuration.mof and sms_def.mof files. Added one class for Hardware Inventory. Could that have messed things up?

Share this post


Link to post
Share on other sites

After a reboot of the server, mpcontrol.log says this:


SMS_MP_CONTROL_MANAGER received STOP notification. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
UnregisterFromWINS: Unregistering the WINS name MP_P01 ... SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
UnregisterFromWINS: EnumerateLANAs() returned 0x0 SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
NetBIOS_DelName(): LocalName: MP_P01 LanaNumber: 1 SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
UnregisterFromWINS: NetBIOS_DelName(LANA=1) returned 0x0 SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
MPStop(): UnregisterFromWINS returned 0x0. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
CMPControlManager::RemoveInDNS: Couldn't delete DNS record of service <SRV_RECORD> FQDN <SCCM_PRIMARY_SITE_SERVER> SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
MPStop(): RemoveInDNS() returned 0x0. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
CMPControlManager::UnregisterForIPAddressChangeNotification() returned 0x0 SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
MPStop(): UnregisterForIPAddressChangeNotifications() returned 0x0 SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
MPStop(): Returning with 0x0. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
SMS_MP_CONTROL_MANAGER successfully STOPPED. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
******************************************************************************** SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4808 (0x12C8)
The registry change notification registry key handle has been closed. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4128 (0x1020)
Deleted 'SMS Server Availability' performance instance => SMS Management Point. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4128 (0x1020)
Configuration and Availability Monitor thread stopped. SMS_MP_CONTROL_MANAGER 2012-08-30 08:41:39 4128 (0x1020)
SMS_EXECUTIVE started SMS_MP_CONTROL_MANAGER as thread ID 4640 (0x1220). SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 1148 (0x047C)
******************************************************************************** SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
SMS_MP_CONTROL_MANAGER received START notification. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
MPStart(): Registered for Notifications. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
CMPControlManager::ReadConfigurationSettings(): m_pWmi->GetObject() failed - 0x80041010 SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
CMPControlManager::ReadConfigurationSettings(): Periodic Interval is 1800000 SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
CMPControlManager::ReadConfigurationSettings(): WINS Interval is 14400000 SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
MPStart(): ReadConfigurationSettings() returned 0x80041010. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
Querying MPHealthCheckIntervalInSeconds registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
Querying MPHealthCheckTimeoutInSeconds registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
Querying MPHealthCheckStatusMessageIntervalInSeconds registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
Querying NLBNodeAvailabilityState registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
MPStart(): Read all MP Settings. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
MPStart(): SSL disabled. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
CMPControlManager::WriteToCCMSettings(): WMI Connection established. SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
CMPControlManager::WriteToCCMSettings(): pWmi->GetObject() failed - 0x80041002 SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
STATMSG: ID=5432 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" SYS=<SCCM_PRIMARY_SITE_SERVER> SITE=P01 PID=1196 TID=4640 GMTDATE=to aug 30 06:43:43.836 2012 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
MPStart(): WriteToCCMSettings() failed - 0x80041002 SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)
SMS_MP_CONTROL_MANAGER failed to start with 0x80041002 SMS_MP_CONTROL_MANAGER 2012-08-30 08:43:43 4640 (0x1220)

SMS_EXECUTIVE started SMS_MP_CONTROL_MANAGER as thread ID 1616 (0x650). SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1148 (0x047C)
******************************************************************************** SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
SMS_MP_CONTROL_MANAGER received START notification. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
MPStart(): Registered for Notifications. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
CMPControlManager::ReadConfigurationSettings(): m_pWmi->GetObject() failed - 0x80041010 SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
CMPControlManager::ReadConfigurationSettings(): Periodic Interval is 1800000 SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
CMPControlManager::ReadConfigurationSettings(): WINS Interval is 14400000 SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
MPStart(): ReadConfigurationSettings() returned 0x80041010. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
Querying MPHealthCheckIntervalInSeconds registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
Querying MPHealthCheckTimeoutInSeconds registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
Querying MPHealthCheckStatusMessageIntervalInSeconds registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
Querying NLBNodeAvailabilityState registry value returned a status of 2. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
MPStart(): Read all MP Settings. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
MPStart(): SSL disabled. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
CMPControlManager::WriteToCCMSettings(): WMI Connection established. SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
CMPControlManager::WriteToCCMSettings(): pWmi->GetObject() failed - 0x80041002 SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
STATMSG: ID=5432 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" SYS=<SCCM_PRIMARY_SITE_SERVER> SITE=P01 PID=1196 TID=1616 GMTDATE=to aug 30 06:44:41.787 2012 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
MPStart(): WriteToCCMSettings() failed - 0x80041002 SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)
SMS_MP_CONTROL_MANAGER failed to start with 0x80041002 SMS_MP_CONTROL_MANAGER 2012-08-30 08:44:41 1616 (0x0650)

Share this post


Link to post
Share on other sites

*PROBLEM SOLVED*

 

Like 2 months ago I accidentally installed the ConfigMgr client on my server. I uninstalled it but it still looked in the console as the server had the client. I double checked then, and it looked fine. Now it seemed like the server had tried to remediate the client (think I forgot to remove the ccmsetup and ccm folders from the C drive back in the days). But the remediation failed and somehow messed things up with the MP.

 

Yesterday I noticed that the MP always stopped working at the same time every night. That's when I noticed the server actually had a half-installed client. Checked in Task Scheduler and saw that the task for ccmeval last ran the same time my MP went down. Ran ccmclean and removed entries from the registry as well as the ccmsetup folder. Checked Task Scheduler again to make sure ccmeval wasn't there.

 

Server and MP looks fine as of this morning :)

Share this post


Link to post
Share on other sites

Thanks for the post. I think that is what is causing my MP to fail also. I will let you know.

 

A question then...

 

Can we not have the CM client on our MP(s)? Do you just re-install the client on the server?

 

Thanks again.

Share this post


Link to post
Share on other sites

Thanks for the post. I think that is what is causing my MP to fail also. I will let you know.

 

A question then...

 

Can we not have the CM client on our MP(s)? Do you just re-install the client on the server?

 

Thanks again.

 

Sure you can have it on the server. We just don't manage servers in our environment, only workstations. And when I'd accidentally installed the client on the site server, and then only half-removed it, it messed things up for me. So I needed to make sure it was completely gone, hence using the good old ccmclean from SMS Toolkit 2003.

Share this post


Link to post
Share on other sites

I was having this problem as well, and this post thread got me started in the right direction. After investigating further, I found a MSKB that describes the problem and has a workaround.

 

http://support.microsoft.com/kb/2796086

 

In a nutshell, you can change a registry setting and the CCMEVAL.exe nightly task will stop breaking the MP.

 

Uninstall the MP role, change HKLM\SOFTWARE\Microsoft\CCM\CcmEval\NotifyOnly to "TRUE", reboot, and reinstall the MP role. You don't have to uninstall the CCM client from the MP server.

 

This is supposed to be fixed in SCCM 2012 SP1, but I haven't installed it yet to test.

  • Like 2

Share this post


Link to post
Share on other sites

Never mind I resolved the issue. Somehow during the installation of the new SQL instance, named pipes got shut off in MSSQLSERVER. Re-enabling named pipes and restarting the services/server solved the problem.

Share this post


Link to post
Share on other sites

I had the same issue, and my MSSQLSERVER named pipes was disabled. Re-enabling and restarging the services solved the issues for me. Maybe something to check if this issue persists with Software Center.

Share this post


Link to post
Share on other sites

Just in case the posted solution didn't work for you, like it was my case:

In my case the "BgbServer.log" log file was reporting login errors of the MP server connecting to the Database (located at a different server). Error message:

ERROR: Can't retrieve SQL connection - Cannot open database "CM_XXX" requested by the login. The login failed

The thing was that I reinstalled the MP server using the same name. In the SCCM database (CM_XXX) at SQL Server the server's account logically was already defined, but since the MP server has been reinstalled, it is a different machine (probably because SQL Server is using the machine's SID).

The solution steps I took: 

  1. Open SQL Server Management Studio and connect to the server which holds the SCCM database (CM_XXX).
  2. Browse to "Databases\CM_XXX\Security\Users"
  3. Edit the already existing MP server's account (for example "Domain\MPServer$") and take screenshots of every property (General, Owned Schemas, Membership, etc...)
  4. Delete the already existing MP server's account (do not delete it from the "Security\Logins" section, it's not necessary)
  5. Add the "Domain\MPServer$" account back to the "Databases\CM_XXX\Security\Users" section, setting the same same properties as shown in the screenshots you took in step 3.

After that, you don't have to do anything else, not even reboot, in a matter of minutes it will automatically start working and you should be able to successfully check MP status (http://<ServerName>/sms_mp/.sms_aut?mplist)

Hope this helps.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...