|
|
You're in the
sql server clustering
group:SQL 2000 Problems EVENT ID 17052
sql server clustering:
following error message: [sqsrvres] checkODBCConnectError: sqlstate = 28000; native error = 4818; message = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'domain\account' I read through MSDN newsgroup & found your article regarding this issue; the problem started when the cluster service accounts were reset on both nodes & SQL would not start, to keep the story short here is what we did. After reseting the password in Active Directory for all the service accounts, all the services are running properly but in cluster adminstartion the sql resource is not online. Later I Guessed that the windows cluster login which is on the sql server is not mapped with active Directory changes. So I dropped the cluster service logon on sql server and re-created. <-- This seem to work but my question is why would we drop the cluster service logon on sql server & re-create it to have sql working again. If you can provide some insight, information, docs it would be a great benefit. Pravin.patel@hp.com
When I re-set the password for the cluster account on both nodes & restarted
the cluster service, it started up okay but SQL would not come online; what may cause this issue? [quoted text, click to view] "Geoff N. Hiten" wrote:
> The cluster service has to connect to the SQL instance in order to execute > the IsAlive and LooksAlive checks. This is how the cluster service > determines whether the resource is online. When you changed the cluster > service account, it could no longer connect, therefore it showed the > resources as offline. > > -- > Geoff N. Hiten > Senior Database Administrator > Microsoft SQL Server MVP > > > "Pravin Patel" <Pravin Patel@discussions.microsoft.com> wrote in message > news:CC096769-574E-4AE7-9E82-088BA2F2F9B7@microsoft.com... > > Hi, Geoff Hiten I have been having issues with SQL not starting due to the > > following error message: > > > > [sqsrvres] checkODBCConnectError: sqlstate = 28000; native error = 4818; > > message = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed > > for user 'domain\account' > > > > I read through MSDN newsgroup & found your article regarding this issue; > > the problem started when the cluster service accounts were reset on both > > nodes & SQL would not start, to keep the story short here is what we > > did. > > > > After reseting the password in Active Directory for all the service > > accounts, all the services are running properly but in cluster > > adminstartion the sql resource is not online. > > > > Later I Guessed that the windows cluster login which is on the sql > > server is not mapped with active Directory changes. > > > > So I dropped the cluster service logon on sql server and re-created. <-- > > This seem to work but my question is why would we drop the cluster > > service logon on sql server & re-create it to have sql working again. > > > > If you can provide some insight, information, docs it would be a great > > benefit. > > > > Pravin.patel@hp.com > > > >
The cluster service has to connect to the SQL instance in order to execute
the IsAlive and LooksAlive checks. This is how the cluster service determines whether the resource is online. When you changed the cluster service account, it could no longer connect, therefore it showed the resources as offline. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "Pravin Patel" <Pravin Patel@discussions.microsoft.com> wrote in message news:CC096769-574E-4AE7-9E82-088BA2F2F9B7@microsoft.com... > Hi, Geoff Hiten I have been having issues with SQL not starting due to the > following error message: > > [sqsrvres] checkODBCConnectError: sqlstate = 28000; native error = 4818; > message = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed > for user 'domain\account' > > I read through MSDN newsgroup & found your article regarding this issue; > the problem started when the cluster service accounts were reset on both > nodes & SQL would not start, to keep the story short here is what we > did. > > After reseting the password in Active Directory for all the service > accounts, all the services are running properly but in cluster > adminstartion the sql resource is not online. > > Later I Guessed that the windows cluster login which is on the sql > server is not mapped with active Directory changes. > > So I dropped the cluster service logon on sql server and re-created. <-- > This seem to work but my question is why would we drop the cluster > service logon on sql server & re-create it to have sql working again. > > If you can provide some insight, information, docs it would be a great > benefit. > > Pravin.patel@hp.com >
Are you using the same user for the SQL services that the cluster users? Did
you reset the password for the SQL services? Cheers, Rod MVP - Windows Server - Clustering http://www.nw-america.com - Clustering Website http://msmvps.com/clustering - Blog http://www.clusterhelp.com - Cluster Training [quoted text, click to view] "Pravin Patel" <PravinPatel@discussions.microsoft.com> wrote in message news:69743AB4-0F39-4F5F-96E7-F1F25FE66373@microsoft.com... > When I re-set the password for the cluster account on both nodes & > restarted > the cluster service, it started up okay but SQL would not come online; > what > may cause this issue? > > "Geoff N. Hiten" wrote: > >> The cluster service has to connect to the SQL instance in order to >> execute >> the IsAlive and LooksAlive checks. This is how the cluster service >> determines whether the resource is online. When you changed the cluster >> service account, it could no longer connect, therefore it showed the >> resources as offline. >> >> -- >> Geoff N. Hiten >> Senior Database Administrator >> Microsoft SQL Server MVP >> >> >> "Pravin Patel" <Pravin Patel@discussions.microsoft.com> wrote in message >> news:CC096769-574E-4AE7-9E82-088BA2F2F9B7@microsoft.com... >> > Hi, Geoff Hiten I have been having issues with SQL not starting due to >> > the >> > following error message: >> > >> > [sqsrvres] checkODBCConnectError: sqlstate = 28000; native error = >> > 4818; >> > message = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed >> > for user 'domain\account' >> > >> > I read through MSDN newsgroup & found your article regarding this >> > issue; >> > the problem started when the cluster service accounts were reset on >> > both >> > nodes & SQL would not start, to keep the story short here is what we >> > did. >> > >> > After reseting the password in Active Directory for all the service >> > accounts, all the services are running properly but in cluster >> > adminstartion the sql resource is not online. >> > >> > Later I Guessed that the windows cluster login which is on the sql >> > server is not mapped with active Directory changes. >> > >> > So I dropped the cluster service logon on sql server and re-created. >> > <-- >> > This seem to work but my question is why would we drop the cluster >> > service logon on sql server & re-create it to have sql working again. >> > >> > If you can provide some insight, information, docs it would be a great >> > benefit. >> > >> > Pravin.patel@hp.com >> > >> >> >>
We are using different users for SQL & Cluster account; the pass for SQL was not reset until we encountered the problem. [quoted text, click to view] "Rodney R. Fournier [MVP]" wrote:
> Are you using the same user for the SQL services that the cluster users? Did > you reset the password for the SQL services? > > Cheers, > > Rod > > MVP - Windows Server - Clustering > http://www.nw-america.com - Clustering Website > http://msmvps.com/clustering - Blog > http://www.clusterhelp.com - Cluster Training > > "Pravin Patel" <PravinPatel@discussions.microsoft.com> wrote in message > news:69743AB4-0F39-4F5F-96E7-F1F25FE66373@microsoft.com... > > When I re-set the password for the cluster account on both nodes & > > restarted > > the cluster service, it started up okay but SQL would not come online; > > what > > may cause this issue? > > > > "Geoff N. Hiten" wrote: > > > >> The cluster service has to connect to the SQL instance in order to > >> execute > >> the IsAlive and LooksAlive checks. This is how the cluster service > >> determines whether the resource is online. When you changed the cluster > >> service account, it could no longer connect, therefore it showed the > >> resources as offline. > >> > >> -- > >> Geoff N. Hiten > >> Senior Database Administrator > >> Microsoft SQL Server MVP > >> > >> > >> "Pravin Patel" <Pravin Patel@discussions.microsoft.com> wrote in message > >> news:CC096769-574E-4AE7-9E82-088BA2F2F9B7@microsoft.com... > >> > Hi, Geoff Hiten I have been having issues with SQL not starting due to > >> > the > >> > following error message: > >> > > >> > [sqsrvres] checkODBCConnectError: sqlstate = 28000; native error = > >> > 4818; > >> > message = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed > >> > for user 'domain\account' > >> > > >> > I read through MSDN newsgroup & found your article regarding this > >> > issue; > >> > the problem started when the cluster service accounts were reset on > >> > both > >> > nodes & SQL would not start, to keep the story short here is what we > >> > did. > >> > > >> > After reseting the password in Active Directory for all the service > >> > accounts, all the services are running properly but in cluster > >> > adminstartion the sql resource is not online. > >> > > >> > Later I Guessed that the windows cluster login which is on the sql > >> > server is not mapped with active Directory changes. > >> > > >> > So I dropped the cluster service logon on sql server and re-created. > >> > <-- > >> > This seem to work but my question is why would we drop the cluster > >> > service logon on sql server & re-create it to have sql working again. > >> > > >> > If you can provide some insight, information, docs it would be a great > >> > benefit. > >> > > >> > Pravin.patel@hp.com > >> > > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |