I've noticed the following event being logged in the Event Viewer on one of our SQL Servers:
This instance of SQL Server has been using a process id of 1148 since 4/14/2005 12:29:38 PM (local) 4/14/2005 4:29:38 PM (UTC).
Has anyone else run into this? Should this cause me some concern or is it one of those messages that is truly just informational?
As always, thank for your help,
Thanks for the response. I was hoping that was the case but always good to see if anyone else here has run into it.
A good resource for such things is EventID.net. You need to use MSSQLServer as the source.
According to the two posts there, this is purely informational. However, I would question why the process is taking so long. Addressing the 'problem' now may save some time and grief later
Barbara, in my opinion you should not worry about this message at all. This is a purely informational message. We get this message all the time.
You could see a corresponding entry in the 'System' event log around the same time noted as event id 6013. The computer is collecting the uptime information and records these events.
You can confirm this with your network admin person and will probably get the same answer.
Just wanted to thank everyone for their taking the time to write their experience with this error.
I really appreciate the feedback, and feel better now about doing nothing
I just read the listing for 17177 at EventID.net and it was helpful for the problem I'm having. The event is informational, but in my case it's telling me that my backup software is not starting correctly and timing out. Now I just have to figure out why it's timing out!
Since you said backup software I'm assuming you're using a third party solution for your SQL Server backups. We've had problems in the past with backup software and it can sometimes cause problems/contention with SQL Server native backups by creating a blocking situation.
What I've done in the past has been to stop the backup software (in our case it runs as a service on the server), then stop and restart the SQL Server Agent. Finally, remember to restart your backup agent service. This solves the problem 99% of the time and doesn't require a restart of the server.
Hope this helps with your problem.