|
From: Eric P. <EP...@ga...> - 2002-11-19 01:14:41
|
Hi Karima,
I have run into that exact same problem too. On some servers a simple
reboot will clear it out. On others it will just continue to reoccur
either immediately or after a few days. I have gone through a significant
amount of troubleshooting work (non-programming) and have not come up with
a resolution. I've tried different versions of NSClient, different Service
Pack levels, different versions of PDH.dll. I dumpster dived into all of
the newsgroups, search engines & even M$'s tech site without success. I
eventually ended up e-mailing Yves back in mid September. Here was my
reply:
"Hi,
Known issue. No workaround for now except that the
latest version has a feature to avoid the error to be
written in the event log. Should come up in the next
few days...
cheers,
Yves"
I assume Yves actually has a life outside of NSClient so for right now I am
in the same situation of cooling my heels until NSClientEVL comes out. In
the mean time I have disabled the NSClient service on the servers that have
this problem. I am not completely sure what the common denominator is with
the system that have errors. It seems that systems with dual processors
are more prone to have this affliction. We also have a fair number of
compaq servers.
Thanks,
-Eric
> Hello,
> With the NSClient I am getting the below error "NSClient Error: PDH.dll
Collect CPU - ERROR: 0x800007D6 (multiple)".
> It fills up the application log within a day. Does anybody have any idea
?
> Thanks
> karima
The content of this email message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments.
|