December 15, 2008 at 7:12 am
Good afternoon
I've given a problem to resolve and at present I can't see a resoulution other than a re-install of SQL server.
We have a sql server 2005 instance installed as a failover cluster , unfortunatley a collegue has managed to delete the sql server cluster resource.JHe then tried to add the resource back manually but naturally that doesnt work.
he the tried to start the sql server service manually outside of the cluster but got
Description:
Cluster resource 'SQL Server (SYSTEM)' in Resource Group failed.
followed by
Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: 0x103.
Is there any alternative to a re-install ?
thanks
December 15, 2008 at 8:37 am
You could salvage this by creating the group and adding the items and dependencies back manually, make sure that you have all the information that you built the cluster with so that things are put back together right.
1. First create add all the disk resources for the group (right click, new resource, physical disk)
2. Once all those have been added create the resource for the SQL IP Address (right click, new resource, IP Address)
3. Then add the SQL Network Name (right click, new resource, network name) and make this dependent on the IP Address
4. Add the SQL Server service (right click, new resource, SQL Server) and make this dependent on all the disks and the network name
5. Add the SQL Server Agent server (right click, new resource, SQL Server Agent) and make this dependent on the SQL Server resource
Bring everything online and you should be all happy happy.
December 16, 2008 at 4:33 am
Hi Nicholas
Thanks for the info , I deleted the cluster group and re-created it plus the resources specified but that has not resolved the issue .
I look to check the TCP/IP protocol was enabled but configuration manager is unable to connect to WMI - but that is another issue
Do you have any further suggestions
Thanks
December 16, 2008 at 4:42 am
Additional info
from the sql server log
2008-12-16 09:33:47.32 Server Microsoft SQL Server 2005 - 9.00.3159.00 (X64)
Mar 23 2007 20:11:35
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2008-12-16 09:33:47.33 Server (c) 2005 Microsoft Corporation.
2008-12-16 09:33:47.33 Server All rights reserved.
2008-12-16 09:33:47.33 Server Server process ID is 4708.
2008-12-16 09:33:47.33 Server Authentication mode is MIXED.
2008-12-16 09:33:47.33 Server Logging SQL Server messages in file 'S:\Microsoft SQL Server\MSSQL.4\MSSQL\LOG\ERRORLOG'.
2008-12-16 09:33:47.33 Server This instance of SQL Server last reported using a process ID of 7420 at 15/12/2008 12:36:23 (local) 15/12/2008 12:36:23 (UTC). This is an informational message only; no user action is required.
2008-12-16 09:33:47.33 Server Registry startup parameters:
2008-12-16 09:33:47.35 Server -d S:\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\master.mdf
2008-12-16 09:33:47.35 Server -e S:\Microsoft SQL Server\MSSQL.4\MSSQL\LOG\ERRORLOG
2008-12-16 09:33:47.35 Server -l S:\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\mastlog.ldf
2008-12-16 09:33:47.44 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-12-16 09:33:47.44 Server Detected 8 CPUs. This is an informational message; no user action is required.
2008-12-16 09:33:47.50 Server Large Page Extensions enabled.
2008-12-16 09:33:47.50 Server Large Page Granularity: 2097152
2008-12-16 09:34:06.07 Server Large Page Allocated: 32MB
2008-12-16 09:34:08.62 Server Using locked pages for buffer pool.
2008-12-16 09:34:10.90 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2008-12-16 09:34:11.85 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-12-16 09:34:22.29 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-12-16 09:34:22.33 Server Database mirroring has been enabled on this instance of SQL Server.
2008-12-16 09:34:22.54 spid5s Starting up database 'master'.
2008-12-16 09:34:23.62 spid5s SQL Trace ID 1 was started by login "sa".
2008-12-16 09:34:23.69 spid5s Starting up database 'mssqlsystemresource'.
2008-12-16 09:34:23.71 spid5s The resource database build version is 9.00.3159. This is an informational message only. No user action is required.
2008-12-16 09:34:24.16 spid5s Server name is 'HMLUSQLAVS03\SYSTEM'. This is an informational message only. No user action is required.
2008-12-16 09:34:24.16 spid9s Starting up database 'model'.
2008-12-16 09:34:24.16 spid5s The NETBIOS name of the local node that is running the server is 'HMLBB9'. This is an informational message only. No user action is required.
2008-12-16 09:34:24.66 Server A self-generated certificate was successfully loaded for encryption.
2008-12-16 09:34:24.71 Server Error: 26054, Severity: 16, State: 1.
2008-12-16 09:34:24.71 Server Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: 0x103.
2008-12-16 09:34:24.71 Server Error: 17182, Severity: 16, State: 1.
2008-12-16 09:34:24.71 Server TDSSNIClient initialization failed with error 0x103, status code 0xa.
2008-12-16 09:34:24.71 Server Error: 17182, Severity: 16, State: 1.
2008-12-16 09:34:24.71 Server TDSSNIClient initialization failed with error 0x103, status code 0x1.
2008-12-16 09:34:24.71 Server Error: 17826, Severity: 18, State: 3.
2008-12-16 09:34:24.71 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2008-12-16 09:34:24.71 Server Error: 17120, Severity: 16, State: 1.
2008-12-16 09:34:24.71 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Thanks
December 16, 2008 at 5:12 am
Try adding the IP address as one of the objects SQL Server is dependent upon
December 16, 2008 at 6:51 am
Hi Nicholas
Tried that , no joy
Thanks
December 16, 2008 at 7:27 am
Any way you could attach a screencap of the cluster group and the resource information? Or even just copy the pertinent details?
December 16, 2008 at 7:45 am
Afternoon Nicholas
have loaded up a screenshot of the cluster group as doc4 below
Thanks
December 17, 2008 at 12:59 pm
The SQL resource needs to be dependent upon the disk resources also (among other things). One trick I've used to trouble-shoot is to start the SQL instance via the service manager and treat it as a non-clustered instance. Check the OS and SQL error logs and fix the errors as they present themselves. Once you get the SQL instance running via the service manager, then try starting if from the cluster adminstration tool.
With the disk, network name and ip resources running, I suspect the SQL instance will start via the service manager but not through the cluster admin.
December 17, 2008 at 1:34 pm
Do you have more than one sql server instance running on your machine?
MJ
February 26, 2010 at 1:15 pm
Hi Team,
I understand that you have one SQL cluster resource group and some one have deleted the SQL service and you are not able to get the resource online event after adding the resources manually.
We had the same problem today and we raised a trouble ticket with Microsoft and they have resolved immediately with the help of KB
http://support.microsoft.com/kb/883732
Try this....
Regards
Jeevan/Folks
April 23, 2010 at 9:02 am
Thanks this Kb really helped , it works for SQL server 2008 clusters as well
🙂
December 12, 2012 at 6:14 pm
I realize this thread is very old, but i just wanted to thank everyone all the same...
I had an insanely stupid moment earlier today and deleted the sql cluster resource instead of a disk within the resource as intended.
We were able to manually re-create the resource as outlined in the beginning of this thread and the KB article mentioned to re-create the reg. keys.
We had a slight issue when testing failover as the passive node had some weird kerberous issues but it was nothing a restart didn't fix.
Overall it went fairly smooth.
thanks!!!
(cluster was sql 2008)
August 8, 2013 at 9:46 am
Nicholas Cain (12/15/2008)
You could salvage this by creating the group and adding the items and dependencies back manually, make sure that you have all the information that you built the cluster with so that things are put back together right.1. First create add all the disk resources for the group (right click, new resource, physical disk)
2. Once all those have been added create the resource for the SQL IP Address (right click, new resource, IP Address)
3. Then add the SQL Network Name (right click, new resource, network name) and make this dependent on the IP Address
4. Add the SQL Server service (right click, new resource, SQL Server) and make this dependent on all the disks and the network name
5. Add the SQL Server Agent server (right click, new resource, SQL Server Agent) and make this dependent on the SQL Server resource
Bring everything online and you should be all happy happy.
Thankful to this thread, I recovered my 2 deleted Cluster groups last night (thankfully they were QA) and want to make updates
Note to everyone: Do not click "DELETE" on the right side Action bar, instead of right-click on the Cluster Disk and "Remove from Group", otherwise you'll delete the cluster group instead
This is Windows 2008 R2, Failover Cluster Manager. It worked with both SQL 2005 & 2008 R2 Cluster groups
1. First create add all the disk resources for the group (right click, new resource, physical disk)
2. Add a resource > Client Access Point > input Virtual name & IP > it'll create Name/IP resource for you
3. Add the SQL Server service (right click, new resource, SQL Server) and make this dependent on all the disks and the network name
4. Add the SQL Server Agent server (right click, new resource, SQL Server Agent) and make this dependent on the SQL Server resource
5. (NEW) instead of visiting the KB and hack registry, the simpler way is to edit in Resource Properties
right-click on [SQL Server] resource, go to last tab [Properties], and fill in the "VirtualServerName" and "InstanceName"; Repeat for SQL Agent
6. Online the SQL Server, and thank god 🙂
May 19, 2014 at 3:01 am
Check out KB 883732. Your cluster parameters in the registry may be missing.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply