Hallo,I have SCCM 2007 RTM everything is working, but i get this error from Component 'SMS_State_Migration_Point': SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base.The IIS is working, for example SMS-Reporting. Where do i configure the ports SMS communicate with IIS?ThanksAndreas Scheer

Andreas, the error you are getting is an internal server error. Can you verify you have configured the SMP server role correctly (i.e the Share created is accessible by the machine SMP is installed). You can also look at the smpisapi.log on the machine where SMP server role is installed, it will give you exact information why the requests are failing.The log file will usually be in the SMS_CCM\logs folder, if its colocated with a client it will be in %windir%\system32\CCM\logs folder. Thanks, Srikanth

Thanks for your answer, but in the Log file also: "...500... internal server error..."...Perhabs its just an error of the iis, this virtual machine I've used for some tests before.I reinstall Windows and SCCM, and it works...ThanksAndreas

I have the same error. SMP is working perfectly. I can migrate the User State without any problems. But every day I get this error. See my smpisapi log file: AddACE to store with access account DOMAINNAME\SMSSERVER$ failed for directory \\SMSSERVER\SMPSTOREE_237B7A0D$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 Revoke access failed for directory \\SMSSERVER\SMPSTOREE_237B7A0D$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 StatusRequest::UpdateStatus failed with errorcode (0x80070035) StatusRequest::HandleMessage failed with errorcode (0x80070035)] Failed to process CAPTURESTATUS request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB SMPRequestHandler::HandleMessage for StoreOp CAPTURESTATUS failed with server errorcode 99 HealthCheckRequest::HandleMessage failed with errorcode (0x80040063) Failed to process HEALTHCHECK request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB SMPRequestHandler::HandleMessage for StoreOp HEALTHCHECK failed with server errorcode 99 Returning status "500 Internal Server Error The folder specified in the log file does't exist on my State Migration Point. Actually when I manually create this folder in the share the folder is eventually deleted if I restart the SMS services. After a couple of minutes the error disapears and everything is Ok. Creating state store - E:\SMS_OSD\MigData\UserState\SMPSTOREE_237B7A0D$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 Statestore - E:\SMS_OSD\MigData\UserState\SMPSTOREE_237B7A0D$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 exists Returning status "200 OK" The status message is saying: SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base. IIS is listing to correct SMS ports SMSWEB is enabled (Using port 9090) Anybody a solution?

I am also seeing the exact same error as Tom. My environment is a clean SCCM 2007 install with the State Migration Point role installed on the Primary Site Server.Thanks,Brian

The error code is "Network Path not found". The folder should automatically be created and deleted, everytime it processes the HealthCheck request. That explains the dissapearence of the folder after the service is restarted. This is basically to determine if the ISAPI is in healthy condition.Tom, can you attach the smpisapi.log, I would like to investigate it further to determine this odd behavior.Thanks,Srikanth

Srikanth, I am experiencing the same issue as Tom. Here is an excerpt from my smpisapi log: ========== GetExtensionVersion ========== smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) SMPRequestHandler::Initialization started. smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) SMS Sitecode = 001 smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) Inserted store "d:\SMP\" to cache smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) Inserted store "D:\SMP\" to cache smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) Initialization of SMP store completed smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) Started SMPStoreMgr worker thread smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) SMPStoreMgr is now initialized smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) Initializing smpPerfObject. smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) smpPerfObject initialization complete. smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0) ========== BEGIN: HttpExtensionProc ========== smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) Query string to parse: 'op=healthcheck'. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) Creating state store - D:\SMP\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) Statestore - D:\SMP\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 exists. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) SecureAccess failed with error code (80070005) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) AddACE to store with access account domain.com\HOST$ failed for directory \\domain.com\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) Revoke access failed for directory \\domain.com\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) StatusRequest::UpdateStatus failed with errorcode (0x80070005) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) StatusRequest::HandleMessage failed with errorcode (0x80070005) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) Failed to process CAPTURESTATUS request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) SMPRequestHandler::HandleMessage for StoreOp CAPTURESTATUS failed with server errorcode 99 smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) HealthCheckRequest::HandleMessage failed with errorcode (0x80040063) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) Failed to process HEALTHCHECK request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) SMPRequestHandler::HandleMessage for StoreOp HEALTHCHECK failed with server errorcode 99 smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) Returning status "500 Internal Server Error" smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) ========== END: HttpExtensionProc ========== smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)

