| Author |
Message |
tdietrich
Joined: 04 May 2012
Posts: 8
|
 Posted: Mon Jun 18, 2012 2:21 pm Post subject: Error monitoring Clustered SQL server |
 |
|
Getting the error: Unreachable (Cannot connect)
The log reads as follows:
18 Jun 2012 9:12 AM SQL Ping Connected
18 Jun 2012 9:12 AM Registry OpenRegistryHive: PerformanceData Cannot connect Win32Exception The network path was not found
18 Jun 2012 9:12 AM Registry OpenRegistryHive: LocalMachine Cannot connect Win32Exception The network path was not found
What is the typical cause of this issue? We've got two two box clusters configured in similar fashions, and one works while the other shows this error. |
|
| Back to top |
|
 |
tdietrich
Joined: 04 May 2012
Posts: 8
|
|
| Back to top |
|
|
Brian Donahue
Joined: 23 Aug 2004
Posts: 6369
Location: Red Gate Software
|
| Posted: Wed Jun 20, 2012 3:41 pm Post subject: |
|
|
SQL Monitor wants to get data from the cluster node rather than the IP address configured as the cluster resource.
When you add a cluster to SQL Monitor, it's importand to specify the server using the node name. It works best to just add all instances. Say you have a cluster with two nodes, NODEA and NODEB. You would add NODEA\*. SQL Monitor will query the registry of NODEA to work out all of the other participating nodes and configure the remote registry, SQL, and WMI connections accordingly.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521 |
|
| Back to top |
|
|
tdietrich
Joined: 04 May 2012
Posts: 8
|
| Posted: Thu Jul 12, 2012 8:49 pm Post subject: Fixed it |
|
|
The issue was isolated to a configuration setting preventing connections to the remote registry at the SQL cluster's address.
Our network administrator found the solution: http://social.technet.microsoft.com/Forums/eu/configmgrsetup/thread/8b4a2246-1cff-4d31-9513-c1239c1e694b
| Quote: |
Of the tests we conducted above the root cause of the short file name error during the Pre-req checks was found to be the fact that we were not able to remotely access the registry using the SQL Virtual name which we should have been able to do. On contacting Microsoft Support we were informed that there are known issues around NoRemap registry key needing to be set if you are using Network Name resource that is dependent on a separate new IP Address resource – see http://support.microsoft.com/?id=306985
The final solution was to add a new REG_MULTI_SZ registry key to BOTH cluster nodes called:-
NoRemapPipes to:-
HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\
This key should contain the values of:-
WINREG
EVENTLOG
svcctl
After adding the above key and values we needed to reboot both cluster nodes and then we were able to connect to the SQL Virtual names (CLUSQL02 + CLUSQL01) using Regedit (Remote registry). Running the SCCM Pre –req checker now returns no errors.
Hope this soluton helps someone else. |
|
|
| Back to top |
|
|
|
|
All times are GMT + 1 Hour
|
| Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
