Hello - Yes, You should try RESTART that is not at all a bad idea. Make sure there is no connectivity (WAN) issue between secondary servers and primary site.Anoop C Nair

Check the SQL server logs using SQL management studio.Torsten Meringer | http://www.mssccmfaq.de

I have a primary site and nine secondary sites all running SCCM 2007 SP2 R2. 5 of the secondary site MPs are working properly, the other 4 are all failing to connect to the SQL database. I've been going down the list of possible causes, but I'm not making any headway. #1 - SQL server is turned off, net connected, or not functioning properly. It's on, connected and functioning properly. #2 - MP does not have sufficient access. I have verified that all of my secondary site servers are members of the msdbrole_MP within the database. #3 - Network problems. Could this include rate limits imposed on the SCCM addresses? Not all of the addresses that have rate limits are failing, but all but one of the failing MPs have rate limits imposed (25% of connection bandwidth) #4 - SQL access account was recently reset. I'm not sure what account this is referring to, but the MPs have been having this problem for some time. I can't promise the ever really worked. I've also rebooted one of the secondary site servers, so the SMS_SITE_COMPONENT_MANAGER has been restarted. #5 - SPNs are not registered correctly. I ran setspn -l <computeraccount> (I'm using the Local System account to run SQL), but I don't know what I'm looking for. SetSPN returned (among other SPNs: MSSQLSvc/<FQDN_for_sqlserver> MSSQLSvc/<FQDN_for_sqlserver>:1433 I have also verifed that the computer account for each of my secondary site servers in a member of the SMS_SiteSystemToSiteServerConnection_<site> and SMS_SiteToSiteConnection_<site> groups on the primary site server.

Configure the SQL service accounts to run under Local System and restart the SMS services. This is just to verify that the SPN/Service accounts is causing the problem.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Are these new DP's? The two main causes I've seen is overloaded SQL (especially when running on VM) or SQL permissions. Does MPCert work but MPList fail? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Both MPCert and MPList work. What are the odds that rebooting my primary site server would help?

I had every intention of rebooting last night, but forgot SQL Logs - great suggestion. My SQL Server log is riddled with messages "Login failed for user ...Reason: Token-based server access validation failed with an infrastructure error. I've seen a lot of posts about this error (only a few SCCM-specific). Most blame it on UAC. I'm doubtful.

I have rebooted both the primary and one of the secondary sites, but I'm still having the same problem. I have also removed the SQL login for the secondary and recreated it, but I'm still getting the same error.

I wasn't patient enough after recreating the SQL login for my MP. I looked that next day and the MP was working. I deleted and recreated the other non-functional logins and now all of my MPs are working. Some of the DCs in my remote offices had been replaced recently. I'm wondering if the logins didn't get removed from SQL, causing a token mismatch when they came back on line.