Anyone find a solution to this yet? I am having the exact same issue, getting status '500 Internal server error' ever hour, with status 'ok 200' in between Here is some of the smsisapi.log to help: Code Block <![LOG[========== BEGIN: HttpExtensionProc ==========]LOG]!><time="08:46:02.857+-660" date="01-02-2008" component="smpisapi" context="" type="0" thread="4188" file="smpisapi.cpp:402"><![LOG[Query string to parse: 'op=healthcheck'.]LOG]!><time="08:46:02.857+-660" date="01-02-2008" component="smpisapi" context="" type="1" thread="4188" file="smpisapi.cpp:157"><![LOG[Creating state store - f:\SMP\SMPSTOREf_C9F8818A$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.]LOG]!><time="08:46:02.873+-660" date="01-02-2008" component="smpisapi" context="" type="1" thread="4188" file="smprequesthandler.cpp:1236"><![LOG[Statestore - f:\SMP\SMPSTOREf_C9F8818A$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 exists.]LOG]!><time="08:46:02.873+-660" date="01-02-2008" component="smpisapi" context="" type="2" thread="4188" file="smprequesthandler.cpp:1248"><![LOG[SecureAccess failed with error code (80070035)]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smputil.cpp:414"><![LOG[AddACE to store with access account nccma.vic.gov.au\HQNCMSA$ failed for directory \\server.domain.com\SMPSTOREf_C9F8818A$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:915"><![LOG[Revoke access failed for directory \\server.domain.com\SMPSTOREf_C9F8818A$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:1998"><![LOG[StatusRequest::UpdateStatus failed with errorcode (0x80070035)]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:2004"><![LOG[StatusRequest::HandleMessage failed with errorcode (0x80070035)]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:1635"><![LOG[Failed to process CAPTURESTATUS request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:303"><![LOG[SMPRequestHandler::HandleMessage for StoreOp CAPTURESTATUS failed with server errorcode 99]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:309"><![LOG[HealthCheckRequest::HandleMessage failed with errorcode (0x80040063)]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:2081"><![LOG[Failed to process HEALTHCHECK request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:303"><![LOG[SMPRequestHandler::HandleMessage for StoreOp HEALTHCHECK failed with server errorcode 99]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="3" thread="4188" file="smprequesthandler.cpp:309"><![LOG[Returning status "500 Internal Server Error"]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="1" thread="4188" file="smpisapi.cpp:248"><![LOG[========== END: HttpExtensionProc ==========]LOG]!><time="08:46:09.732+-660" date="01-02-2008" component="smpisapi" context="" type="0" thread="4188" file="smpisapi.cpp:481"><![LOG[========== BEGIN: HttpExtensionProc ==========]LOG]!><time="08:51:02.859+-660" date="01-02-2008" component="smpisapi" context="" type="0" thread="4188" file="smpisapi.cpp:402"><![LOG[Query string to parse: 'op=healthcheck'.]LOG]!><time="08:51:02.859+-660" date="01-02-2008" component="smpisapi" context="" type="1" thread="4188" file="smpisapi.cpp:157"><![LOG[Creating state store - f:\SMP\SMPSTOREf_C9F8818A$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.]LOG]!><time="08:51:02.859+-660" date="01-02-2008" component="smpisapi" context="" type="1" thread="4188" file="smprequesthandler.cpp:1236"><![LOG[Statestore - f:\SMP\SMPSTOREf_C9F8818A$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 exists.]LOG]!><time="08:51:02.859+-660" date="01-02-2008" component="smpisapi" context="" type="2" thread="4188" file="smprequesthandler.cpp:1248"><![LOG[Returning status "200 OK"]LOG]!><time="08:51:02.890+-660" date="01-02-2008" component="smpisapi" context="" type="1" thread="4188" file="smpisapi.cpp:248"><![LOG[========== END: HttpExtensionProc ==========]LOG]!><time="08:51:02.890+-660" date="01-02-2008" component="smpisapi" context="" type="0" thread="4188" file="smpisapi.cpp:481">

All, I am seeing the same error message as well...I don't suppose anyone has happened upon a solution? I can't reinstall windows and SCCM at this point. Thanks, Andrew

Srikanth (or anyone on the OSD team), I to am expierencing the same issue on my customer's new production install. Our SMP however is on a separate site system running just the SMP, PSP and DP roles. The status message from ConfigMgr states the following: Code BlockSMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base. The error is logged once per hour and I found the SMPISAPI.LOG just were you said it would bein the \SMS_CCM\Logsdirectory Code Block========== BEGIN: HttpExtensionProc ==========smpisapi1/16/2008 9:14:15 AM2108 (0x083C)Query string to parse: 'op=healthcheck'.smpisapi1/16/2008 9:14:15 AM2108 (0x083C)Creating state store - E:\StateMigData\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.smpisapi1/16/2008 9:14:15 AM2108 (0x083C)Statestore - E:\StateMigData\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 exists.smpisapi1/16/2008 9:14:15 AM2108 (0x083C)SecureAccess failed with error code (80070033)smpisapi1/16/2008 9:14:16 AM2108 (0x083C)AddACE to store with access account <Domain.com>\<SiteSystem>$ failed for directory \\<SiteSystem.domain.com>\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.smpisapi1/16/2008'>file://\\\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473">\\<SiteSystem.domain.com>\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.smpisapi1/16/2008 9:14:16 AM2108 (0x083C)Revoke access failed for directory \\<SiteSystem.domain.com>\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.smpisapi1/16/2008'>file://\\\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473">\\<SiteSystem.domain.com>\SMPSTOREE_C31CECEC$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.smpisapi1/16/2008 9:14:16 AM2108 (0x083C)StatusRequest::UpdateStatus failed with errorcode (0x80070033)smpisapi1/16/2008 9:14:16 AM2108 (0x083C)StatusRequest::HandleMessage failed with errorcode (0x80070033)smpisapi1/16/2008 9:14:16 AM2108 (0x083C)Failed to process CAPTURESTATUS request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFBsmpisapi1/16/2008 9:14:16 AM2108 (0x083C)SMPRequestHandler::HandleMessage for StoreOp CAPTURESTATUS failed with server errorcode 99smpisapi1/16/2008 9:14:16 AM2108 (0x083C)HealthCheckRequest::HandleMessage failed with errorcode (0x80040063)smpisapi1/16/2008 9:14:16 AM2108 (0x083C)Failed to process HEALTHCHECK request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFBsmpisapi1/16/2008 9:14:16 AM2108 (0x083C)SMPRequestHandler::HandleMessage for StoreOp HEALTHCHECK failed with server errorcode 99smpisapi1/16/2008 9:14:16 AM2108 (0x083C)Returning status "500 Internal Server Error"smpisapi1/16/2008 9:14:16 AM2108 (0x083C)========== END: HttpExtensionProc ==========smpisapi1/16/2008 9:14:16 AM2108 (0x083C) If I'm reading the log file correctly, it appears to be trying to add an ACE to the folder for the site system itself that is hosting the SMP. The machine account cannot be denied batch logon rights that I know of and none of the other solutions suggested by the status message appear to be the culprit. Can you or anyone else on the OSD team help us out and if not provide a solution give us some more info on what the problem is and what could be causing it?? Thank you so much for your time.

Can you connect to the SMP share from the SMPmachine using the fully qualified domain name (FQDN)? E.G. "net use \\<SiteSystem.domain.com>\SMPSTOREE_C31CECEC$"

Also, can you try turning on debug logging on the SMP machine by creating the debug key at: HKLM\SOFTWARE\Microsoft\CCM\Logging\debuglogging

Bryce, I verified that I connect to the share using the FQDN from the primary site server by opening a CMD window on the primary site server using AT to run CMD as the localsystem. I mapped it as a drive and navigated to the migrationstatus.xml file and opened it using notepad to verify that the correct ACL's were in place. I then enabled debug logging and I have a lot of PXE related logs in the SMS\LOGS directory now. Do I need to stop and restart the STATE_MIGRATION_POINT? What exactly am I looking for?? Thanks a million for all your help

Bryce (or anyone else on the OSD team), Which log file is put into debug mode by the debuglogging key? What should I be looking for as a clue to my SMP problem? Please let me know.

I had similar problems with the SMP - continually failed on the healthcheck. Finally I realised that I was using the Netbios name of the server to connect to the store share, but SCCM was using the FQDN. When I tried to use the FQDN, I couldn't connect to the share either. I removed the FQDN from the site system in the console, restarted SCCM and everything is now happy.

THX I removed the FQDN from the site system in the console, restarted SCCM and everything is now happy.This is right!

Wow, I had been working on this problem for months now. Prairie was right on. Remove the checkbox from FQDN on the site system and green checkmarks filled my console. Errors are gone and it's Christmas morning for me! Thanks Prairie!

I'm seeing the exact same problem, but its reversed. If I try to connect to the netbios name, it fails, get the error about being out of storage space. If I try the FQDN it works. The MigrationStatus.xml says it is sucessfull. When I go into ConfigMgr site system Properties, both of the FQDN (intranet and internet are blank). [The Name is \\netbios; sitesytem type: Windows NT Server] If I restart the server I am good for about 3 days then I have the problem again.

I had the same issue and resolved this as follows: Goto the state migration folder\share on the server. Right click on the share and grant the computer account for the SMP Full Control on the Security Tab. Do this on the share example SMPSTOREE_891164CE$ You should see the following message confirming that state migration point is working. SeverityTypeSite codeDate / TimeSystemComponentMessage IDDescriptionInformationMilestoneWRE09/05/2008 11:00:00WREMFP01SMS_STATE_MIGRATION_POINT4629SMS Component Status Summarizer detected that the availability of component "SMS_STATE_MIGRATION_POINT" on computer "WREMFP01" has changed to Online.

I tried that, and it didn't work...

I did one other step. In the parent folder to the sharw where the SMP is located, grant the Network Service Full Controll ACL permissions to the parent. This fixed the issue for me on a Seconary Site what was installed on a DC that was assigned a SMP. If your environment is differnet i.e. its a SDP only, then try adding the SDP computer account to the SiteToSiteConnection local group on the Primary Site Server. You will need to purge the kerberos ticket on the server/or reboot. Hope this helps

Hi, I gave that a try and no luck... I just have a really, really small test environment, a single site with 5 computers.... I'm not sure its so much a SMP issue, as everything on this server is error'd, and I get the errors if I go to \\netbios\anyshere but if I goto \\my.fqdn.com\anyshere it works... Also weird, is if i go into the sessions on the server, I see hundreds of open sessions from computer localhost (127.0.0.1) and as the user of SCCM.... All the connections are idle between 7 days and 5 minutes to 10 days 5 minutes... The SMP is the only thing that i see in the event log as a problem, and that is the 6207 event.... I've been holding out to install SP1 once its RTM... which should be soon... Event Type:ErrorEvent Source:SMS ServerEvent Category:SMS_STATE_MIGRATION_POINTEvent ID:6207Date:5/9/2008Time:2:08:13 PMUser:N/AComputer:ATHENADescription:On 05/09/08 14:08:13, component SMS_STATE_MIGRATION_POINT on computer ATHENA reported: SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp....

Hi, I have double-checked my resolution and it definately works. Resolution 1. Right-click and properties, then securityof the Parent folder name of the SMP. 2. Click Add, and Type LOCAL SERVICE. Grant Full Control 2. Click Ok to close Properties. 3. Next, Double-click or naviagate to the folder within the Parent SMP (i.e. SMPSTORED_05ACDFF6$ something like this) 4. Right-clikc and Sharing and Security 5. Click Security and add the local Computer account with Full Control. Stop and start the smsexective service on the SMP. Verify the followingsmpmgr.log Error Message Creating share SMPSTORED_05ACDFF6$ succeededSMS_STATE_MIGRATION_POINT12/05/2008 10:25:192936 (0x0B78)AllowSMPIsapiAccess succeeded for share D:\StateMigration\SMPSTORED_05ACDFF6$.SMS_STATE_MIGRATION_POINT12/05/2008 10:25:192936 (0x0B78)SMPPeriodicActivityInterval = 60 minutesSMS_STATE_MIGRATION_POINT12/05/2008 10:25:192936 (0x0B78)Handling SMP registry Changes succeeded.SMS_STATE_MIGRATION_POINT12/05/2008 10:25:192936 (0x0B78)Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server ErrorSMS_STATE_MIGRATION_POINT12/05/2008 10:25:372936 (0x0B78)Health check request failed, status code is 500, 'Internal Server Error'.SMS_STATE_MIGRATION_POINT12/05/2008 10:25:372936 (0x0B78) Success Message Successfully initialized COpsMgmtComponent object for component 'SMS_STATE_MIGRATION_POINT'.SMS_STATE_MIGRATION_POINT12/05/2008 10:55:213876 (0x0F24)Configuration and Availability Monitor thread started.SMS_STATE_MIGRATION_POINT12/05/2008 10:55:213876 (0x0F24)Initialized 'SMS Server Availability' performance instance => SMS State Migration Point.SMS_STATE_MIGRATION_POINT12/05/2008 10:55:213876 (0x0F24)Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OKSMS_STATE_MIGRATION_POINT12/05/2008 10:55:523876 (0x0F24)Health check operation succeededSMS_STATE_MIGRATION_POINT12/05/2008 10:55:523876 (0x0F24) It works, give it a go.

Hey, Gave it a try, and it didn't help... this is post stop/start of sms_executive service. Machine name is 'athena.my.domain.ca'. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>CryptVerifyCertificateSignatureEx returned error 0x80090006. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Certificate has "SSL Client Authentication" capability. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Select first cert flag is set, choosing the first certificate valid for ConfigMgr usage. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Call to HttpSendRequestSync failed for port 443 with status code 500, text: Internal Server Error $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.328 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Health check request failed, status code is 500, 'Internal Server Error'. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.328 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Completed availability check on local machine $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.328 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Initialization still in progress. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:09.328 2008 Mountain Daylight Time><thread=8048 (0x1F70)>The 'Certificate Store' is empty in the registry, using default store name 'MY'. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' of 'Local Computer' store. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>The 'MY' of 'Local Computer' store has 3 certificate(s).~Using custom selection criteria based on the machine name. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Machine name is 'athena.my.domain.ca'. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>CryptVerifyCertificateSignatureEx returned error 0x80090006. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Certificate has "SSL Client Authentication" capability. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Select first cert flag is set, choosing the first certificate valid for ConfigMgr usage. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.281 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Call to HttpSendRequestSync failed for port 443 with status code 500, text: Internal Server Error $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.313 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Health check request failed, status code is 500, 'Internal Server Error'. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.313 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Completed availability check on local machine $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.313 2008 Mountain Daylight Time><thread=8048 (0x1F70)>Initialization still in progress. $$<SMS_STATE_MIGRATION_POINT><Mon May 12 08:33:39.313 2008 Mountain Daylight Time><thread=8048 (0x1F70)>

Its appears that you are in Native Mode, our deployment was using mixed mode (i.e advanced security model in SMS 2003). Its possible that you might have issues with a) certfiicate, b) management point iis related). Have you assigned and configured the certificate to all site servers? Sorry I have not deployed a site yet using Native Mode.

Correct, we are in native mode... I don't believe that it is an issue with the certificate.... IIS has the correct certificate for the FQDN, and as there is only the one site server, it has the certificate... The certificate has the enhanced key usages of client and server authentication. The error I have in the app event log, goes back to the issues unable to connect using \\netbios\share, while \\fqdn\share works.... SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base. When i connect to IIS, it is successful, and shows the correct certificate. All the site system status is in a failed state all with errors along the lines of: SMS Site System Status Summarizer still cannot access storage object "\\ATHENA\C$\Program Files\Microsoft Configuration Manager" on site system "\\ATHENA". The operating system reported error 2147943530: Not enough server storage is available to process this command. Possible cause: The site system is turned off, not connected to the network, or not functioning properly.Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object.Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system and access the storage object. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the site system.Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend on using it as a site system any more.Solution: Remove the site system from the list of site systems used by this site; this list appears under Site Systems in the SMS Administrator console. Possible cause: You accidentally deleted the storage object or took the storage object out of service.Solution: The SMS components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other SMS components to verify that this occurs properly. The storage object has been inaccessible since "5/9/2008 5:00:02 PM". When you correct the problem and SMS Site System Status Summarizer successfully accesses the storage object, SMS Site System Status Summarizer will set the storage object's status to OK, providing that the storage object has sufficient free space. I'm wondering if i should create a new post for my whole issue.

Hope this helps Can you confirm that you have 3 certificates created. Should have the following types. 1. Document Signing - Primary Site, subject field must contain "The site coee of this site server is XXX" 2. Server Authentication (use web server template) use for MP, DP, SUP, SMP, Site System 3. Client Authentication (Computer template), use for client communication A trustred root certificate configured for Site Server MP DP SUP SMP All Client computers In addition you will need to configure the clients to communicate on port 443. There is a WMI script you can use to configure this. Port 80 can be used as a fallback.

1) check... friendly name is name of site... setup requires this before it can continue 2) check... friendly name is the FQDN 3) check... see number two... also a dedicated one issued to the FQDN. I have Server 2003 enterprise as the root certificate, with auto-enrollment, etc. the root certificate is in the trusted root certificates on all computers. the above certs are all from that PKI and can be found in the SCCM local computers personal certificates.

And you assigned the web certificate to the various roles in IIS. MP, SMP? Icant think of anything else soundslikeyou did everything right. For the web certificate also confirm that you granted permission for the Site Server i.e. group: Read, Enroll, and Autoenroll Everything is pointing at a certficate issue more than SCCM. Sorry dude...

I've had this problem for the last few days now only on my secondary sites which are spec'd as follows: SCCM 07 Server 2003 SP2 x64 running onVMWare I have tried everything in the abovethreads including: checking permissions on the data drive as well as the SMP Share uninstalling IIS verifying all IIS settings certificate settings All other server components worked fine, MPControl was reporting a status of 200 meanwhile the SMPMGR.log and the SMSISAPI.log were reporting errors. I was getting internal server error 500 in the SMPMGR.log and AddACE to store with access account domain\server$ failed for directory \\Server.Domain.COM\SMPSTOREF_2B33F290$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. What I finally did was changed the binding order on the NIC card on the server: Right click my network places - hit advanced on the file menu - Advanced Settings... - verify that your production NIC is first in the binding order. If not move it up to the first place. Reinstall SMP with FQDN. Only after doing this and reinstalling the SMP with FQDN did this work and all logs are clean reporting 200 status.

Installed Sp1, and it resolved the issue for me.

I resolved the issue with a similar method before finding your post. I simply added the everyone group to the SMP parent folder and gave it modify rights to verify the folder security was the problem. This solved the problem but left me with a security issue. After finding your post I switched to Local Service and both problems were resolved. It seems odd that the install process for the State Migration Point would not set the security of a folder it creates correctly.

In my case, I have found the errors stopped after I went into my Site Systems -> ConfigMgr state migration point Properties and examined the folder settings for where client state data is stored. I had a folder setting that was set to 10 GB minimum free space, and the drive it was on was down to 8 GB. After dropping the required minimum free space to 5GB, the errors ceased to occur. Strange that it didn't really give any indication that this could be the issue, however, that cleared up the errors. I notice others above had posted or noted space issues, I recommend trying this perhaps.