I have a Config Mgr 2007 SP2 environment running in mixed mode with a Fallback Status Point server and 3 primary sites reporting to my central primary site. All servers are 2008 Enterprise SP2 and members of the same 2003 AD forest. The FSP and the central primary site are members of the same domain within the forest. The FSP has been communicating fine with the central primary site for several months now. However after applying the latest Microsoft security and critical updates last Tuesday, I have not been getting any status messages from client installs. The smsexec log on the FSP is full of the following lines which started when the server rebooted after the updates: ERROR: Could not establish a connection to the site server using the SMS Service Connect Account. Sleeping 60 for seconds... (Yes, the 60 is before the 'for'.) Nothing has been changed with the server accounts and all the primary sites are still communicating with each other. I've verified that the FSP's server account is in the SMS_SiteSystemToSiteServerConnection group on the central site and the central site's account is in the local admin group on the FSP. It also appears that client messages are getting to the FSP because the FSPStaging directory has alot of .SMX files in it with dates ranging from 8-24-10 through today. I've search through several forums with no luck and have run out of things to check. Any help would be greatly appreciated.

what do these logs say fspisapi.log (SMS_CCM\Logs folder) on the site system server with the fallback status point role. fspmgr.log (SCCM installation\logs folder)

fspisapi.log has lots and lots of lines like this: <![LOG[Successfully processed request with connection ID = 28891360.]LOG]!><time="13:54:12.826+300" date="08-30-2010" component="FSPIsapi" context="" type="1" thread="1656" file="fspisapi.cpp:339"> <![LOG[Successfully processed request with connection ID = 28904016.]LOG]!><time="13:55:02.811+300" date="08-30-2010" component="FSPIsapi" context="" type="1" thread="2976" file="fspisapi.cpp:339"> <![LOG[Successfully processed request with connection ID = 28916704.]LOG]!><time="13:55:14.592+300" date="08-30-2010" component="FSPIsapi" context="" type="1" thread="2248" file="fspisapi.cpp:339"> <![LOG[Successfully processed request with connection ID = 28929352.]LOG]!><time="13:55:16.561+300" date="08-30-2010" component="FSPIsapi" context="" type="1" thread="2248" file="fspisapi.cpp:339"> <![LOG[Successfully processed request with connection ID = 28942008.]LOG]!><time="13:55:37.248+300" date="08-30-2010" component="FSPIsapi" context="" type="1" thread="2248" file="fspisapi.cpp:339"> <![LOG[Successfully processed request with connection ID = 28954656.]LOG]!><time="13:55:54.733+300" date="08-30-2010" component="FSPIsapi" context="" type="1" thread="2248" file="fspisapi.cpp:339"> <![LOG[Successfully processed request with connection ID = 28967304.]LOG]!><time="13:56:39.389+300" date="08-30-2010" component="FSPIsapi" context="" type="1" thread="2672" file="fspisapi.cpp:339"> fspmgr.log ends like this: CFSPManager::TransferFiles - No files need to be copied from the staging location. $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 16:53:31.789 2010 Central Daylight Time><thread=2500 (0x9C4)> CFSPManager::TransferFiles - No files need to be copied from the staging location. $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 16:54:31.789 2010 Central Daylight Time><thread=2500 (0x9C4)> Successfully copied 1 out of 1 file(s). $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 16:55:31.789 2010 Central Daylight Time><thread=2500 (0x9C4)> Successfully copied 1 out of 1 file(s). $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 16:56:31.945 2010 Central Daylight Time><thread=2500 (0x9C4)> CFSPManager::TransferFiles - No files need to be copied from the staging location. $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 16:57:32.086 2010 Central Daylight Time><thread=2500 (0x9C4)> CFSPManager::TransferFiles - No files need to be copied from the staging location. $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 16:58:32.086 2010 Central Daylight Time><thread=2500 (0x9C4)> Successfully copied 1 out of 1 file(s). $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 16:59:32.086 2010 Central Daylight Time><thread=2500 (0x9C4)> ******************************************************************************** $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 17:00:03.992 2010 Central Daylight Time><thread=2484 (0x9B4)> SMS_FALLBACK_STATUS_POINT received STOP notification. $$<SMS_FALLBACK_STATUS_POINT><Tue Aug 24 17:00:03.992 2010 Central Daylight Time><thread=2484 (0x9B4)> I see that the FSP received a STOP notification which I assume was due to the reboot. I don't know why it didn't start back after the reboot though (and I've tried rebooting it a couple of times since the updates.) Also, here is the part of the smsexec.log when the server came back up after the 8-24-10 reboot: SMS_EXECUTIVE stopped. $$<SMS_EXECUTIVE><Tue Aug 24 17:00:07.977 2010 Central Daylight Time><thread=2056 (0x808)> ******************************************************************************** $$<SMS_EXECUTIVE><Tue Aug 24 17:00:07.977 2010 Central Daylight Time><thread=2056 (0x808)> ******************************************************************************** $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> Starting SMS_EXECUTIVE... $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> Microsoft System Center Configuration Manager v4.00 (Build 6487) $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> Copyright (C) 2005 Microsoft Corp. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> Running as a Win32 service. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> Process ID: 792 $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> Worker thread ID: 1944 $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> Initialize COM Security. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> InitializeCOMSecurity: RegOpenKeyEx for appid key Succeeded. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.720 2010 Central Daylight Time><thread=1944 (0x798)> InitializeCOMSecurity: RegQueryInfoKey for appid key Succeeded. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.736 2010 Central Daylight Time><thread=1944 (0x798)> InitializeCOMSecurity: RegQueryValueEx for AccessPermission Succeeded. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.736 2010 Central Daylight Time><thread=1944 (0x798)> InitializeCOMSecurity: IsValidSecurityDescriptor() Succeeded. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.736 2010 Central Daylight Time><thread=1944 (0x798)> InitializeCOMSecurity: MakeAbsoluteSD() Succeeded. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.736 2010 Central Daylight Time><thread=1944 (0x798)> InitializeCOMSecurity: CoInitializeEx() Succeeded. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.736 2010 Central Daylight Time><thread=1944 (0x798)> InitializeCOMSecurity() Succeeded.~ $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.752 2010 Central Daylight Time><thread=1944 (0x798)> Installation directory: C:\SMS $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.752 2010 Central Daylight Time><thread=1944 (0x798)> This server: SCCMFSP $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.752 2010 Central Daylight Time><thread=1944 (0x798)> Site server: SCCM $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.752 2010 Central Daylight Time><thread=1944 (0x798)> Site code: CP1 $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.752 2010 Central Daylight Time><thread=1944 (0x798)> ERROR: Could not establish a connection to the site server using the SMS Service Connect Account. $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.892 2010 Central Daylight Time><thread=1944 (0x798)> Sleeping 60 for seconds... $$<SMS_EXECUTIVE><Tue Aug 24 17:02:13.892 2010 Central Daylight Time><thread=1944 (0x798)> ERROR: Could not establish a connection to the site server using the SMS Service Connect Account. $$<SMS_EXECUTIVE><Tue Aug 24 17:03:13.892 2010 Central Daylight Time><thread=1944 (0x798)> Sleeping 60 for seconds... $$<SMS_EXECUTIVE><Tue Aug 24 17:03:13.892 2010 Central Daylight Time><thread=1944 (0x798)>

ERROR: Could not establish a connection to the site server using the SMS Service Connect Account. $$ Have you already checked that?

If my understanding is correct, the SMS Service Connect Account is the server account, such as domain/server$. The server account of the FSP server is in the SMS_SiteSystemToSiteServerConnection group on the central site server. And the central site server's account is a local admin on the FSP server. I don't know of anything else to check. Is there some way to verify that the FSP is using it's server account to connect to the central site server? I've checked the security log on the central site server and I don't see any failures for FSP's account. The FSP has been working fine for several months before the last Microsoft updates were applied. I haven't changed anything with the accounts since the SCCM infrastructure was built several months ago. The Windows firewalls are turned off and the FSP and the central site server are in the same IP range as well as the same domain. I've thought about deleting and then re-adding the FSP role but I don't want to lose all the status messages which are getting queued up on the FSP. Anything you can suggest to help would be greatly appreciated.

Hmm... wierd.. Just curious if you already tried site reset. and restart the sccm server

I didn't do a site reset because I've never done that before and it sounds kind of scary to me because there are a lot of configuration settings I don't want to lose. I restarted the sccm server after applying the patches but I haven't restarted it since then. So I just now restarted it, and magic, the FSP is communicating again. YES!!! Thanks Vamsi Varma Ganaraju!!! Now the question is why it took more than 1 restart to get everything in the SCCM world going? Oh well, the world may never know. :)