Re: Error with Exchange 2000 SP2 upgrade

From: Kevin (kevans_at_newsgroup.nospam)
Date: 08/05/04


Date: Thu, 5 Aug 2004 13:18:45 -0400

Yes I have thanks. No luck, because when I run WMIMGMT.MSC, you can't
change the security for anything because basically nothing work in that
management console. If I pull up properties, none of the tabs have data
behind them; the only thing I get is "class not registered", which is the
same error I get with the SP2 upgrade. It's like WMI doesn't exist anymore.

I upgraded this Win2000 server to Win2003 first before doing all of this.
I'm finding information that WMI changed to a certain degree, although it
still exists. It's almost like it's been uninstalled and I can't install it
again (that I know of), but without it, I can't proceed with upgrades.

Perhaps I should have upgraded Exchange before Windows? I don't know, but
it's too late now if that's the case.

Any other ideas?
Kevin

"Jan Englund" <Jan.englund@NOSPAM.capgeminidotcom> wrote in message
news:%23RRMSIveEHA.632@TK2MSFTNGP12.phx.gbl...
> Hi kevin
> Have you tired the following article?
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q298928
> Hope it helps
>
> --
> Best Regards
> Jan Englund
> Capgemini Sweden
> MCSA 2000/2003, MCSE NT4/2000/2003
> MCSA 2000/2003:Messaging MCSE2000:Messaging
> www.se.capgemini.com
> "Kevin" <kevans@newsgroup.nospam> wrote in message
> news:%23LVlUEueEHA.3348@TK2MSFTNGP12.phx.gbl...
> > I'm trying to install Exchange 2000 SP2 in preparation for the an
Exchange
> > 2003 upgrade. However I get an error "Setup was unable to set
permissions
> > on the WMI namespace. The error code is: 0x80040154 (340): Class not
> > registered"
> >
> > It then references a MS knowledge base article on how to manually set
> > permissions, however this involves running the wmimgmt.msc management
> > console and performing steps there. I don't see much in that console
> except
> > more references to a class not being registered.
> >
> > Basically, I don't know why I need Windows Management Instrumentation
> (WMI)
> > to run Exchange, or whether it's really required, or even if I have it;
> but
> > it's stopping me from upgrading Exchange which is a big problem.
> >
> > Please help as I'm stuck on this and can't get to Exchange 2003. This
> > process has also broken OWA, which I'm ignoring until we get through
this
> > and to Ex2003, but that is causing big problems. If nothing else, any
> > insight on how & why WMI interacts with Exchange
> > 2000 would be appeciated. I've included a snippet below of the error
log.
> >
> > TIA,
> > Kevin
> >
> > [20:48:05] ++++ Starting interpreter on file
> > c:\exchangesp3temp\server\setup\i386\exchange\wmiprov.ins ++++
> > [20:48:05] Interpreting line
> > <CreateProcess:C:\EXCHSRVR\bin;C:\EXCHSRVR\bin\exmgmt.exe
/install;60000>
> > [20:48:05] Process created ... waiting (60000)
> > [20:48:05] Process has exited with 00000000
> > [20:48:05] Interpreting line
> >
>
<CreateProcess:C:\WINNT\system32\WBEM;C:\WINNT\system32\WBEM\mofcomp.exe -cl
> > ass:forceupdate "C:\WINNT\system32\WBEM\exmgmt.mof";600000>
> > [20:48:05] Process created ... waiting (600000)
> > [20:48:05] Process has exited with 0x000003
> > [20:48:05] The command
> >
> > C:\WINNT\system32\WBEM\mofcomp.exe -class:forceupdate
> > "C:\WINNT\system32\WBEM\exmgmt.mof"
> >
> > failed, returning error code 3 (The system cannot find the path
> specified.).
> > ScCreateProcess (y:\admin\src\libs\exsetup\hiddenw1.cxx:1803)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:48:05] CInsParser::ScProcessLine
> > (y:\admin\src\libs\exsetup\hiddenw1.cxx:1226)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:48:05] Processing file
> > 'c:\exchangesp3temp\server\setup\i386\exchange\wmiprov.ins', at or near
> line
> > 5
> >
>
(CreateProcess:C:\WINNT\system32\WBEM;C:\WINNT\system32\WBEM\mofcomp.exe -cl
> > ass:forceupdate "C:\WINNT\system32\WBEM\exmgmt.mof";600000)
> > CInsParser::ScProcessLine (y:\admin\src\libs\exsetup\hiddenw1.cxx:486)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:48:05] Registry file name:
> > 'c:\exchangesp3temp\server\setup\i386\exchange\wmiprov.ins'
> > CRegistryManager::ScProcessFile
> > (y:\admin\src\udog\setupbase\tools\regmgr.cxx:95)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:48:05] Filename = '%sourcedir%\wmiprov' CBaseAtom::ScAddRegistryKeys
> > (y:\admin\src\udog\setupbase\basecomp\baseatom.cxx:1244)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:48:05] CAtomWMIProv::ScAddRegistryKeys
> > (y:\admin\src\udog\exsetdata\components\server\a_wmiprov.cxx:356)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:48:05] Leaving CAtomWMIProv::ScAddRegistryKeys
> > [20:48:05] CAtomWMIProv::ScServicePackUpdate
> > (y:\admin\src\udog\exsetdata\components\server\a_wmiprov.cxx:416)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:48:05] Leaving CAtomWMIProv::ScServicePackUpdate
> > [20:48:05] mode = 'Update' (61957) CBaseAtom::ScSetup
> > (y:\admin\src\udog\setupbase\basecomp\baseatom.cxx:788)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:49:38] Setup encountered an error during Microsoft Exchange System
> > Management Tools of Update component task. CBaseComponent::ScSetup
> > (y:\admin\src\udog\setupbase\basecomp\basecomp.cxx:1078)
> > Error code 0XC103798A (31114): An internal component has
> failed.
> > [20:49:38
> >
> >
> >
>
>



Relevant Pages

  • Re: Does it matter?
    ... [[A type of tool you can add to a console supported by Microsoft Management ... Disk Management is a stand-alone. ... Performance Logs and Alerts has nothing to do With System Restore. ...
    (microsoft.public.windowsxp.basics)
  • Re: Security Simplification
    ... If you have a decent Anti-Virus product deployed on each end-point, make sure you deploy a management console to centralize the installation of software agents and virus definitions updates. ... Newer products and services provide Virtual Patch technology, which means that if the vulnerability scanner correlates an existing vendor advisory with an exposed system, the scanner talks to the IPS devices on the network to block any attempt to take advantage of that vulnerability. ... Arm your enterprise with BigFix, the single converged IT security and operations engine. ...
    (Security-Basics)
  • RE: Sizing CPU
    ... management simply does not want to hear that an upgrade is ... Single Processor doing to get these numbers? ... We converted from VSE to z/OS about 2 years ago and they were able to ...
    (bit.listserv.ibm-main)
  • ES40s wont boot!
    ... and wwidmgr show all 4 of the units, so I think that part's okay. ... a copy of the AS4100's system disk, ... (Every console variable I could think of seems to be okay. ... site (in-box upgrade of CPUs from 667MHz to 833MHz), ...
    (comp.os.vms)
  • Re: MMC unable sav a snap-in
    ... The word you want is console. ... "Snap-in Failed to Initialize" Error Message When You Open Microsoft ... When you try to start Microsoft Management Console with a snap-in on a ... MMC may not start and you may receive ...
    (microsoft.public.windowsxp.general)

Quantcast