Support Tip: ConfigMgr 2012 Management Point fails with a 500 error after working fine for a short period of time


~ Muhammad Adil | Senior Consult-Escalation Engineer

AdilHi Everyone, hope you all are doing well! I’m writing this post regarding a recent case that was escalated to me. During my research and troubleshooting, I found a few people who were mentioning the same issue on the TechNet forum but without any resolution so I thought to write this in an effort to help anyone else who might come across the same issue.

With this issue, a System center 2012 Configuration Manager (ConfigMgr 2012) Management Point (MP) had been reinstalled several times, as was IIS as well, but still the Management Point fails after working fine for a short span of time and logs the following error in mpcontrol.log:

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER

Http test request failed, status code is 500, 'Internal Server Error'. SMS_MP_CONTROL_MANAGER 5/23/2013 2:33:47 PM 584 (0x0248) STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER

Since IIS had already been reinstalled and no AV was running on the machine, the next thing I suspected was that some Group Policy might be causing the issue. We reinstalled the MP and it showed 200 OK in mpcontrol.log. Then we ran the command gpupdate /force, and the moment we did that the MP generated our 500 error, thus I was assured that there is some GPO causing this issue

On the site server we ran the command gpresult /z >c:\result.txt. We then opened the result.txt file and found several policies, however there was one policy that I was quite skeptical about. It showed that the CCMExec service has been configured to run automatically:

GPO: Servers GPO
ServiceName: CcmExec
Startup: Automatic

I reproduced the problem in my lab and verified that if CCMExec is configured to run automatically using a GPO, the Management Point will fail in a ConfigMgr 2012 environment. It’s interesting to note that it does not fail in a ConfigMgr 2007 environment as I tested it in both.

Also note that there is a similar issue with this policy as documented in the Knowledge Base article below:

KB919592 - The Advanced Client in Systems Management Server 2003 and in System Center Configuration Manager 2007 no longer works after you deploy Windows XP Service Pack 2 (SP2) (http://support.microsoft.com/kb/919592)

So the resolution is that CCMExec (SMS Agent Host) should not be configured to run automatically using a Group Policy.

Hope this helps!

Muhammad Adil | Senior Consult-Escalation Engineer | PRO Support Middle East & India

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/


Comments (7)
  1. Robert says:

    Ms documented years ago how to use GPO with ccmexec properly. Its possible…just learn how. Not doing it because you don't know how isn't the answer….

  2. Anonymous says:

    Pingback from SCCM 2012 R2: Http test request failed, status code is 500, 'Internal Server Error'. | Deploiement Windows

  3. Anonymous says:

    Pingback from SCCM 2012 R2: Http test request failed, status code is 500, 'Internal Server Error'. | Deploiement Windows

  4. bhupalan says:

    but this happens for me in 2007 environment 🙁
    I was suppose to restore the site with the servers c: drive gone crashed earlier. so I had to rebuild the VM and restore the site and db… but this error screws me for the past 1 week…

  5. Jose Angel Rivera says:

    In my case I got it fixed by doing this:

    Gave read permission to “everyone” to the folder and all subfolders at “C:Program FilesSMS_CCMSMS_MP

    After that, got another error now 403 regarding another permissions. Followed some instructions on the error while trying to browse to the SMS_MP site and could fix it. I went to the IIS website “SMS_MP”, then selected the option “Handler Mappings” then “Edit
    Permissions”, and marked the option for “Read”. Everything seemed to work after I set that.

  6. Hi Muhamed.

    I was facing same situation in my company and I’ve checked in my environment and fix it. Great Post.
    Thanks so much for your Shared Article. 🙂

    Rodney

Comments are closed.

Skip to main content