SCCM SMP 500 error

Just stumbled across the top solution. I'm going to try it now and see if my error goes away. Seems over night the error has happen 4 times. I'll post updates if it fixes my error

@@@@@@@@@@@@@@
@@@ SOLUTION 1 @@@@
@@@@@@@@@@@@@@

Issue: MP Control fails with HTTP test request failed, status code is 500, 'Internal Server Error' on a Management Point running a 64-bit OS hosting 32-bit (x86) based IIS. The MPControl log contains the following:

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 1/23/2008 5:53:30 PM 4792 (0x12B8)
Http test request failed, status code is 500, 'Internal Server Error'. SMS_MP_CONTROL_MANAGER 4792 (0x12B8)

The IIS Logs may also show the following:

W3SVC1 192.168.0.35 CCM_POST /ccm_system/request - 80 - 192.168.0.105 ccmhttp 500 0 193
W3SVC1 192.168.0.35 CCM_POST /ccm_system/request - 80 - 192.168.1.109 ccmhttp 500 0 193
W3SVC1 192.168.0.35 GET /SMS_MP/.sms_aut MPLIST 80 - 192.168.0.35 SMS_MP_CONTROL_MANAGER 500 0 193
W3SVC1 192.168.0.35 CCM_POST /ccm_system/request - 80 - 192.168.0.61 ccmhttp 500 0 193

Browsing to http://SiteServer/SMS_MP/.sms_aut?MPlist returns a 500 as well.

Cause: This problem occurs because the ASP.NET registry keys are missing. The ASP.NET registry keys are missing when you install ASP.NET after the Enable32bitAppOnWin64 Microsoft Internet Information Services (IIS) metabase setting is set to a value of 1. Because IIS is configured to run in 32-bit mode, the ASP.NET installation does not create the ASP.NET registry keys in the 64-bit registry. The ASP.NET installation creates the ASP.NET registry keys only in the 32-bit registry.

Resolution: To resolve this problem, follow these steps for 32-bit or 64-bit mode:

To enable 64-bit mode:

1. Click Start, click Run, type cmd, and then click OK.

2. To enable the 64-bit mode, type the following command, and then press ENTER:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

3. Type the following command, and then press ENTER:

cd C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727

4. To install the 64-bit version of ASP.NET, type the following command, and then press ENTER:

aspnet_regiis -i

5. Type the following command, and then press ENTER:

iisreset

----

To enable the 32-bit mode:

1. Type the following command, and then press ENTER:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

2. Type the following command, and then press ENTER:

cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

3. To install the 32-bit version of ASP.NET, type the following command, and then press ENTER:

aspnet_regiis -i

4. Type the following command, and then press ENTER:

iisreset


@@@@@@@@@@@@@@
@@@ SOLUTION 2 @@@@
@@@@@@@@@@@@@@

In management Console I just started getting the following error:

SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error

So far the fix that works 99% of the time is as follows

1. Remove the MP role and reporting role by highlighting the roles on the server and deleting them. Check MPSetup.log to make sure it is fully uninstalled.

2. Remove IIS

3. Reboot

4. Delete the Inetpub folder (C:\inetpub) I renamed to inetpub_OLD for safety

5. Reinstall IIS - I used server management and added the application server role back. Make sure to enable WEBDAV in the IIS console under web service extentions. **ALSO** add remove windows component and make sure BITS gets installed. otherwise error 1603 will show in the MPsetup.log

6. Add back the reporting point.

7. Add back the MP role and check the box to allow clients to use the MP. Check The MPSetup.log to make sure it install is successful.

8. Watch the MPcontrol.log file. May take up to 20 minutes for the normal HTTP 200 messages to appear, but it should work and communications should resume with your clients.

So thats it. Main things to check are the logs to make sure the install and unisntalls are successful other wise other errors may occur. I usually do a search for the log files. Also make sure BITS and WEBDAV are setup correct. WEBDAV just needs to be allowed. BITS needs to be seleted