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

CLUSTER Error: Could not find any IP address that this SQL Server instance depends upon??? Expand / Collapse
Author
Message
Posted Tuesday, October 17, 2006 11:18 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 2:14 PM
Points: 1,298, Visits: 1,886

Hi all

I've got a sql 2005 active/passive cluster on win2k3 servers.

In cluster admin under sql server 2005 group resources i've got:

3 physical disks

IP Address - ip address of mycluster server

Network Name - mycluster-depends on Ip address

SQL Server  - sql server - depends on 3 physical disks, network name and ip address.

SQL Server Agent - SQL agent - depends on SQL Server

SQL Full-Text - also depends on sql server

All my dependencies and resources are correct.

so when i try to bring online the sql server it says failed under state.

I try to start the sql server from config manager it doesn't start. give me an error:

"The request failed or service did not respond in timely fashion. consult event log"

I go into the Event Viewer under application i see this error:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 26054
Date:  10/17/2006
Time:  1:10:19 PM
User:  N/A
Computer: mycluster1
Description:
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: c6 65 00 00 10 00 00 00   Æe......
0008: 0b 00 00 00 4e 00 59 00   ....m.y.
0010: 43 00 53 00 51 00 4c 00   c.l.u.s.
0018: 49 00 4d 00 44 00 42 00   t.e.r.1.
0020: 00 00 00 00 00 00         ...... 

 

I double checked everything that this error refers to and still i cannot start sql server.

Can someone help me out with this?

Thanks for all your help in advance

 

 



Alex S
Post #315991
Posted Tuesday, October 17, 2006 11:37 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 4:31 PM
Points: 344, Visits: 308

Can you check if you have same message in SQL Error Logs?

I feel there is something wrong with registry setting.

http://support.microsoft.com/?id=883732

 

Post #315997
Posted Wednesday, October 18, 2006 9:55 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 2:14 PM
Points: 1,298, Visits: 1,886

This is what i see in the error log of sql server.

I still can't start sql server from cnfogi manager or bring online from cluster admin.

2006-10-17 13:10:19.44 Server      Error: 26054, Severity: 16, State: 1.
2006-10-17 13:10:19.44 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.
2006-10-17 13:10:19.44 Server      Error: 17182, Severity: 16, State: 1.
2006-10-17 13:10:19.44 Server      TDSSNIClient initialization failed with error 0x103, status code 0xa.
2006-10-17 13:10:19.44 Server      Error: 17182, Severity: 16, State: 1.
2006-10-17 13:10:19.44 Server      TDSSNIClient initialization failed with error 0x103, status code 0x1.
2006-10-17 13:10:19.44 Server      Error: 17826, Severity: 18, State: 3.
2006-10-17 13:10:19.44 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.
2006-10-17 13:10:19.44 Server      Error: 17120, Severity: 16, State: 1.
2006-10-17 13:10:19.44 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.



Alex S
Post #316312
Posted Wednesday, October 18, 2006 10:07 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Saturday, November 22, 2014 7:46 PM
Points: 3,220, Visits: 2,361

Have you tried a cold boot of the cluster nodes ? Have you tried evicting and readding a node ? Have you tried cluster failovers manually and by reboot ignoring SQL Server ? Could you post the C:\Windows\cluster\cluster.log file ?

 





Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."
Post #316323
Posted Wednesday, October 18, 2006 3:45 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 2:14 PM
Points: 1,298, Visits: 1,886

Because of previous manual removal of clustered sql server 2000

we decided to reformat the nodes and reinstall everything from scratch.

When we installed sql server 2005 on a cluster we started getting weird errors all over the nodes.

Even explorer.exe and mmc.exe would generate exception errors.

 

Thanks for all your help



Alex S
Post #316460
Posted Wednesday, October 18, 2006 7:18 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, November 24, 2014 8:22 AM
Points: 40, Visits: 184
What kind of errors are you getting? Is SQL 2k5 installation completing successfully or is it failing before that? I am sure you are but just out of curiosity are you using different network name and different ip for cluster and sql or not? Can you post the errors you are getting?
Post #316483
Posted Saturday, May 16, 2009 4:23 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 3, 2012 7:42 AM
Points: 1, Visits: 137
had the same issue but none of the above worked and the adding the HKLM parameters fix did not work either.

We traced it down to someone was over zealous of security and removed the AD Service account group from the Cluster Admin security but did not add the SQL Service accounts back in.

If you remove the AD Group from Cluster admin for SQL 2005, you must add the SQL Service account back in so SQL can connect and cluster can manage the resources. in this case, it couldnt read the IP parameters. makes sense since this is the first parm in the dependency chain.
Post #718565
Posted Sunday, June 6, 2010 3:58 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, January 12, 2011 10:12 PM
Points: 4, Visits: 2
AlexSQLForums (10/18/2006)


This is what i see in the error log of sql server.

I still can't start sql server from cnfogi manager or bring online from cluster admin.

2006-10-17 13:10:19.44 Server Error: 26054, Severity: 16, State: 1.
2006-10-17 13:10:19.44 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.
2006-10-17 13:10:19.44 Server Error: 17182, Severity: 16, State: 1.
2006-10-17 13:10:19.44 Server TDSSNIClient initialization failed with error 0x103, status code 0xa.
2006-10-17 13:10:19.44 Server Error: 17182, Severity: 16, State: 1.
2006-10-17 13:10:19.44 Server TDSSNIClient initialization failed with error 0x103, status code 0x1.
2006-10-17 13:10:19.44 Server Error: 17826, Severity: 18, State: 3.
2006-10-17 13:10:19.44 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.
2006-10-17 13:10:19.44 Server Error: 17120, Severity: 16, State: 1.
2006-10-17 13:10:19.44 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.



I got similar problem. Resolved it by using following steps described here - http://humanier.blogspot.com/2010/06/today-i-installed-ms-sql-server-2005-on.html


==================
Visit my blog!
Post #933206
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse