Re: MP Problems at secondary site
- From: "John" <hush@xxxxxxxxxxxxxx>
- Date: Tue, 19 Jul 2005 15:24:38 +0100
Hi Kim,
Thanks very much for that. I ran the RepairWMISetup and rebooted and can now
attach using wbemtest to the root\ccm class. The MP has installed correctly
now. I've run the post installation test on the MP using MPTroubleshooter
from the Toolkit and it only fails on one thing. The Testing MPCert HTTP
Request Functionality shows an error of "Object reference not set to an
instance of an object.
When i check IIS, I see that the folder which should hold objects for the
MPCert is empty, so when I go to the webpage for MPCert, and the same for
MPList, I get the expected results.
Thanks
John
"Kim Oppalfens" <kim@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1d47115fd3ba468d98a07f@xxxxxxxxxxxxxxxxxxxxxxx
>
> Here you go (this is everything I have on wmi troubleshooting)
> For Windows Server 2003 SP1 builds, invoke the "check" functionality as
> follows:
>
> c:\>rundll32 wbemupgd, CheckWMISetup
>
> "Repair" functionality is invoked as:
>
> c:\>rundll32 wbemupgd, RepairWMISetup
>
> The WMI product development team have put a FAQ on this hot topic and
> I?d highly recommend you to look into it.
> http://www.microsoft.com/technet/scriptcenter/resources/wmifaq.mspx
>
> Additionally I am including some more specific information as it applies
> to consistency checker and repair functionality we have put in XP SP2
> and W2K3 SP1 for WMI Repository.
>
> On XP SP2 and W2K3 we?ve exposed ?check? and ?repair? functionality that
> you can use right from the code without having to use any tool or
> script.
> The way this check and repair functionality is exposed on XPSP2 slightly
> differs on W2K3 SP1 bits (current builds)
>
> On XPSP2 you would type following from command line?(Note: that
> UpgradeRepository is case sensitive). Also this code was made available
> for XP SP2 upgrade path when we check repository for corruption and
> rebuild (Upgrade) repository for you. However it is okay to use to
> validate the repository for any corruptions and fix it. NOTE: This could
> result in data loss for all static entries in repository. Also the old
> repository is not discarded but just renamed.
>
> C:\> rundll32 wbemupgd, UpgradeRepository
> The result of this operation can be verified by viewing the setup.log
> file in your %WINDOWS%\system32\wbem\Logs directory. On my XP SP2 system
> with no repository issue, I got following entries?
>
> (Thu Oct 21 11:46:51 2004):
> ========================================================================
> ========
>
> (Thu Oct 21 11:46:51 2004): Beginning WBEM Service Pack Installation
>
> (Thu Oct 21 11:46:51 2004): Current build of wbemupgd.dll is
> 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
>
> (Thu Oct 21 11:46:51 2004): Current build of wbemcore.dll is
> 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
>
> (Thu Oct 21 11:46:54 2004): Wbemupgd.dll Service Security upgrade
> succeeded (XP SP update).
>
> (Thu Oct 21 11:46:54 2004): WBEM Service Pack Installation completed.
>
> (Thu Oct 21 11:46:54 2004):
> ========================================================================
> ========
>
>
>
>
> In article <ewzDQjFjFHA.3568@xxxxxxxxxxxxxxxxxxxx>, hush@xxxxxxxxxxxxxx
> says...
>> Hi Kim
>>
>> when I try that, I get a WMI failure error, Description is Generic
>> Failure..
>> I get the same error if I try to connect to root\cimv2 and root\default.
>> Looks like WMI is corrupt on that server. Is there a way to
>> reinstall/repair
>> WMI on Windows 2003 Server?
>>
>> Thanks
>>
>> John
>>
>>
>> "Kim Oppalfens" <kim@xxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:MPG.1d46f14338d1470a98a077@xxxxxxxxxxxxxxxxxxxxxxx
>> >
>> > Ok, looks like a wmi issue.
>> >
>> > On the runbox type wbemtest
>> > then try to connect to root\ccm.
>> >
>> > Kim Oppalfens
>> > In article <OwoTAa7iFHA.2484@xxxxxxxxxxxxxxxxxxxx>, hush@xxxxxxxxxxxxxx
>> > says...
>> >> Hi
>> >>
>> >> I've come across a problem with the MP at my secondary site.
>> >> Initially,
>> >> it
>> >> was working and about half a dozen machines installed Advanced client
>> >> successfully, and inventories were take.
>> >>
>> >> However, over the Weekend, my component status for the MP went
>> >> critical,
>> >> and
>> >> logged errors 5432 and 5433 every hour. It appears there is a problem
>> >> with
>> >> the WMI on the Server.
>> >>
>> >> I've checked services on the server, SMS Agent Host is stopped, and
>> >> does
>> >> not
>> >> restart. It starts then stops immediately. When I look at the
>> >> properties
>> >> of
>> >> the service, I get a "WMI Generic failure" errors when I click the
>> >> Dependencies tab.
>> >>
>> >> I have tried uninstalling the MP, rebooting the Server, the
>> >> reinstalling
>> >> (I
>> >> waited about 1 hour before reinstalling). But MP now fails to
>> >> reinstall.
>> >> MPSetup.Log
>> >> file shows:
>> >>
>> >> <07-18-2005 12:13:33> MP Setup Started....
>
> --
> Kim Oppalfens
> MVP SMS
> Computacenter Belgium
.
- Follow-Ups:
- Re: MP Problems at secondary site
- From: Kim Oppalfens
- Re: MP Problems at secondary site
- References:
- MP Problems at secondary site
- From: John
- Re: MP Problems at secondary site
- From: Kim Oppalfens
- Re: MP Problems at secondary site
- From: John
- Re: MP Problems at secondary site
- From: Kim Oppalfens
- MP Problems at secondary site
- Prev by Date: Re: Some clients - incorrect subnet
- Next by Date: Re: MP Problems at secondary site
- Previous by thread: Re: MP Problems at secondary site
- Next by thread: Re: MP Problems at secondary site
- Index(es):
Relevant Pages
|
Loading
