|
|
>> Could that be the corrupted key interfering with DCOM and WMI?
Could be! Norton products... I would uninstall them if you ask me.
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
The Winhelponline Blog: http://www.winhelponline.com/blog
Windows® Troubleshooting: www.winhelponline.com">http://www.winhelponline.com
"Eugenio" <ojedaeug@xxxxxxxxxx(donotspam)> wrote in message
news:A3C78858-3C9C-4BF8-ACD4-C42B7DD2B405@xxxxxxxxxxxxxxxx
> Ramesh,
> I doing some research I find that that particular key refers to a Norton
> Symantec ccEventManager. It seems that there is a Norton WMI Update as
> part
> of Norton 2005. Could that be the corrupted key interfering with DCOM and
> WMI?. It also seems that Norton has some information on the WMI Update and
> I
> am going to be looking into. Maybe I can uninstall that Update if present
> in
> the WinXP PC.
> Regards,
> Eugenio
>
>
> "Ramesh, MS-MVP" wrote:
>
>> Hi Eugenio,
>>
>> Can you copy the complete DCOMServer error shown in the Event Viewer and
>> post here? Note that there is a copy button (with no text, only graphic)
>> in
>> the Event Properties dialog. Clicking that button copies the event to the
>> Clipboard.
>>
>> --
>> Regards,
>>
>> Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
>> The Winhelponline Blog: www.winhelponline.com/blog">http://www.winhelponline.com/blog
>> Windows® Troubleshooting: www.winhelponline.com">http://www.winhelponline.com
>>
>>
>> "Eugenio" <ojedaeug@xxxxxxxxxx(donotspam)> wrote in message
>> news:E8968C53-CA35-47E3-BAE2-412B0A43CC06@xxxxxxxxxxxxxxxx
>> > Ramesh,
>> > I ran the comprehensive rebuild method, but no positive results, I am
>> > still
>> > getting the "can' collect information..." message.
>> > The Event Viewer is showing a DCOM error, something like: "unable to
>> > start
>> > DCOMServer, the system cnnot find the file specified... happened while
>> > starting, and them something either blank or mixed specia characters.
>> > I
>> > also
>> > ran the
>> > WIMDiag.vbs with the sale results mentioned in my prior note, with
>> > errors
>> > with "....the registry settings of COM/DCOM has been damaged or wrongly
>> > modified..."
>> >
>> > I hope you can decypher all the above and come up with the suggestions.
>> > Thanks for your valuable support, I appreciate all this very much.
>> > Eugenio
>> >
>> >
>> >
>> >
>> > "Ramesh, MS-MVP" wrote:
>> >
>> >> Try repairing WMI using the steps here:
>> >> windowsxp.mvps.org/repairwmi.htm">http://windowsxp.mvps.org/repairwmi.htm
>> >>
>> >> See section "Comprehensive rebuild method" in that page.
>> >>
>> >> --
>> >> Regards,
>> >>
>> >> Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
>> >> The Winhelponline Blog: www.winhelponline.com/blog">http://www.winhelponline.com/blog
>> >> Windows® Troubleshooting: www.winhelponline.com">http://www.winhelponline.com
>> >>
>> >>
>> >> "Eugenio" <ojedaeug@xxxxxxxxxx(donotspam)> wrote in message
>> >> news:7EDE4EBB-FD10-4EF9-9FA3-8E2B9177D4E4@xxxxxxxxxxxxxxxx
>> >> > Ramesh, no, it did not help. I went thru the info and took the
>> >> > actions,
>> >> > but
>> >> > nothing, msinfo32 keeps on not being able to display information.
>> >> > I tried the WMIDiag.vbs, and here are the restuls:
>> >> > Error: WMI ADAP status. I ran the winmgmt.exe /clearadap and
>> >> > /resyncperf.
>> >> > Error: Error WMI moniker connection, root, ox1AD activex component
>> >> > can't
>> >> > create object.
>> >> > Errors external to WMI: Registry info for DCOM, changed COM/DCOM
>> >> > keys
>> >> > have
>> >> > been changed by some program. I ran regsvr32.exe for ole32.dll and
>> >> > oleaut32.dll
>> >> > No positive results. What else can I do? Would I have to
>> >> > reinstall
>> >> > WinXP,
>> >> > which I am reluctant to do?
>> >> > Thanks for all your help and insight into the windows magical world.
>> >> > Eugenio
>> >> >
>> >> >
>> >> >
>> >> > "Ramesh, MS-MVP" wrote:
>> >> >
>> >> >> Does this help?
>> >> >>
>> >> >> Fix for Msinfo32.exe Error Can't Collect Information - The
>> >> >> Winhelponline
>> >> >> Blog:
>> >> >> www.winhelponline.com/blog/fix-for-msinfo32exe-error-cant-collect-information/">http://www.winhelponline.com/blog/fix-for-msinfo32exe-error-cant-collect-information/
>> >> >>
>> >> >> --
>> >> >> Regards,
>> >> >>
>> >> >> Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
>> >> >> The Winhelponline Blog: www.winhelponline.com/blog">http://www.winhelponline.com/blog
>> >> >> Windows® Troubleshooting: www.winhelponline.com">http://www.winhelponline.com
>> >> >>
>> >> >>
>> >> >> "Eugenio" <ojedaeug@xxxxxxxxxx(donotspam)> wrote in message
>> >> >> news:22247CEB-3712-40B7-8483-7506AAD951FF@xxxxxxxxxxxxxxxx
>> >> >> > Rames, thanks for your suggetion.
>> >> >> > I ran the regsvr32 and they executed OK. I also did the Mark
>> >> >> > recommendations. I think the wmi data is OK, and what may be
>> >> >> > wrong
>> >> >> > is
>> >> >> > the
>> >> >> > system info display --isn't this part of internet explorer?
>> >> >> > Thanks,
>> >> >> > Eugenio
>> >> >> >
>> >> >> >
>> >> >> > "Ramesh, MS-MVP" wrote:
>> >> >> >
>> >> >> >> Msinfo32.exe Generates a "Can't Collect Information" Error
>> >> >> >> Message:
>> >> >> >> support.microsoft.com/?kbid=323209">http://support.microsoft.com/?kbid=323209
>> >> >> >>
>> >> >> >> If that does not help, try these commands from Start/Run:
>> >> >> >>
>> >> >> >> regsvr32 %Windir%\system32\wbem\wbemprox.dll
>> >> >> >> regsvr32 %Windir%\system32\wbem\wbemcore.dll
>> >> >> >> regsvr32 %Windir%\system32\wbem\wbemsvc.dll
>> >> >> >> regsvr32 %Windir%\system32\wbem\fastprox.dll
>> >> >> >>
>> >> >> >> --
>> >> >> >> Regards,
>> >> >> >>
>> >> >> >> Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
>> >> >> >> The Winhelponline Blog: www.winhelponline.com/blog">http://www.winhelponline.com/blog
>> >> >> >> Windows® Troubleshooting: www.winhelponline.com">http://www.winhelponline.com
>> >> >> >>
>> >> >> >>
>> >> >> >> "Eugenio" <ojedaeug@xxxxxxxxxx(donotspam)> wrote in message
>> >> >> >> news:44EC5E4A-1DBD-4FBE-83A5-DAA87BDDB6F2@xxxxxxxxxxxxxxxx
>> >> >> >> > When I try to open msinfo32 I get a message: "cannot access
>> >> >> >> > the
>> >> >> >> > windows
>> >> >> >> > management instrumentation sotware"... Is there a way of
>> >> >> >> > fixing
>> >> >> >> > this?
>> >> >> >> > thanks,
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
|
|