Confused...SA Account

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
>

Configuring mail for SQL Server Agent - Problem with Exchange and Outlook on same machine?

I would like to configure e-mail alerts on my SQL Server 2000 box.
However, we also run Exchange on the same machine. I've been told there
could be conflicts/issues having Outlook on the same machine as
Exchange; and apparently, one needs Outlook to configure a mail profile
for SQL Server Agent.

Is there, in fact, anything to worry about? If so, are there any
work-arounds beside moving Exchange to another server? (we've only got
one server, so this is not an option for us at this time).
Thanks.

- Dana<dananrg@.yahoo.com> wrote in message
news:1106142898.187937.44340@.z14g2000cwz.googlegro ups.com...
> I would like to configure e-mail alerts on my SQL Server 2000 box.
> However, we also run Exchange on the same machine. I've been told there
> could be conflicts/issues having Outlook on the same machine as
> Exchange; and apparently, one needs Outlook to configure a mail profile
> for SQL Server Agent.
> Is there, in fact, anything to worry about? If so, are there any
> work-arounds beside moving Exchange to another server? (we've only got
> one server, so this is not an option for us at this time).
> Thanks.
> - Dana

SQL Mail can sometimes be tricky to set up - you can check the MS Knowledge
Base for detailed articles on setup and troubleshooting. This is one
alternative approach:

http://www.karaszi.com/sqlserver/info_no_mapi.asp

I don't know if there are any problems with Exchange and Outlook on the same
box (you might want to ask in an Exchange group), but moving Exchange (or
MSSQL) to a separate server might be a good idea anyway, to avoid possible
resource conflicts. Although if you've been running both together for a
while, presumably that's not an issue for you right now.

Simon