During the install of agents onto an Exchange2003 cluster homed on Windows 2003, the agent would not install on the passive node for the cluster. An attempt was made to install the Shared Components, which failed, and the EMWMigration.log file contained the following messages:
2/9/2010 5:39:28 PM aeEMWGUIShared::WMICmdRunner::RunCommandLine2 Start execution command line on server_name: C:\WINDOWS\system32\Aelita Exchange Migration Wizard\Setup\EMWShared.exe /s /a /s /f1C:\WINDOWS\system32\Aelita Exchange Migration Wizard\Setup\setup.iss
2/9/2010 5:41:28 PM aeEMWGUIShared::WMICmdRunner::RunCommandLine2 Error: -2147217389 - Provider load failure
2/9/2010 5:41:28 PM aeEMWGUIShared::WMICmdRunner::RaiseOnComplete Process completed. Exit status: -1
2/9/2010 5:41:28 PM aeEMWGUIWizards::CInstaller::m_runner_OnComplete Error: (Unsuccess process exit code: -1)
2/9/2010 5:41:28 PM aeEMWGUIWizards::CAgentInstaller::m_internalInstaller_OnComplete Error: (Install completed unsuccessfully. Agent: Shared Components Server: server_name)
The share and agent files were removed from the passive node manually. Tried to install the Transmission Agent to the cluster and got a pop-up error box containing themessage:
sever_name Error: -2147217389 Description: Automation error
The EMWMigration.log file contained the following messages:
2/10/2010 10:46:12 AM aeEMWGUIShared::CmodMisc::ProcessingLogMessageError: (Computer: STSESMAILCN3 | Error: 2310 | Description: This shared resource does not exist. Cannot get share QMMEXNode$ information (System \\server_name, NetShareGetInfo, level 2). | Severity: 0 | Source: )
2/10/2010 10:46:12 AM aeEMWGUIShared::modMain::GetWMIComputerSystemTypeExecute query: SELECT SystemType FROM Win32_ComputerSystem WHERE Name=server_name
2/10/2010 10:46:12 AM EMWCon::WMIHelper::WMI_ConnectServerConnect using WMI. Server: server_name. Namespace: root\CIMV2.
Windows Management Instrumentation (WMI) failure.
Restart the WMI service on the server identified in the EMWMigration.log file. If this fails to clear up the error, the reboot the server (node) that was identified.
WMI stands for Windows Management Instrumentation. For more information on what WMI is and Frequently Asked Questions (FAQs), please refer to the following Microsoft article titled Secrets of Windows Management Instrumentation | Troubleshooting and Tips at the following link:
The following WMItroubleshooting toolsare normallyutilized:
Go to Start - Run - and type wmimgmt.msc
When the console opens use the right mouse menu - Connect to another computer - Another computer - and type the name of the server.
After it connects use the right mouse menu again and select Properties, it should display the properties without any errors.
Go to Start - Run - and type Wbemtest.exe
The wbemtest.exe tool makes a WMI connect and can query the metabase at the same time. For more information on the wbemtest.exe tool, please see the following Microsoft article titled Scripting Eye for the GUI Guy | WBEM What? at the following link:Note: before continuing, please heed the warning at this link: The word Tester in the title of this opening dialog should serve as a warning even to GUI gurus. Wbemtest was not designed for mere mortals or even savvy system admin scripters. It was designed as a tool for testing the functionality of the WMI COM API. The result is that: 1) wbemtest enables you to do almost anything with the WMI COM API and 2) the interface is difficult to use even for experts.