April 14, 2009 at 1:54 pm
I would check to see what context the sql server is running under - I think it is local user, and that user has changed its password recently, but did not change the context the service runs under.
-- Cory
April 14, 2009 at 1:58 pm
yulichka (4/14/2009)
I copied the the hall message from Activity Monitor
Then check the SQL error log.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 14, 2009 at 2:04 pm
GilaMonster (4/14/2009)
Job? Windows Service? You're typing the password wrong? Registered servers with wrong credentials?
Registered server, wrong credentials, possibly on another PC? I've seen this where an old coworker went to corporate, set up a registered server, and then we changed the password. Polling was being used, so we got this at intervals.
Greg E
April 15, 2009 at 5:36 am
How can I check context the service runs under
April 15, 2009 at 5:42 am
I am sure there are other ways, but here is one:
on the affected machine:
Start -> run
Type "Services.msc" without the quotes
find your sql server service, right click, properties (or dbl click)
click on the log on tab and see what it is set to run as - if it is your user name, verify the current password.
click ok
restart the service.
-- Cory
April 15, 2009 at 2:19 pm
The place you want to check for services, and change it, is in the SQL Configuration Manager. You can check in the Control Panel Services applet, but it's easier in the Configuration Manager.
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply