SQL 2000 Cluster Help Urgent

unable to move any instances over to the second node
was working fine for over a year  windows2003 sp1  sql 2000

17052 sqsrvres  odbc sql driverconnect failed
sqsrves check odbc  not asociated


if i try to move an instance the Ip and disk move fine then waits for a while on the sql bits then flips it back to original node.
mhamerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rboyd56Commented:
Can you post the exact error messages from the application log?
0
rboyd56Commented:
Sounds like the cluster service cannot connect ot SQL Server to verify that it is running.

Verify that the cluster service service account on the node that SQL Server will not start on has a login with SQL Server and that it is a member of the sysadmin role.

With the full messages from the application log, we an get a better idea of what is happening.
0
mhamerAuthor Commented:
Source  (mssql$TRN  which is the instance im trying to move to other node)

event id 17052

computer affcetd node

[sqsrvres] ODBC sqldriverconnect failed





Source  (mssql$TRN  which is the instance im trying to move to other node)

event id 17052

computer affcetd node

[sqsrvres] checkODBCConnectError: sqlstate = 28000; native error = 4814; message = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

mhamerAuthor Commented:
we have 2 nodes,  both run 2 instances of SQL each, at present only node a will run these instances.
0
rboyd56Commented:
This is an authentication error. For some reason the cluster server service account cannot be validated.
If the cluster service account is domain account then this coupd be because the cluster service is attempting to make a Kerberos connction and is not falling back to NTLM. Verify that the cluster service account on this node is a domain account on the same domain as the SQL Server.

If it is a domain account there are a couple of things you can do to resolve this. The easiest is to change the default client library on this node to be named pipes. You can do this with the SQL Server client network utility. This will force the cluster service to use named pipes. If the problem is related to a Kerberos connection then this will reoslve that. Kerberos does not use named pipes, only tcp/ip.

Or you can use the steps in this URL to create the necesssary SPNs for SQL Server to use Kerberos:

http://msdn2.microsoft.com/en-us/library/ms189585.aspx
0
mhamerAuthor Commented:
hii cheers it is the same account that is in use on node a

i have made the change to use Namedpipes  but same error ( irebooted too)

i di dnotice a big patch of "information mesages in event viewer" that seemd to indicate it was talking ok, but then back to the RED  it fillthe whole event viewer in a few seconds.
0
rboyd56Commented:
Are there aliases established on this node that is used to connect to these instances of SQL Server?
Check the SQL Server client Network Utility on this node for aliases. If thera are any aliases, rename them and see if it will come online.

SQL Server is probably starting ok but the cluster service cannot connect. If there are aliases they could be the reason.
0
mhamerAuthor Commented:
Cluster resource 'SQL Server (TRN)' in Resource Group 'Training Sql' failed.
ClusSvc  
failover Mgr
1069
0
mhamerAuthor Commented:
not sure what you mean about rename alias's

where?
0
rboyd56Commented:
In the client network utility
Start - Run - cliconfg
Check the alias tab for aliases
Also make sure named pipes is at the top of the enabled protocols list.
0
mhamerAuthor Commented:
hi thanks

same error though

named pipes was top and no aliases. listed

any more ideas?

thanks for yyour help by the way
0
rboyd56Commented:
Then it could be a true authentication error.

Look in the nodes Security log for logon failures.
0
mhamerAuthor Commented:
not a single security error  :-(
0
mhamerAuthor Commented:
in fact   both the cluster service and the sql server account are both in there under sucsessful..
0
mhamerAuthor Commented:
ok out of hours took whole cluster down then just brought up the array and node be   same stuff  just wont start the sql resources (disk and ip etc fine)

could it be Sql rather than the node?

im a bit loath to rebuild node till i know what cause is.
0
rboyd56Commented:
Fail SQL over to that node and let it fail on that node. You may have to set the resource to not restart.

Go to the Services applet on that node and try to start the SQL Server service. If it does start then it is not SQL Server.  Now see if you can start SQL Server Agent. If it starts then connectivity is OK

 If you are still getting login failed or use 'Null'. Then it is something to do with authentication of the either the cluster service account or the sql server agent account (provided of courxe you get the same error starting SQL Server Agent)

When a user attempts to connect the account is passed to the DC to be authenticated. IF the account cannot be authenticated then the NULL user is passed back to SQL Server. That is why the error is being generated..

0
mhamerAuthor Commented:
did as you suggested, the instance i failed over did start using services  as did the matching sql agent.
but would not come live in cluster mgr,

tried to remake instance (old db not needed)  and i cant make a new instance, similar error not being able to connect to sql  or it diesnt exist..
0
mhamerAuthor Commented:
Sorted, any one know what might cause the issue though.

started to go through each and every error in event log to the point it no longer occured.

the fix was to  in adsi edit  alter the rights  of the sql server account,
the setserverprinciplename was read only, changed it to write  and it all started to work.

so what would cause the rights to change?  no one who works there even knows what adsiedit is.
0
rboyd56Commented:
That is strange. The only thing that I can think of it is that someone changed it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mhamerAuthor Commented:
Thnak you for your time and effort
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.