March 18, 2010 at 5:48 am
URGENT HELP needed
sql agent is stopped, i am unable to restart it. got below error
"The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details."
Please advice
March 18, 2010 at 5:55 am
I found below error in eventlog
Faulting application sqlagent90.exe, version 2005.90.1399.0, stamp 434f60a9, faulting module kernel32.dll, version 5.2.3790.4062, stamp 46264680, debug? 0, fault address 0x0000bee7.
please let me know the solution, this is the production server
March 18, 2010 at 6:08 am
Are there any other errors in the log?
Also check the system logs for errors?
March 18, 2010 at 6:47 am
Reboot the machine if Possible - this will resolve many issues. (Production)
If not. Then stop the services of SQL Server and Agent services and try starting the services ...
I faced this in past. I rebooted as i was permitted to do so. And also did the second thing..
Do the same if you have full control on the server.
-Win.
Cheers,
- Win.
" Have a great day "
March 18, 2010 at 6:54 am
I agree with winslet. Once there is a memory fault or a stack dump the only way you are going to get the service back online is by rebooting. Unfortunately this doesn't get at the root of the cause, so the memory fault could happen again.
I wouldn't spend any more time on it then a reboot unless it does happen again. If it does then I suggest passing it to operations, and if that isn't an option then going over the system and application logs. It could be something hardware related especially with the memory.
March 18, 2010 at 7:16 am
I am posting the SQL Server error logs and SQL agent error log
SQL Server Agent Error logs:
Date 3/18/2010 8:09:35 AM
Log SQL Agent (Current - 3/18/2010 8:09:00 AM)
Message
[364] The Messenger service has not been started - NetSend notifications will not be sent
===============
sql server logs:
Date 3/18/2010 8:09:35 AM
Log SQL Agent (Current - 3/18/2010 8:09:00 AM)
Message
[364] The Messenger service has not been started - NetSend notifications will not be sent
-----
Date 3/18/2010 8:09:35 AM
Log SQL Agent (Current - 3/18/2010 8:09:00 AM)
Message
[364] The Messenger service has not been started - NetSend notifications will not be sent
-------
Date 3/18/2010 8:09:35 AM
Log SQL Agent (Current - 3/18/2010 8:09:00 AM)
Message
[364] The Messenger service has not been started - NetSend notifications will not be sent
-----
Date 3/18/2010 8:09:35 AM
Log SQL Agent (Current - 3/18/2010 8:09:00 AM)
Message
[364] The Messenger service has not been started - NetSend notifications will not be sent
----
Date 3/18/2010 8:09:35 AM
Log SQL Agent (Current - 3/18/2010 8:09:00 AM)
Message
[364] The Messenger service has not been started - NetSend notifications will not be sent
---
Date 3/18/2010 8:09:35 AM
Log SQL Agent (Current - 3/18/2010 8:09:00 AM)
Message
[364] The Messenger service has not been started - NetSend notifications will not be sent
March 18, 2010 at 7:25 am
I don't think you are going to find anything useful in the agent log. However, there could be a stack dump or mini-stack dump in the sql log.
March 18, 2010 at 7:39 am
I have started SQL Agent with local system account succesfully, but unable to start with service account(pw is correct).
Temapararly issue is resolved, but I need to start service with service account, because all my logshipping jobs and shared folder access depends on this service account.
I will try to reboot the server today off hours...
does it make sense....any thoughts? THanks much!
March 18, 2010 at 7:45 am
In this case I don't think rebooting the system is going to help after all. Look at whether the account is locked out. Try logging on to the machine with that account. You can also try running management studio on your local machine as that account and attempt a login to the sql instance. You can also check to see if any necessary permissions were taken away from the account on the machine.
March 18, 2010 at 7:53 am
I've seen similar things happen when password policies are enforced on service accounts and the passwords have expired or been changed. I've had this cause issues on service start-up before now.
Make sure any expiry policies aren't applied to your service accounts, reset the passwords on the accounts and try starting the services again, see if that helps.
March 18, 2010 at 8:34 am
Password is correct and I had put never expired. It is working for other server.
I tried to connect sql server with that account in server , below error
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
I tried to connect sql thru my laptop, below error
Login failed for user 'abcd'. (Microsoft SQL Server, Error: 18456)
March 18, 2010 at 9:59 am
Check on the SQL Server to see if the login is disabled. If it is, then enable it. You can do this in management studio by checking properties of the login under the status page.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply