asked on

Disaster recovery – E2K3 and WMI Problem

OK,
- Server failed and needed to be re-installed
- Server is back up and running with last system state restored, Recovered from crashed disks
- Server was DC with Exchange 2k3 installed.
- Hard disks in the server were being listed by the wrong disk drive letters.
- Boot Partition is C, but due to %#$# the Boot Partition is C but the System partition is D
- I had to change the system partition letter to E so Exchange would re-Install (or so I thought)

Huston, we have a problem.

I get an error when performing the reinstall of Exchange. The error pops up during the Messaging and Collaboration Services section of the installation:
“Setup failed while installing sub-component Base DAV protocol with error code 0x8007042C (please consult installation logs for a detailed description). You may cancel the installation or try the failed step again.”

I have checked the Exchange installation log file and based on that it is WMI that does not want to start. An yes… it fails to start – Error 1068: The dependency service or group failed to start.

Now WMI requires the Event Log service and the RPC service. Although this looks like an Exchange problem, we are still dealing with failures on the server side. Both are running nicely. So then we are left again in the middle of a rock and a hard place.

Please help.
Regards,

amaheshwari

First, verify the number of dependencies attached to the WMI service. This can be viewed by running the following command from Start, Run:

CMD /K SC QC WINMGMT

The output should exactly as given below.

[SC] GetServiceConfig SUCCESS

SERVICE_NAME: winmgmt

TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 0 IGNORE
BINARY_PATH_NAME : C:\WINDOWS\system32\svchost.exe -k netsvcs
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : Windows Management Instrumentation
DEPENDENCIES : RPCSS
SERVICE_START_NAME : LocalSystem

The only dependency is the RPCSS service, and it does run by default whenever you start Windows. If you have any other dependencies listed, then it may be the causing the problem. To remove the additional Dependencies, follow this:

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Before you modify the registry, backup the registry key by exporting the corresponding branch. Also, see here to learn how to perform a complete registry backup.

Click Start, Run and type Regedit.exe
Navigate to the following location
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services\ winmgmt

Double-click DependOnService and set it's Value data to RPCSS
Close Regedit and restart Windows

itcoza

ASKER

WMI is started and is running....

Here is thefailure part of the Exchange Setup log file:

[00:14:47] Entering CAtomDAV::ScAddMetabaseKeys
[00:14:47] Entering CAtomBaseDAV::ScAddMetabaseKeys
[00:14:47] Creating IIS Metabase objects for Base DAV protocol
[00:14:47] Entering ScFixWebSvcRestrictionList
[00:14:47] Entering ScFixWebSvcRestrictionListByDisplayName
[00:14:47] Failed to connect to WMI on the local machine
[00:14:47] ScFixWebSvcRestrictionListByDisplayName (f:\titanium\admin\src\libs\exsetup\exmisc.cxx:3920)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation
[00:14:47] Leaving ScFixWebSvcRestrictionListByDisplayName
[00:14:47] ScFixWebSvcRestrictionList (f:\titanium\admin\src\libs\exsetup\exmisc.cxx:3656)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation
[00:14:47] Leaving ScFixWebSvcRestrictionList
[00:14:47] CAtomBaseDAV::ScAddMetabaseKeys (f:\titanium\admin\src\udog\exsetdata\components\server\a_basedav.cxx:124)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation
[00:14:47] Leaving CAtomBaseDAV::ScAddMetabaseKeys
[00:14:47] CAtomDAV::ScAddMetabaseKeys (f:\titanium\admin\src\udog\exsetdata\components\server\a_dav.cxx:753)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation
[00:14:47] Leaving CAtomDAV::ScAddMetabaseKeys
[00:14:47] CBaseAtom::ScRefreshMetabaseKeys (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:1695)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation
[00:14:47] CBaseAtom::ScReinstall (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:1139)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation
[00:14:47] Service = '' CBaseServiceAtom::ScReinstall (f:\titanium\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:247)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation
[00:14:47] Leaving CBaseServiceAtom(Base DAV protocol)::ScReinstall
[00:14:47] mode = 'Reinstall' (61955) CBaseAtom::ScSetup (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:842)
Error code 0X8004100E (4110): An error occurred during a call to Windows Management Instrumentation

I have to get this server up... and your help will be appreciated...

:-}

amaheshwari

Please refer this:

https://www.experts-exchange.com/questions/20899099/Exchange-2003-Install-Error.html

itcoza

ASKER

No luck.

I get the error as soons is the reinstallation wants to write IIS Metabase Objects. Would that then mean that we have a corrupt Metabase... no.. That can't be, the IISAdmin service is still very fuctional.

We have to find the solution.
M

itcoza

ASKER

Don't know if this is part of the problem, but when I run Netdiag I get this error:

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Passed

Trust relationship test. . . . . . : Failed
[FATAL] Secure channel to domain 'PIGROUP' is broken. [ERROR_ACCESS_DENIED]

==================

itcoza

ASKER

From the other domain controller when I run NetDiag I get:
Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Passed

LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC 'svr-mail.pigroup.co.za'.

Bindings test. . . . . . . . . . . : Passed

itcoza

ASKER

Found the problem, AD wasn't started and the Server could not authenticate the access to the WMI object access.

Resolved the AD problem and the rest is history.

Thanx anyway for the assistance.
:0

amaheshwari

What do you mean by ad not started ? May you please tell me.

Thanks

itcoza

ASKER

The server's ntfrs was not able to replicate the sysvol folder and was preventing the server from acting as a domain controller.

So... AD was and DC functions were dead on this server.

:-)

amaheshwari

Great!!!

ASKER CERTIFIED SOLUTION

GhostMod

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial