[THIN] Re: Perflib errors
- From: Adam.Baum@xxxxxxxxxxxxxx
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 4 Jan 2007 14:41:04 -0700
Go to www.eventid.net and search on the event id and source. It will bring
up a number of responses, many of which reference MS KB articles. I
usually go into the offending service and eithe rincrease the timeout value
or disable the counters for it. That sight has all the details.
adam
"Carl Stalhood"
<cstalhood@mailsn
are.net> To
Sent by: <thin@xxxxxxxxxxxxx>
thin-bounce@freel cc
ists.org
Subject
[THIN] Re: Perflib errors
01/04/2007 02:30
PM
Please respond to
thin@xxxxxxxxxxxx
g
I see these kinds of errors a lot so I just ignore them.
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Schneider, Chad M
Sent: Thursday, January 04, 2007 2:45 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Perflib errors
I have an idea that I am seeing the same thing on some servers….
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Malcolm Bruton
Sent: Thursday, January 04, 2007 2:40 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Perflib errors
Anyone have any idea?
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Malcolm Bruton
Sent: 03 January 2007 11:23
To: thin@xxxxxxxxxxxxx
Subject: Perflib errors
All
Have a problem where we get lots of perflib errors in the event logs...Such
as
The timeout waiting for the performance data collection function "PerfOS"
in the "C:\WINNT\system32\perfos.dll" Library to finish has expired. There
may be a problem with this extensible counter or the service it is
collecting data from or the system may have been very busy when this call
was attempted.
or
The timeout waiting for the performance data collection function
"TermService" in the "C:\WINNT\system32\perfts.dll" Library to finish has
expired. There may be a problem with this extensible counter or the service
it is collecting data from or the system may have been very busy when this
call was attempted.
We run Metaframe XPe FR3 on Windows 2000 Sp4 and use RM on HP tin. We
think we get all these errors because we have too many things running on
the boxes monitoring performance. E.g. the OS, RM HP management agents and
NETIQ. Boxes appear to show no information in the CMC but if you wait 10
mins or so the box is fine. Whilst in this state the above event log
messages occur.
Anyone have any ideas? We were thinking about disabling the HP Management
agent (just the Performance monitor on) but can't work out how to automate
this.
Thanks
Malcolm
Other related posts: