Hi
I have a two node cluster with SQL2000 SP3. When the node1 fails over to
node2, the SQL Server Agent fails. The log file says "Login Failed for user
'sa'" I don't understand how the SA account can fail on node2 and not on
node1. Can anyone shed some light on this and possibly how to resolve the
issue.
Thank You
Marc
What security account context is the SQL Agent running under? Is it a domain account and does it have adequate permissions/rights on both nodes?
|||Hi Stephen
SQL security is set for "SQL Server and Windows" and the service account is
in the Domain Admins group. Same service account is used for both nodes.
Regards
Marc
"Stephen Strong" <anonymous@.discussions.microsoft.com> wrote in message
news:39A963C4-A818-487F-8B10-C38CC58715FA@.microsoft.com...
> What security account context is the SQL Agent running under? Is it a
domain account and does it have adequate permissions/rights on both nodes?
|||Is the SQL Server Agent startup account a member of the local admin group
on both nodes. If you are using SQL Server authentication for SQL Server
Agent to connect to SQL Server then the SQL Server Agent startup account
has to be a local Admin.
You can check the SQL Agent connection properties by right clicking on SQL
Server Agent - Properties - Connection and see how the connection to SQL
Server is set up.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks Guys
As it turns out, one of our programmers changed the authentication method to
Windows rather than SQL. I changed it back and all is well.
Regards
Marc
"Marc" <Marc@.nospam.com> wrote in message
news:%23u4AZPJJEHA.2736@.TK2MSFTNGP12.phx.gbl...
> Hi
> I have a two node cluster with SQL2000 SP3. When the node1 fails over to
> node2, the SQL Server Agent fails. The log file says "Login Failed for
user
> 'sa'" I don't understand how the SA account can fail on node2 and not on
> node1. Can anyone shed some light on this and possibly how to resolve the
> issue.
> Thank You
> Marc
>
Showing posts with label node. Show all posts
Showing posts with label node. Show all posts
Wednesday, 7 March 2012
Sunday, 19 February 2012
Confirm SP install on a cluster
Hi,
How do I know that the installation of a SP was successfully done on both
nodes of a 2-node cluster?
I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
it had successfully completed. I checked the productlevel to confirm and then
failed over to the other node and checked the productlevel there as well. Is
that good enough? Should I bee looking elsewhere, such as maybe
date-time-stamp on certain files, registry entries, file versions, etc?
Thanks.
Hello Rob, the updates to the dlls and exe files under c:\program
files\microsoft sql server\mssql\binn can also me checked for versioning
information if you wish. the SQL that is aplied during the install will be in
the server no matter what server your on obviously. In my experience when a
service pack fails to update binaries properly for a cluster and SP1 for
SQL2000 did you will be a message on the node it failed on that it can no
longer run the SQL resource and it will fail back to the other node that was
updated properly usually the one you ran the SP on.
Hope that helps
John Vandervliet
"Rob" wrote:
> Hi,
> How do I know that the installation of a SP was successfully done on both
> nodes of a 2-node cluster?
> I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
> it had successfully completed. I checked the productlevel to confirm and then
> failed over to the other node and checked the productlevel there as well. Is
> that good enough? Should I bee looking elsewhere, such as maybe
> date-time-stamp on certain files, registry entries, file versions, etc?
> Thanks.
How do I know that the installation of a SP was successfully done on both
nodes of a 2-node cluster?
I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
it had successfully completed. I checked the productlevel to confirm and then
failed over to the other node and checked the productlevel there as well. Is
that good enough? Should I bee looking elsewhere, such as maybe
date-time-stamp on certain files, registry entries, file versions, etc?
Thanks.
Hello Rob, the updates to the dlls and exe files under c:\program
files\microsoft sql server\mssql\binn can also me checked for versioning
information if you wish. the SQL that is aplied during the install will be in
the server no matter what server your on obviously. In my experience when a
service pack fails to update binaries properly for a cluster and SP1 for
SQL2000 did you will be a message on the node it failed on that it can no
longer run the SQL resource and it will fail back to the other node that was
updated properly usually the one you ran the SP on.
Hope that helps
John Vandervliet
"Rob" wrote:
> Hi,
> How do I know that the installation of a SP was successfully done on both
> nodes of a 2-node cluster?
> I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
> it had successfully completed. I checked the productlevel to confirm and then
> failed over to the other node and checked the productlevel there as well. Is
> that good enough? Should I bee looking elsewhere, such as maybe
> date-time-stamp on certain files, registry entries, file versions, etc?
> Thanks.
Confirm SP install on a cluster
Hi,
How do I know that the installation of a SP was successfully done on both
nodes of a 2-node cluster?
I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
it had successfully completed. I checked the productlevel to confirm and then
failed over to the other node and checked the productlevel there as well. Is
that good enough? Should I bee looking elsewhere, such as maybe
date-time-stamp on certain files, registry entries, file versions, etc?
Thanks.Hello Rob, the updates to the dlls and exe files under c:\program
files\microsoft sql server\mssql\binn can also me checked for versioning
information if you wish. the SQL that is aplied during the install will be in
the server no matter what server your on obviously. In my experience when a
service pack fails to update binaries properly for a cluster and SP1 for
SQL2000 did you will be a message on the node it failed on that it can no
longer run the SQL resource and it will fail back to the other node that was
updated properly usually the one you ran the SP on.
Hope that helps
John Vandervliet
"Rob" wrote:
> Hi,
> How do I know that the installation of a SP was successfully done on both
> nodes of a 2-node cluster?
> I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
> it had successfully completed. I checked the productlevel to confirm and then
> failed over to the other node and checked the productlevel there as well. Is
> that good enough? Should I bee looking elsewhere, such as maybe
> date-time-stamp on certain files, registry entries, file versions, etc?
> Thanks.
How do I know that the installation of a SP was successfully done on both
nodes of a 2-node cluster?
I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
it had successfully completed. I checked the productlevel to confirm and then
failed over to the other node and checked the productlevel there as well. Is
that good enough? Should I bee looking elsewhere, such as maybe
date-time-stamp on certain files, registry entries, file versions, etc?
Thanks.Hello Rob, the updates to the dlls and exe files under c:\program
files\microsoft sql server\mssql\binn can also me checked for versioning
information if you wish. the SQL that is aplied during the install will be in
the server no matter what server your on obviously. In my experience when a
service pack fails to update binaries properly for a cluster and SP1 for
SQL2000 did you will be a message on the node it failed on that it can no
longer run the SQL resource and it will fail back to the other node that was
updated properly usually the one you ran the SP on.
Hope that helps
John Vandervliet
"Rob" wrote:
> Hi,
> How do I know that the installation of a SP was successfully done on both
> nodes of a 2-node cluster?
> I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
> it had successfully completed. I checked the productlevel to confirm and then
> failed over to the other node and checked the productlevel there as well. Is
> that good enough? Should I bee looking elsewhere, such as maybe
> date-time-stamp on certain files, registry entries, file versions, etc?
> Thanks.
Confirm SP install on a cluster
Hi,
How do I know that the installation of a SP was successfully done on both
nodes of a 2-node cluster?
I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
it had successfully completed. I checked the productlevel to confirm and the
n
failed over to the other node and checked the productlevel there as well. Is
that good enough? Should I bee looking elsewhere, such as maybe
date-time-stamp on certain files, registry entries, file versions, etc?
Thanks.Hello Rob, the updates to the dlls and exe files under c:\program
files\microsoft sql server\mssql\binn can also me checked for versioning
information if you wish. the SQL that is aplied during the install will be i
n
the server no matter what server your on obviously. In my experience when a
service pack fails to update binaries properly for a cluster and SP1 for
SQL2000 did you will be a message on the node it failed on that it can no
longer run the SQL resource and it will fail back to the other node that was
updated properly usually the one you ran the SP on.
Hope that helps
John Vandervliet
"Rob" wrote:
> Hi,
> How do I know that the installation of a SP was successfully done on both
> nodes of a 2-node cluster?
> I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
> it had successfully completed. I checked the productlevel to confirm and t
hen
> failed over to the other node and checked the productlevel there as well.
Is
> that good enough? Should I bee looking elsewhere, such as maybe
> date-time-stamp on certain files, registry entries, file versions, etc?
> Thanks.
How do I know that the installation of a SP was successfully done on both
nodes of a 2-node cluster?
I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
it had successfully completed. I checked the productlevel to confirm and the
n
failed over to the other node and checked the productlevel there as well. Is
that good enough? Should I bee looking elsewhere, such as maybe
date-time-stamp on certain files, registry entries, file versions, etc?
Thanks.Hello Rob, the updates to the dlls and exe files under c:\program
files\microsoft sql server\mssql\binn can also me checked for versioning
information if you wish. the SQL that is aplied during the install will be i
n
the server no matter what server your on obviously. In my experience when a
service pack fails to update binaries properly for a cluster and SP1 for
SQL2000 did you will be a message on the node it failed on that it can no
longer run the SQL resource and it will fail back to the other node that was
updated properly usually the one you ran the SP on.
Hope that helps
John Vandervliet
"Rob" wrote:
> Hi,
> How do I know that the installation of a SP was successfully done on both
> nodes of a 2-node cluster?
> I installed SQL 2005 SP1 on the active node of my 2-node cluster and after
> it had successfully completed. I checked the productlevel to confirm and t
hen
> failed over to the other node and checked the productlevel there as well.
Is
> that good enough? Should I bee looking elsewhere, such as maybe
> date-time-stamp on certain files, registry entries, file versions, etc?
> Thanks.
Subscribe to:
Posts (Atom)