Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SQL server cluster resource deleted Expand / Collapse
Author
Message
Posted Monday, December 15, 2008 7:12 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, August 6, 2014 4:37 AM
Points: 520, Visits: 1,677
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

Post #619568
Posted Monday, December 15, 2008 8:37 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, July 11, 2014 10:29 PM
Points: 2,006, Visits: 6,077
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.




Shamless self promotion - read my blog http://sirsql.net
Post #619628
Posted Tuesday, December 16, 2008 4:33 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, August 6, 2014 4:37 AM
Points: 520, Visits: 1,677
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
Post #620290
Posted Tuesday, December 16, 2008 4:42 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, August 6, 2014 4:37 AM
Points: 520, Visits: 1,677
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
Post #620301
Posted Tuesday, December 16, 2008 5:12 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, July 11, 2014 10:29 PM
Points: 2,006, Visits: 6,077
Try adding the IP address as one of the objects SQL Server is dependent upon



Shamless self promotion - read my blog http://sirsql.net
Post #620315
Posted Tuesday, December 16, 2008 6:51 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, August 6, 2014 4:37 AM
Points: 520, Visits: 1,677
Hi Nicholas

Tried that , no joy

Thanks
Post #620369
Posted Tuesday, December 16, 2008 7:27 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, July 11, 2014 10:29 PM
Points: 2,006, Visits: 6,077
Any way you could attach a screencap of the cluster group and the resource information? Or even just copy the pertinent details?



Shamless self promotion - read my blog http://sirsql.net
Post #620395
Posted Tuesday, December 16, 2008 7:45 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, August 6, 2014 4:37 AM
Points: 520, Visits: 1,677
Afternoon Nicholas

have loaded up a screenshot of the cluster group as doc4 below

Thanks



  Post Attachments 
Doc4.doc (159 views, 57.50 KB)
Post #620416
Posted Wednesday, December 17, 2008 12:59 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, March 25, 2014 3:37 PM
Points: 12, Visits: 84
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.
Post #621565
Posted Wednesday, December 17, 2008 1:34 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 22, 2014 7:04 AM
Points: 1,688, Visits: 8,766
Do you have more than one sql server instance running on your machine?

MJ
Post #621587
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse