Skip to main content

VMware vCenter Site Recovery Manager installation may fail if the Windows firewall services are not registered

 

Symptoms
  • Installing VMware vCenter Site Recovery Manager (SRM) 4.x fails
  • Installing SRM 4.0 fails with these MSI installer verbose log messages:

    MSI (s) (2C:3C) [16:35:34:349]: Executing op: ActionStart(Name=VMRollbackAddSrmFirewallExceptions,,)
    MSI (s) (2C:3C) [16:35:34:349]: Executing op: CustomActionSchedule(Action=VMRollbackAddSrmFirewallExceptions,ActionType=1345,Source=BinaryData,Target=VMRemoveSrmFirewallExceptions,CustomActionData=VMware vCenter Site Recovery Manager;C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\;8095;8096;9007)
    MSI (s) (2C:3C) [16:35:34:349]: Executing op: ActionStart(Name=VMAddSrmFirewallExceptions,Description=Configuring Windows Firewall Exceptions,)
    MSI (s) (2C:3C) [16:35:34:365]: Executing op: CustomActionSchedule(Action=VMAddSrmFirewallExceptions,ActionType=1025,Source=BinaryData,Target=VMAddSrmFirewallExceptions,CustomActionData=VMware vCenter Site Recovery Manager;C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\;8095;8096;9007)
    MSI (s) (2C:1C) [16:35:34:365]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI371.tmp, Entrypoint: VMAddSrmFirewallExceptions
    VMware: Srm::Installation::Utility::GetMsgFromErrorTable: ERROR: MsiGetActiveDatabase() failed. Trying MsiOpenDatabase().
    VMware: Srm::Installation::Utility::GetMsgFromErrorTable: INFORMATION: Error message is Could not open service:
    VMware: Srm::Installation::ServiceHandler::ServiceHandler: ERROR: Could not open service: SharedAccess
    VMware: Srm::Installation::Utility::ConfigureSrmFirewallExceptions: ERROR: VMConfigureSrmFirewallExceptions failed: Could not open service: SharedAccess
    CustomAction VMAddSrmFirewallExceptions returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 16:35:34: InstallFinalize. Return value 3.
  • Installing SRM 4.1 fails with these MSI installer verbose log messages:

    MSI (s) (88:7C) [12:50:57:477]: Executing op: ActionStart(Name=VMRemoveSrmFirewallExceptions,Description=Removing Windows Firewall Exceptions,)
    MSI (s) (88:7C) [12:50:57:509]: Executing op: CustomActionSchedule(Action=VMRemoveSrmFirewallExceptions,ActionType=1089,Source=BinaryData,Target=VMRemoveSrmFirewallExceptions,CustomActionData=VMware vCenter Site Recovery Manager;C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\;8095;8096;9007)
    MSI (s) (88:00) [12:50:57:634]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI1395.tmp, Entrypoint: VMRemoveSrmFirewallExceptions
    VMware: Srm::Installation::Utility::GetMsgFromErrorTable: ERROR: MsiGetActiveDatabase() failed. Trying MsiOpenDatabase().
    VMware: Srm::Installation::Utility::GetMsgFromErrorTable: INFORMATION: Error message is Could not open service:
    VMware: Srm::Installation::ServiceHandler::ServiceHandler: ERROR: Could not open service: MpsSvc
    VMware: Srm::Installation::Utility::ConfigureSrmFirewallExceptions: ERROR: VMConfigureSrmFirewallExceptions failed: Could not open service: MpsSvc
Resolution
Depending on the Windows platform on which SRM is, one of two firewall services (SharedAccess or MpsSvc) may be registered and running on the system. Using Windows Service Control Manager, you can can get the display names and query the status information on these two services.
For example:
C:\>sc getDisplayName SharedAccess
[SC] GetServiceDisplayName SUCCESS
Name = Internet Connection Sharing (ICS)
C:\>sc getDisplayName MpsSvc
[SC] GetServiceDisplayName SUCCESS
Name = Windows Firewall
For SRM to install successfully, these two services must be registered on the system. That is, they must show up in the services list. As long as these services are registered, it does not matter whether they are enabled (running/stopped) or disabled.
To check if these services are registered, you can review the service list or use Windows Service Control Manager.
C:\>sc query MpsSvc
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
In this example, the MpsSvc service has been unregistered.
In the event that all perceived services are running and the installation is still failing, it may be beneficial to run the installation in verbose mode to determine if any other services are marked disabled.
Related Information
To collect verbose SRM installation logs, the installation must be started from the command line. For example:
<VMware-srm-####.exe> /V"/lve C:\SRM-installation-log.txt"
Where <VMware-srm-####.exe> is the SRM installation executable file and C:\SRM-installation-log.txt is the file where the installation logs will be saved

Comments

Post a Comment

Popular posts from this blog

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
Post a Comment
Read more

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...
Post a Comment
Read more

Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5, 6.7 and 7.0

  Purpose This article provides steps to increase the disk space of a specific VMDK for the vCenter Server Appliance 6.5, 6.7 and 7.0. With the introduction of Logical Volume Management (LVM) in vSphere 6.0 and continued support with vSphere 6.5, 6.7 and 7.0, the vCenter Server disks can be dynamically increased. List of VMDKs for a vCenter Server Appliance 6.5 - Size Mount point and Purpose Note : Resizing the root partition (VMDK1 listed in the KB above) is not supported on 6.5. Please see the vSphere 6.5 Release Notes for more information. Resizing root partition has been added to 6.7 and 7.0. List of VMDKs/Partitions for a vCenter Server Appliance 6.7 - Size Mount point and Purpose   List of VMDKs/Partitions for a vCenter Server 7.0 - Size Mount point and Purpose Note : This KB can be used for the situation like SEAT partition full or any other vCenter appliance partition full. ...
Post a Comment
Read more