Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Event: 17177 Expand / Collapse
Author
Message
Posted Thursday, June 16, 2005 12:04 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 17, 2008 10:35 AM
Points: 102, Visits: 110

Hello Everyone,

I've noticed the following event being logged in the Event Viewer on one of our SQL Servers:

Type:  Information

Source: MSSQLSERVER

Category:  (2)

Event: 17177

User:  N/A

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,

Barbara

 

Post #191440
Posted Thursday, June 16, 2005 2:13 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, April 18, 2014 8:44 AM
Points: 1,148, Visits: 81
I personally don't recall seeing this, but I did see an msdn blog that mentioned that this event log message was informational and can be seen when a SQL Server process has been running for a long time.  Hope this helps. 



My hovercraft is full of eels.
Post #191470
Posted Friday, June 17, 2005 6:59 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 17, 2008 10:35 AM
Points: 102, Visits: 110

sswords,

Thanks for the response.  I was hoping that was the case but always good to see if anyone else here has run into it.

Thanks again,

Barbara

Post #191634
Posted Friday, June 17, 2005 2:20 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, May 27, 2010 5:17 AM
Points: 104, Visits: 3

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

Post #191839
Posted Saturday, June 18, 2005 3:48 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 6, 2009 5:27 PM
Points: 38, Visits: 58
I've seen it but it doesn't appear to cause any harm. It was on a few QA / Dev type servers that don't get reboot that often. Though, I don't know if that's why. Since there's no complaints, I haven't seen a reason to fix it...or is that break it!
Post #191920
Posted Sunday, June 19, 2005 4:01 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, November 29, 2005 3:36 PM
Points: 57, Visits: 1

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.




Post #191944
Posted Tuesday, June 21, 2005 7:26 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 17, 2008 10:35 AM
Points: 102, Visits: 110

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

Thanks Again,

Barbara

 

Post #192425
Posted Thursday, August 4, 2005 11:41 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 22, 2008 7:54 AM
Points: 5, Visits: 12

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!

Laura

Post #207553
Posted Thursday, August 4, 2005 3:27 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, April 18, 2014 8:44 AM
Points: 1,148, Visits: 81

Laura,

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.

 





My hovercraft is full of eels.
Post #207684
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse