"C:\Windows\System32\wbem\Logs\wmiprov.log" is logged massively&#

By jamesVault
in Microsoft (Windows)

 Share

Recommended Posts

Proficient

jamesVault

Posted
Posted

"C:\Windows\System32\wbem\Logs\wmiprov.log" is logged massively!

What happens?

(Sat Jan 31 10:49:55 2009.268774) : ***************************************

(Sat Jan 31 10:49:56 2009.268789) : Could not get pointer to binary resource for file:

(Sat Jan 31 10:49:56 2009.268789) : C:\Windows\system32\DRIVERS\monitor.sys[MonitorWMI](Sat Jan 31 10:49:56 2009.268789) :

(Sat Jan 31 10:49:56 2009.268789) : ***************************************

(Sat Jan 31 19:03:36 2009.268742) : ***************************************

(Sat Jan 31 19:03:36 2009.268758) : Could not get pointer to binary resource for file:

(Sat Jan 31 19:03:36 2009.268758) : C:\Windows\system32\drivers\ndis.sys[MofResourceName](Sat Jan 31 19:03:36 2009.268758) :

(Sat Jan 31 19:03:36 2009.268758) : ***************************************

(Sat Jan 31 19:03:37 2009.268774) : ***************************************

(Sat Jan 31 19:03:37 2009.268774) : Could not get pointer to binary resource for file:

(Sat Jan 31 19:03:37 2009.268774) : C:\Windows\system32\DRIVERS\msiscsi.sys[MofResource](Sat Jan 31 19:03:37 2009.268774) :

(Sat Jan 31 19:03:37 2009.268774) : ***************************************

(Sat Jan 31 19:03:37 2009.268789) : ***************************************

(Sat Jan 31 19:03:37 2009.268789) : Could not get pointer to binary resource for file:

(Sat Jan 31 19:03:37 2009.268789) : C:\Windows\system32\DRIVERS\monitor.sys[MonitorWMI](Sat Jan 31 19:03:37 2009.268789) :

(Sat Jan 31 19:03:37 2009.268789) : ***************************************

(Sun Feb 01 08:33:12 2009.269881) : ***************************************

(Sun Feb 01 08:33:12 2009.269881) : Could not get pointer to binary resource for file:

(Sun Feb 01 08:33:12 2009.269881) : C:\Windows\system32\drivers\ndis.sys[MofResourceName](Sun Feb 01 08:33:12 2009.269881) :

(Sun Feb 01 08:33:12 2009.269881) : ***************************************

(Sun Feb 01 08:33:12 2009.269897) : ***************************************

(Sun Feb 01 08:33:12 2009.269897) : Could not get pointer to binary resource for file:

(Sun Feb 01 08:33:12 2009.269897) : C:\Windows\system32\DRIVERS\msiscsi.sys[MofResource](Sun Feb 01 08:33:12 2009.269897) :

(Sun Feb 01 08:33:12 2009.269897) : ***************************************

(Sun Feb 01 08:33:12 2009.269897) : ***************************************

(Sun Feb 01 08:33:12 2009.269897) : Could not get pointer to binary resource for file:

(Sun Feb 01 08:33:12 2009.269897) : C:\Windows\system32\DRIVERS\monitor.sys[MonitorWMI](Sun Feb 01 08:33:12 2009.269897) :

(Sun Feb 01 08:33:12 2009.269897) : ***************************************

(Mon Feb 02 09:10:58 2009.267760) : ***************************************

(Mon Feb 02 09:10:59 2009.267775) : Could not get pointer to binary resource for file:

(Mon Feb 02 09:10:59 2009.267775) : C:\Windows\system32\drivers\ndis.sys[MofResourceName](Mon Feb 02 09:10:59 2009.267775) :

(Mon Feb 02 09:10:59 2009.267775) : ***************************************

(Mon Feb 02 09:10:59 2009.267822) : ***************************************

(Mon Feb 02 09:10:59 2009.267822) : Could not get pointer to binary resource for file:

(Mon Feb 02 09:10:59 2009.267822) : C:\Windows\system32\DRIVERS\msiscsi.sys[MofResource](Mon Feb 02 09:10:59 2009.267822) :

(Mon Feb 02 09:10:59 2009.267822) : ***************************************

(Mon Feb 02 09:10:59 2009.267838) : ***************************************

