Error: WMI performance API service

[Guest]

Everytime when I start up the Windowsxp, the following error occurs:

Timeout (30000 milliseconds) waiting for the WMI Performance API service to
connect.

The error shows only in event viewer.

How can I resolve the problem?

 

[John John]

Copy and paste the full contents of the particular event here. Click on
the little clipboard icon on the right, the one on the bottom that looks
like 2 pages of paper, then paste the contents to your message. It will
make it easier for the elves to help you.

John

 

[Guest]

Everytime when I start up the Windowsxp, the following error occurs:

Timeout (30000 milliseconds) waiting for the WMI Performance API service to
connect.

The error shows only in event viewer.

How can I resolve the problem?

It looks like there is an application/program that want to connect to the
internet on startup and timing out because the time interval for the startup
longer than being anticipated or the settings for this application to try (
say for 5 times).
So try to start in clean boot as described below:
How to perform a clean boot procedure to prevent background programs from..:
http://support.microsoft.com/kb/331796
Also try to Disable the Windows Updates from the services and look in the
Device manager for the API devices for malfunctioning or Conflict in IRQ.
HTH.
nass

 

[Guest]

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 20.06.2007
Time: 09:49:29
User: N/A
Computer: LUSBAOBEI
Description:
Timeout (30000 milliseconds) waiting for the WMI Performance API service to
connect.

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

 

[Guest]

Thanks, nass.
But it seems that the application/program doesn't want to connect to the
internet, but to the service control manage. I'm sorry that I haven't posted
the wohle the information.
Following are the full information that xp provided me:

Details
Product: Windows Operating System
ID: 7009
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_CONNECTION_TIMEOUT
Message: Timeout (%1 milliseconds) waiting for the %2 service to connect.

Explanation
Within a specified time period after a new service starts, it notifies
Service Control Manager (SCM) that it is ready to connect. In this case, the
service did not notify SCM within the time period.

The service might be stuck in a loop or waiting on a system resource, such
as additional memory.


User Action
To determine why the service is not connecting, do the following:

Verify that the service is configured correctly.
Verify that the system is in a healthy state, for example, it is not running
low on resources

 

[Guest]

more detailed information:

Details
Product: Windows Operating System
ID: 7009
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_CONNECTION_TIMEOUT
Message: Timeout (%1 milliseconds) waiting for the %2 service to connect.

Explanation
Within a specified time period after a new service starts, it notifies
Service Control Manager (SCM) that it is ready to connect. In this case, the
service did not notify SCM within the time period.

The service might be stuck in a loop or waiting on a system resource, such
as additional memory.


User Action
To determine why the service is not connecting, do the following:

Verify that the service is configured correctly.
Verify that the system is in a healthy state, for example, it is not running
low on resources

 

[Guest]

Thanks, nass.
But it seems that the application/program doesn't want to connect to the
internet, but to the service control manage. I'm sorry that I haven't posted
the wohle the information.
Following are the full information that xp provided me:

Details
Product: Windows Operating System
ID: 7009
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_CONNECTION_TIMEOUT
Message: Timeout (%1 milliseconds) waiting for the %2 service to connect.

Explanation
Within a specified time period after a new service starts, it notifies
Service Control Manager (SCM) that it is ready to connect. In this case, the
service did not notify SCM within the time period.

The service might be stuck in a loop or waiting on a system resource, such
as additional memory.


User Action
To determine why the service is not connecting, do the following:

Verify that the service is configured correctly.
Verify that the system is in a healthy state, for example, it is not running
low on resources

Your Network settings is messed up for some how, how do you connect to the
Internet?, try System Restore to an Earlier Date and see if that will help.
Certificate Server Fails to Start with Event ID 7000 or 7009
http://support.microsoft.com/kb/217339
TCP/IP and NBT configuration parameters for Windows XP
http://support.microsoft.com/kb/314053
The Microsoft Exchange Information Store service does not start, and Event
IDs 7009 and 7000 are logged after you apply security update 894689 in
Exchange 2000 Server
http://support.microsoft.com/kb/926204
COM+ functionality may be disabled after you install the security update
that is associated with security bulletin MS05-051 on a computer that is
running a 64-bit edition of Windows Server 2003
http://support.microsoft.com/kb/910383/
Things to look at( USB, PCI card, Wireless Card, CD/DVD), run chckdsk /r on
this machine.
HTH.
nass

 

