November 18, 2002 at 12:01 pm
OK I'll put this here where it belongs.
I have an active / passive setup connected to a SAN via Fiber. Win2kAS and SQL2K EE.
Installed to primary node, etc currently only base install but I did have it installed with SP2 same problem.
When I move the group SQL will not start on the alternate node.
The only message I'm getting is
Cluster resource 'SQL Server' failed. From the Alternate node Source ClusSvc EventId 1069.
Any ideas, what else can I look at ??
KlK, MCSE
KlK
November 18, 2002 at 12:06 pm
I'll add one more message from SQL server logs
Resource Manager Creation Failed: Result Code = 0x8004d01c
KlK, MCSE
KlK
November 18, 2002 at 12:36 pm
Make sure you have a sql group with all the apropreate services to start up in that group for failover. I'd do a look on MS technet as well. My gut tells me you don't have the right services or disk groups starting up when the node fails over.
Cheers,
Wes
November 18, 2002 at 12:37 pm
Probably not the cause, but one of those "Get the question out of the way" types of things. Did a password change occur recently and if so, how was the password change?
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
November 18, 2002 at 12:44 pm
Question #1: Did you test failover of your resources BEFORE you installed SQL Server 2000 EE?
If the answer is YES (and it worked!), I suggest you uninstall SQL Server 2000, reboot and try again.
If the answer is NO, I suggest you check to see if the name of each server is "close" to the name of the cluster, i.e. I had a resource failover problem when the cluster name was "ROSETTSTDBC" and the server names were "ROSETTSTDBC1" and "ROSETTSTDBC2". When I renamed the cluster to "TTSTDBC", the resource failover problem disappeared. I suspect Windows 2000 clustering has some type of limit to the number of characters it checks for server names, because I setup a Windows NT 4.0 cluster in a similar fashion (albeit with shorter names) without incident.
November 19, 2002 at 10:31 am
We'll have move info later, but it appears our engineering team missed a couple of things on the second machine.
We did test the cluster before installing SQL and it seemed to work, with a couple of what seemed to be non related issues.
The names are all under the 8 characters
XXXAPP21 / XXXAPP22 / XXXASC02 / XXXSQL02 for server / server / cluster / SQL. So I don't think that is an issue.
The Userid / password is specific for SQL Clustering so that shouldn't be an issue.
Hopefully they have found the problem-S- and fixed them. I should get it back later today to try again, sometimes I do wish they'd just let me put it all together myself.
Thanks much to all !!!
KlK, MCSE
KlK
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply