We have setup and installed our top level SCCM Primary Site server and this is configured with a remote SQL clustered database. Our database administrators created a specific SQL instance for SCCM and this is located on a SAN drive.The SCCM Admin console loads successfully and all functionality is fine. With the database on the active node,I can look at the Site status/Site system status, and can see the 'green ticks/OK' symbols on all the SCCM Site components, so everything looks good. Even the passive node of the cluster is showing as green/OK.However,when the database fails over and the passive node becomes the active one, I then receive lots of errors in the Site system status. The console loads ok and the active node is showing as successful. The passive node then shows as 'Red/Critical' with the error message:-SMS Site Component Manager could not read the write SMS Server Network Connection account data to the SMS server components installation directory R:\SMS_WG2WDS06 on site system \\WG2CLU12. Error 64 reported. (R: is a SAN drive and WG2CLU12 is the passive node)This problem is not stopping the console being used but it obviously generates quite a few error messages. Can anyone advise how to resolve this issue please??? It only appears to happen in one of the two scenarios. If the database is failed back to the original cluster node, then the new passive node seems fine and doesn't generate errors. To me it seems like a SQL problem rather than SCCM butour database experts claim nothing is wrong with the two SQL nodes!Thanks

Is the serve account for your ConfigMgr server an administrator on both nodes of the cluster?Jason | http://myitforum.com/cs2/blogs/jsandys

Risk01 said: Error 64 reported. Error 64 translates to "The specified network name is no longer available". This might give you another hint to start troubleshooting.

Yes,the SCCM Site server account is a member of the Administrators group on each cluster node.

I understand that something is not available, that's whyerrors are being generated. It just seems very odd that it only happens when one of the nodes is passive and not then other way round. I'm assuming the Site server is trying to access something on the SAN drive that is no longer availble to the passive node, which in turn causes the errors. However, if the database fails over and the other node is passive, then the errors do not occur and the new passive node wouldn't be able to access the SAN drive as it would be attached to the active node.

As you rightly said, Risk01, the errors come up for the passive node as those resources are not available to Configmgr as Configmgr is using the active node. If and when the cluster fails over to the passive node (and it becomes active) the errors will stop and may show up for the other node.

But this is my point....In one situation, the passive node creates errors because something is not available. However, if the cluster fails over, the new passive node does not generate the errors. Something is different and I do not know if it is an SCCM problem or a SQL problem. My Database administrators assure me it is not SQL but I do not have the SQL knowledge to question them. As it only happens in one situation and not both, I would personally say it was more to do with SQL, but it might still be related to the setup of SCCM with the remote SQL cluster.

Its seems its old Post I think you already solved it J but I like to share my resolution in case someone face it in the future, Its seems it’s was little bit miss planning on cluster node, 1- Create NO_SMS_ON_DRIVE on all shared storage to be sure that the sccm site component is installed on local drive 2- Open the regedit and connect sms\components\site component manager\multisite components\WG2WDS06 3- Installation Directory change it to local C:\SMS_WG2WDS06 4- Restart SMS_SITE_COMPONENT_MANAGER 5- see the status messages again and monitoring