PerfNet and Perflib Errors

[OC]

I'm trying to troubleshoot very slow start-ups on a computer running WXP
Home SP1. The problem does not occur on every start-up or reboot, and in
some cases, appears to be related to a USB printer. If the printer is on,
start-up is normal; if it's turned off, the slow start-up occurs.
Regardless, everytime I encounter the slow start-up, the following two error
messages appear in the Application Log. I would appreciate any suggestions
for resolving the problem.
Thanks,
~OC~
----------------------------
Event Type: Error
Event Source: PerfNet
Event Category: None
Event ID: 2004
Date: 7/17/2004
Time: 6:59:03 PM
User: N/A
Computer: SARAG
Description:
Unable to open the Server service. Server performance data will not be
returned. Error code returned is in data DWORD 0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 34 00 00 c0 4..À
----------------------------
Event Type: Error
Event Source: Perflib
Event Category: None
Event ID: 2002
Date: 7/17/2004
Time: 6:59:14 PM
User: N/A
Computer: SARAG
Description:
The open procedure for service "WmiApRpl" in DLL
"C:\WINDOWS\System32\wbem\wmiaprpl.dll" has taken longer than the
established wait time to complete. 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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

It may only be coincidental that it happens when the printer is not turned
on during bootup.

Start with this, be sure you antivirus software is up to date and run a
virus scan. Also be sure you have no malware on your system, download,
install and run Ad Aware:
www.lavasoftusa.com.

If you are clear, is your printer in a networked environment? WBEM stands
for Web Based Enterprise Management. If your printer has some sort of
networking component, even if it is not connected to a network, that might
be the issue. It would then appear, it's software is making a call as the
system loads and because the printer is not turned on it doesn't get the
proper response.