XenMobile Mail Manager Setup Wizard ended prematurely – XMM v10.2.1.103

There are no logs under XMM logs, the only thing you see is the error below:

XenMobile Mail Manager Setup Wizard ended prematurely

By default, Windows does not log Windows Installer errors, so you have to manually enable Windows Installer logging by following this article by Microsoft:

https://support.microsoft.com/en-us/help/223300/how-to-enable-windows-installer-logging

This will create a log file under the Windows TEMP directory.

If you see the logs, you will find the following:

MSI (c) (0C:04) [15:18:33:187]: Doing action: CustomAction_PrepForUpgradeMSI (c) (0C:04) [15:18:33:187]: Note: 1: 2205 2: 3: ActionText Action 15:18:33: CustomAction_PrepForUpgrade. Action start 15:18:33: CustomAction_PrepForUpgrade.MSI (c) (0C:04) [15:18:33:339]: Creating MSIHANDLE (1) of type 790542 for thread 2308MSI (c) (0C:AC) [15:18:33:341]: Invoking remote custom action. DLL: C:UsersTERMXM~1AppDataLocalTemp2MSI4466.tmp, Entrypoint: PrepForUpgradeMSI (c) (0C:60) [15:18:33:343]: Cloaking enabled.MSI (c) (0C:60) [15:18:33:343]: Attempting to enable all disabled privileges before calling Install on ServerMSI (c) (0C:60) [15:18:33:343]: Connected to service for CA interface.MSI (c) (0C!F4) [15:18:33:420]: Creating MSIHANDLE (2) of type 790531 for thread 3572SFXCA: Extracting custom action to temporary directory: C:UsersTERMXM~1AppDataLocalTemp2MSI4466.tmp-MSI (c) (0C!F4) [15:18:33:421]: Closing MSIHANDLE (2) of type 790531 for thread 3572MSI (c) (0C!F4) [15:18:33:544]: Creating MSIHANDLE (3) of type 790531 for thread 3572SFXCA: Binding to CLR version v4.0.30319MSI (c) (0C!F4) [15:18:33:545]: Closing MSIHANDLE (3) of type 790531 for thread 3572MSI (c) (0C!F4) [15:18:33:612]: Creating MSIHANDLE (4) of type 790531 for thread 3572Calling custom action InstallerCustomActions!InstallerCustomActions.CustomActions.PrepForUpgradeMSI (c) (0C!F4) [15:18:33:615]: Closing MSIHANDLE (4) of type 790531 for thread 3572MSI (c) (0C!F4) [15:18:33:643]: Creating MSIHANDLE (5) of type 790531 for thread 3572Exception thrown by custom action:MSI (c) (0C!F4) [15:18:33:643]: Closing MSIHANDLE (5) of type 790531 for thread 3572MSI (c) (0C!F4) [15:18:33:647]: Creating MSIHANDLE (6) of type 790531 for thread 3572System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'System.String System.String.Format(System.IFormatProvider, System.String, System.Object)'. at InstallerCustomActions.CustomActions.PrepForUpgrade(Session session) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture) at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr)MSI (c) (0C!F4) [15:18:33:648]: Closing MSIHANDLE (6) of type 790531 for thread 3572CustomAction CustomAction_PrepForUpgrade returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)MSI (c) (0C:AC) [15:18:33:654]: Closing MSIHANDLE (1) of type 790542 for thread 2308Action ended 15:18:33: CustomAction_PrepForUpgrade. Return value 3.MSI (c) (0C:04) [15:18:33:655]: Doing action: FatalErrorMSI (c) (0C:04) [15:18:33:655]: Note: 1: 2205 2: 3: ActionText Action 15:18:33: FatalError. Action start 15:18:33: FatalError.Action 15:18:33: FatalError. Dialog createdMSI (c) (0C:08) [15:18:33:667]: Note: 1: 2731 2: 0 Action ended 15:18:34: FatalError. Return value 2.Action ended 15:18:34: INSTALL. Return value 3.MSI (c) (0C:04) [15:18:34:578]: Destroying RemoteAPI object.MSI (c) (0C:60) [15:18:34:582]: Custom Action Manager thread ending.

This error indicates that .NET Framework is missing or is not at the minimum required version for XMM V10.2.1.103.

Minimum required version of .NET Framework is 4.6

Related:

Leave a Reply