Greetings, I am having an issue with my SQL server site system; where I get a daily error message that says: SMS Site Component Manager could not access site system \\SQLServer. The operating system reported error 2147942464: The specified network name is no longer available. The subsequent messages say: Because site system "\\SQLServer" might have malfunctioned, as a safety measure SMS Site Component Manager will attempt to reconfigure it to receive SMS server components and reinstall all of the SMS server components on it. This attempt will occur in 60 minutes. and SMS Site Component Manager successfully reconfigured site system "\\SQLServer" to receive SMS server components. SMS Site Component Manager will now begin reinstalling the components on the site system. This seems to be happening once a day every day like clockwork. I checked our network logs, and the server has been up for weeks. I checked to make sure that the Site Server's computer account is an administrator of the SQL server. Every client agent I have setup so far seem to be working properly. I am getting hardware and software inventory information. Is there anything else I should be lookingat? Has anyone seen this before?

DeeKM wrote: SMS Site Component Manager could not access site system \\SQLServer. The operating system reported error 2147942464: The specified network name is no longer available. [...] This seems to be happening once a day every day like clockwork. I checked our network logs, and the server has been up for weeks. That's not really a ConfigMgr related problem ("The operating system reported error 2147942464"). You should check other things that are going on at the same time. Maybe there's backup running (that stops services or overutilizes the LAN) or some other jobs ...

Torsten, It looks like there is a backup running at about the same time that the error occurs.I'm going to call this one closed and I'll post back any other info that might be useful. Thanks for the reply.

I am having this exact same issue but we do not have backups running at the time the error occurs. I know that it is a scheduled process that is causing the issue though. The error occurs every ten hours on the nose. I have checked the Task Scheduler for anything that might be running every ten hours and cannot find anything. I have checked all of the Site Maintenance settings, Discovery Methods, Component Configurations, even Collection Intervals and can find nothing that kicks off every 10 hours. There is nothing in the event logs on the site server or the database server that indicates any issues at the time the error occurs. Fortunately I know exactly when the next error is going to occur. Unfortunately I am not sure what to look for. Any ideas?

I ended up having the SQL administratorrebooteach node of the SQL cluster after hours. This appears to have fixed the issue. We have not had a reoccurrence for 16 days now. These nodes had not been restarted since before SCCM was installed. When we first installed SCCM there were no issues and no errors but a couple of months after the install we started to get the "could not access site system" errors for the SQL cluster. I can only assume that some change was made on the SQL cluster that started the errors and that the reboots took care of the problem. My hunch is that it had something to do with Kerberos and SPNs but I cannot verify that at this point.