(Mon Feb 02 09:10:59 2009.267838) : Could not get pointer to binary resource for file:

(Mon Feb 02 09:10:59 2009.267838) : C:\Windows\system32\DRIVERS\monitor.sys[MonitorWMI](Mon Feb 02 09:10:59 2009.267838) :

(Mon Feb 02 09:10:59 2009.267838) : ***************************************

(Mon Feb 02 09:35:24 2009.275638) : ***************************************

(Mon Feb 02 09:35:24 2009.275638) : Could not get pointer to binary resource for file:

(Mon Feb 02 09:35:24 2009.275638) : C:\Windows\system32\drivers\ndis.sys[MofResourceName](Mon Feb 02 09:35:24 2009.275638) :

(Mon Feb 02 09:35:24 2009.275638) : ***************************************

(Mon Feb 02 09:35:24 2009.275653) : ***************************************

(Mon Feb 02 09:35:24 2009.275653) : Could not get pointer to binary resource for file:

(Mon Feb 02 09:35:24 2009.275653) : C:\Windows\system32\DRIVERS\msiscsi.sys[MofResource](Mon Feb 02 09:35:24 2009.275653) :

(Mon Feb 02 09:35:24 2009.275653) : ***************************************

(Mon Feb 02 09:35:24 2009.275653) : ***************************************

(Mon Feb 02 09:35:24 2009.275653) : Could not get pointer to binary resource for file:

(Mon Feb 02 09:35:24 2009.275669) : C:\Windows\system32\DRIVERS\monitor.sys[MonitorWMI](Mon Feb 02 09:35:24 2009.275669) :

(Mon Feb 02 09:35:24 2009.275669) : ***************************************

(Mon Feb 02 18:16:13 2009.31524385) : ***************************************

(Mon Feb 02 18:16:13 2009.31524401) : Could not get pointer to binary resource for file:

(Mon Feb 02 18:16:13 2009.31524401) : C:\Windows\system32\drivers\ndis.sys[MofResourceName](Mon Feb 02 18:16:13 2009.31524401) :

(Mon Feb 02 18:16:13 2009.31524401) : ***************************************

(Mon Feb 02 18:16:13 2009.31524416) : ***************************************

(Mon Feb 02 18:16:13 2009.31524416) : Could not get pointer to binary resource for file:

(Mon Feb 02 18:16:13 2009.31524416) : C:\Windows\system32\DRIVERS\msiscsi.sys[MofResource](Mon Feb 02 18:16:13 2009.31524416) :

(Mon Feb 02 18:16:13 2009.31524416) : ***************************************

(Mon Feb 02 18:16:13 2009.31524432) : ***************************************

(Mon Feb 02 18:16:13 2009.31524432) : Could not get pointer to binary resource for file:

(Mon Feb 02 18:16:13 2009.31524432) : C:\Windows\system32\DRIVERS\monitor.sys[MonitorWMI](Mon Feb 02 18:16:13 2009.31524432) :

(Mon Feb 02 18:16:13 2009.31524432) : ***************************************

Link to comment
Share on other sites
Grand Master

soldier1st

Posted
Posted

the WMI database itself is corrupt or missing data.

Knowledgebase - Repair Corrupt WMI Services

Repairing and re-registering the WMI Services

Rebuilding the WMI Repository

If you experience behavior when using WMI, such as application errors or scripts that used to work are no longer working, you may have a corrupted WMI repository. To fix a corrupted WMI repository, you have to reinstall WMI. Follow these steps:

Click Start, Run and type CMD

Type this command and press Enter:

net stop winmgmt

Using Windows Explorer, navigate to %systemroot%\system32\wbem directory and delete the Repository directory. By default, the repository folder is located in the C:\Windows\system32\wbem directory.

Switch to Command Prompt window, and type:

net start winmgmt

Re-registering the WMI components

The .DLL and .EXE files used by WMI are located in %windir%\system32\wbem. You might need to re-register all the .DLL and .EXE files in this directory. If you are running a 64-bit system you might also need to check for .DLLs and .EXE files in %windir%\sysWOW64\wbem.

To re-register the WMI components, run the following commands at the command prompt:

cd /d %windir%\system32\wbem

for %i in (*.dll) do RegSvr32 -s %i

for %i in (*.exe) do %i /RegServer

Link to comment
Share on other sites
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.