[John John]

That might be hard to troubleshoot. Are there any other error messages
in the Event Log? I think that something is calling on WMI to collect
information on a perfmon object but WMI can't connect to the object
counter for some reason or other. Does the error occur when you boot to
safe mode? Using a tool like Autoruns and taking a good look at the
items that start when the computer boots may shed some light on the
subject. Another approach would be to try using msconfig and do a
diagnostic startup and see if the error is still there. If the error
disappears enable half of the startup items, then you will know from
which pile the error comes from. Keep parsing the list in halves until
you find the culprit. These are just suggestions or things to try to
see if you can narrow things down.

John

 

[Guest]

Your Network settings is messed up for some how, how do you connect to the
Internet?, try System Restore to an Earlier Date and see if that will help.
Certificate Server Fails to Start with Event ID 7000 or 7009
http://support.microsoft.com/kb/217339
TCP/IP and NBT configuration parameters for Windows XP
http://support.microsoft.com/kb/314053
The Microsoft Exchange Information Store service does not start, and Event
IDs 7009 and 7000 are logged after you apply security update 894689 in
Exchange 2000 Server
http://support.microsoft.com/kb/926204
COM+ functionality may be disabled after you install the security update
that is associated with security bulletin MS05-051 on a computer that is
running a 64-bit edition of Windows Server 2003
http://support.microsoft.com/kb/910383/
Things to look at( USB, PCI card, Wireless Card, CD/DVD), run chckdsk /r on
this machine.
HTH.
nass

Adding to the above:
WMI search:
http://www.microsoft.com/communitie...&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
MS:: <Quote>
Stopping and Starting the WMI Service

If you are experiencing problems with the WMI service you might need to
manually stop and restart the service. Before doing so you should enable
WMI’s verbose logging option. This provides additional information in the WMI
error logs that might be useful in diagnosing the problem. To enable verbose
logging using the WMI control, do the following:
1.Open the Computer Management MMC snap-in and expand Services and
Applications.
2.Right-click WMI Control and click Properties.
3.In the WMI Control Properties dialog box, on the Logging tab, select
Verbose (includes extra information for Microsoft troubleshooting) and then
click OK.
Alternatively, you can modify the following registry values:
•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging to 2.
•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging File Max Size
to 4000000.
After enabling verbose logging try stopping the WMI service by typing the
following
Open a run command prompt:
net stop winmgmt

If the net stop command fails you can force the service to stop by typing
this:
winmgmt /kill

Important. If you are running Windows XP or Windows Server 2003 the WMI
service runs inside a process named Svchost; this process contains other
services as well as WMI. Because of that, you should not try to stop
Svchost;
if you succeed, you’ll stop all the other services running in that process
as
well. Instead, use net stop winmgmt or winmgmt /kill in order to stop just
the WMI service.

You can then restart the service by typing the following command:
net start winmgmt

If the service does not restart try rebooting the computer to see if that
corrects the problem.
If it does not, then continue reading.
MS:: </Quote>

"WMI Diagnosis Utility"
http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx

Systems that have changed the default Access Control List permissions on the
%windir%\registration directory may experience various problems after you
install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC
http://support.microsoft.com/kb/909444
Also you can download the DiagWMI from here and some good solutions on the
page:
http://windowsxp.mvps.org/repairwmi.htm.

= Open a run command and try to re-register these DLLs:
regsvr32 hnetcfg.dll
regsvr32 netcfgx.dll
regsvr32 netman.dll
regsvr32 atl.dll
regsvr32 netshell.dll
Also try repair the WMI as descriped here:
http://groups.google.com/group/microsoft.public.win32.programmer.wmi/msg/1da6ab3690bc75a0
What Firewall/Anti-Virus you have running on your machine?.
HTH.
Let us know.
nass