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

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...

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...