By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,739 Members | 1,523 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,739 IT Pros & Developers. It's quick & easy.

Client EM produce OS "failed login errors"

P: n/a
hi all, have anyone else met with the following problem.

we've got a SQL2000SP3a on a 2 active-active node clusters of W2K3,
this cluster in using AD.

I've found that whenever I use Enterprise Manager on my local computer
to register the above instance, it will constantly produce "Failed
login for <Domain>\<DomainUser>" errors in the Windows Security Log of
the database server machine. There's no failed login in the SQL error
log and I can work normally with the Enterprise Manager. The OS failed
logins error are gone once I un-register the instance from my
Enterprise Manager.

Does anyone know or met with this before?

Jul 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"New MSSQL DBA" <bo*******@gmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
hi all, have anyone else met with the following problem.

we've got a SQL2000SP3a on a 2 active-active node clusters of W2K3,
this cluster in using AD.

I've found that whenever I use Enterprise Manager on my local computer
to register the above instance, it will constantly produce "Failed
login for <Domain>\<DomainUser>" errors in the Windows Security Log of
the database server machine. There's no failed login in the SQL error
log and I can work normally with the Enterprise Manager. The OS failed
logins error are gone once I un-register the instance from my
Enterprise Manager.

Does anyone know or met with this before?


I don't really know, but as a complete guess, EM is trying to connect to the
operating system to get information about the MSSQL service state, and your
Windows account doesn't have those permissions. If this isn't helpful, you
might consider posting the full error details from the log.

Simon
Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.