October 17, 2006 at 11:18 am
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
October 17, 2006 at 11:37 am
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
October 18, 2006 at 9:55 am
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.
October 18, 2006 at 10:07 am
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 ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
October 18, 2006 at 3:45 pm
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
October 18, 2006 at 7:18 pm
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?
May 16, 2009 at 4:23 pm
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.
June 6, 2010 at 3:58 am
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!
June 13, 2017 at 11:05 pm
Stanley Thurman - Saturday, May 16, 2009 4:23 PMhad 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.
Thank you very much Stanley... this work around worked for our environment but here our team have migrated the SQL server from 2008/R2 to 2012, during migration they removed old service accounts which are used for cluster configuration have removed and used new account which are part of domain group and later they are removed from group which in turn our SQL server services are stopped while failover & failback we tried most of the option which we were aware and none worked and finally the above option what suggestion had worked however I would like to add one more point it...
To fix above issue either we can add SQL Server service accounts to cluster administrator
or
Adding SID's to cluster admin
or
Adding doming group which SQL Server service account's which are part of it...
Thank you much for sharing resolution with us and help...
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply