Lost System Information

  • Thread starter Thread starter Roger
  • Start date Start date
R

Roger

Hi,
I have xp pro sp2 and for reasons unknown I cannot use system info link.
When I access it I have box open with words Cant Collect information, and
more stating Cannot access Windows Management instrumentation software,
Windows Management files may be moved or missing ! I have run Disc Check
fully and defrag without any change. My PC appears to operate as normal,
but can you assist with problem please.

Roger
------------------------------------------------------ ------------------------------------------------------
 
Roger said:
Hi,
I have xp pro sp2 and for reasons unknown I cannot use system info link.
When I access it I have box open with words Cant Collect information, and
more stating Cannot access Windows Management instrumentation software,
Windows Management files may be moved or missing ! I have run Disc Check
fully and defrag without any change. My PC appears to operate as normal,
but can you assist with problem please.

Start here:

http://support.microsoft.com/kb/323209
Msinfo32.exe Generates a "Can't Collect Information" Error Message

John
 
John John - MVP said:
Start here:

http://support.microsoft.com/kb/323209
Msinfo32.exe Generates a "Can't Collect Information" Error Message

John

The above was of no use, on event viewer showing error since end of May
saying it could be disc space , I have loads or Memory.
Also repository files may be corrupted and should be deleted and re-boot !

Roger
=============================
==================================
 
Roger said:
The above was of no use, on event viewer showing error since end of May
saying it could be disc space , I have loads or Memory.
Also repository files may be corrupted and should be deleted and re-boot !

So the

* Event Log
* Windows Management Instrumentation
* Remote Procedure Call (RPC)

services are set to Automatic start and all of them are running?

Where do you get the message telling you to delete the repository files?

To delete the WMI repository:

1- Stop the Windows Management Instrumentation service.
2- Delete the \WINDOWS\system32\wbem directory.
3- Restart the WMI service.

John
 
John John - MVP said:
So the

* Event Log
* Windows Management Instrumentation
* Remote Procedure Call (RPC)

services are set to Automatic start and all of them are running?

Where do you get the message telling you to delete the repository files?

To delete the WMI repository:

1- Stop the Windows Management Instrumentation service.
2- Delete the \WINDOWS\system32\wbem directory.
3- Restart the WMI service.

John

All above running on Auto, when clicking on one of the error's in event log
it gave that advice about repository files.

I am about to go through procedure now to delete, will report back on
progress.
Roger
---------------------------------------------------- ------------------------------------
 
Roger said:
All above running on Auto, when clicking on one of the error's in event
log it gave that advice about repository files.

I am about to go through procedure now to delete, will report back on
progress.
Roger
---------------------------------------------------- ------------------------------------
Well I have tried a couple of ways advised on the below site and I still
get error message when trying to obtain system info, because of problem with
WMI
http://blog.perfectspace.com/2004/07/21/windows-management-instrumentation-wmi-error/

Roger PS Its doing my old head in now
 
Roger said:
Well I have tried a couple of ways advised on the below site and I still
get error message when trying to obtain system info, because of problem with
WMI
http://blog.perfectspace.com/2004/07/21/windows-management-instrumentation-wmi-error/

Roger PS Its doing my old head in now

This can be a *very* difficult problem to resolve! Try the methods for
Windows XP here:

http://windowsxp.mvps.org/repairwmi.htm

If the suggestions and methods shown there fail to repair things then
the only other fix that I know of is an in-place upgrade (repair
install) of the operating system.

http://www.michaelstevenstech.com/xp_in_place_upgrade.htm

http://support.microsoft.com/kb/978788
How to perform an in-place upgrade (reinstallation) of Windows XP

John
 
John John - MVP said:
This can be a *very* difficult problem to resolve! Try the methods for
Windows XP here:

http://windowsxp.mvps.org/repairwmi.htm

If the suggestions and methods shown there fail to repair things then the
only other fix that I know of is an in-place upgrade (repair install) of
the operating system.

http://www.michaelstevenstech.com/xp_in_place_upgrade.htm

http://support.microsoft.com/kb/978788
How to perform an in-place upgrade (reinstallation) of Windows XP

John thank you for links, on the one
http://windowsxp.mvps.org/repairwmi.htm for winxp sp2 is that all i need
to do and where would I access the setup log file where results are
stored, would this be of any use ? Also would it help if I tried
spc/scannow action !

Roger
 
Roger said:
John thank you for links, on the one
http://windowsxp.mvps.org/repairwmi.htm for winxp sp2 is that all i need
to do

Follow the instructions on the page:

Click Start, Run and type the following command:

rundll32 wbemupgd, UpgradeRepository



and where would I access the setup log file where results are
stored, > would this (log) be of any use ?

The log might be of use, it might point to an obvious cause for the
problem but otherwise the log will only be useful if you understand the
WMI inner workings and know how to go about fixing it. As explained on
the page the log will be in the \WINDOWS\system32\wbem\Logs folder.


Also would it help if I tried
spc/scannow action !

If the rundll32 wbemupgd, UpgradeRepository command doesn't help proceed
to the next step and re-register the WMI components:

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


If that doesn't fix things then try to rebuild/reinstall the WMI
components. If you have SP3 installed on your computer your Windows XP
CD will have to have SP3 slipstreamed into it, a search on the net will
provide information on how to slipstream the Service Pack into your
Windows XP CD:

http://search.yahoo.com/search;_ylt...lipstream"+"SP3"&fr=yfp-t-501&fr2=sfp&iscqry=

With your Windows XP SP3 cd at hand:

Click Start, Run and type the following command, and press ENTER:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

The above is all on one line, to avoid errors you can copy and paste it
from the website to your Run box.

If rebuilding/reinstalling the WMI components doesn't fix things then
the in-place upgrade is about the only remaining way that I know to
repair a broken WMI. You can try the sfc /scannow command before doing
the in-place upgrade but I doubt that it will be of any help.

John
 
John John - MVP said:
Follow the instructions on the page:

Click Start, Run and type the following command:

rundll32 wbemupgd, UpgradeRepository



and where would I access the setup log file where results are

The log might be of use, it might point to an obvious cause for the
problem but otherwise the log will only be useful if you understand the
WMI inner workings and know how to go about fixing it. As explained on
the page the log will be in the \WINDOWS\system32\wbem\Logs folder.


Also would it help if I tried

If the rundll32 wbemupgd, UpgradeRepository command doesn't help proceed
to the next step and re-register the WMI components:

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


If that doesn't fix things then try to rebuild/reinstall the WMI
components. If you have SP3 installed on your computer your Windows XP CD
will have to have SP3 slipstreamed into it, a search on the net will
provide information on how to slipstream the Service Pack into your
Windows XP CD:
[snip] John well done, the above rundll32upgrade worked. I now have
system info showing and hope associated item work as well.
One more question re above command prompts, forgive my ignorance would they
all be entered as shown on screen or one at a time on a different procedure.
Just for the record future use. And I am storing those links you never know.
It proves that corrupted files action was negative so files were missing
maybe.

Kind Regards Roger
 
Roger said:
John John - MVP said:
Follow the instructions on the page:

Click Start, Run and type the following command:

rundll32 wbemupgd, UpgradeRepository



and where would I access the setup log file where results are
The log might be of use, it might point to an obvious cause for the
problem but otherwise the log will only be useful if you understand the
WMI inner workings and know how to go about fixing it. As explained on
the page the log will be in the \WINDOWS\system32\wbem\Logs folder.


Also would it help if I tried
If the rundll32 wbemupgd, UpgradeRepository command doesn't help proceed
to the next step and re-register the WMI components:

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


If that doesn't fix things then try to rebuild/reinstall the WMI
components. If you have SP3 installed on your computer your Windows XP CD
will have to have SP3 slipstreamed into it, a search on the net will
provide information on how to slipstream the Service Pack into your
Windows XP CD:
[snip] John well done, the above rundll32upgrade worked. I now have
system info showing and hope associated item work as well.
One more question re above command prompts, forgive my ignorance would they
all be entered as shown on screen or one at a time on a different procedure.
Just for the record future use. And I am storing those links you never know.
It proves that corrupted files action was negative so files were missing
maybe.

Glad to see that you got it fixed. As for the commands they would be
run one at a time, one after the other, pressing <Enter> after each.

John
 
John John - MVP said:
Roger said:
John John - MVP said:
Roger wrote:
Roger wrote:
Roger wrote:
Roger wrote:
Hi,
I have xp pro sp2 and for reasons unknown I cannot use system
info link. When I access it I have box open with words Cant
Collect information, and more stating Cannot access Windows
Management instrumentation software, Windows Management files
may be moved or missing ! I have run Disc Check fully and
defrag without any change. My PC appears to operate as normal,
but can you assist with problem please.
Start here:

http://support.microsoft.com/kb/323209
Msinfo32.exe Generates a "Can't Collect Information" Error
Message

John
The above was of no use, on event viewer showing error since end
of May saying it could be disc space , I have loads or Memory.
Also repository files may be corrupted and should be deleted and
re-boot !
So the

* Event Log
* Windows Management Instrumentation
* Remote Procedure Call (RPC)

services are set to Automatic start and all of them are running?

Where do you get the message telling you to delete the repository
files?

To delete the WMI repository:

1- Stop the Windows Management Instrumentation service.
2- Delete the \WINDOWS\system32\wbem directory.
3- Restart the WMI service.

John
All above running on Auto, when clicking on one of the error's in
event log it gave that advice about repository files.

I am about to go through procedure now to delete, will report back
on progress.
Roger
----------------------------------------------------
------------------------------------
Well I have tried a couple of ways advised on the below site and I
still get error message when trying to obtain system info, because of
problem with WMI
http://blog.perfectspace.com/2004/07/21/windows-management-instrumentation-wmi-error/

Roger PS Its doing my old head in now
This can be a *very* difficult problem to resolve! Try the methods
for Windows XP here:

http://windowsxp.mvps.org/repairwmi.htm

If the suggestions and methods shown there fail to repair things then
the only other fix that I know of is an in-place upgrade (repair
install) of the operating system.

http://www.michaelstevenstech.com/xp_in_place_upgrade.htm

http://support.microsoft.com/kb/978788
How to perform an in-place upgrade (reinstallation) of Windows XP

John thank you for links, on the one
http://windowsxp.mvps.org/repairwmi.htm for winxp sp2 is that all i
need to do
Follow the instructions on the page:

Click Start, Run and type the following command:

rundll32 wbemupgd, UpgradeRepository



and where would I access the setup log file where results are
stored, > would this (log) be of any use ?
The log might be of use, it might point to an obvious cause for the
problem but otherwise the log will only be useful if you understand the
WMI inner workings and know how to go about fixing it. As explained on
the page the log will be in the \WINDOWS\system32\wbem\Logs folder.


Also would it help if I tried
spc/scannow action !
If the rundll32 wbemupgd, UpgradeRepository command doesn't help proceed
to the next step and re-register the WMI components:

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


If that doesn't fix things then try to rebuild/reinstall the WMI
components. If you have SP3 installed on your computer your Windows XP
CD will have to have SP3 slipstreamed into it, a search on the net will
provide information on how to slipstream the Service Pack into your
Windows XP CD:
[snip] John well done, the above rundll32upgrade worked. I now have
system info showing and hope associated item work as well.
One more question re above command prompts, forgive my ignorance would
they all be entered as shown on screen or one at a time on a different
procedure.
Just for the record future use. And I am storing those links you never
know. It proves that corrupted files action was negative so files were
missing maybe.

Glad to see that you got it fixed. As for the commands they would be run
one at a time, one after the other, pressing <Enter> after each.

John What I forgot to mention when looking through report in log noticed
a point that mentioned a reboot, which i did after.
 
Back
Top