This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Management Server Installation Failed - MSI terminated unexpectedly

Hi,

I migrated Sophos from a server which had the 4.7 version to the 5.1 on a couple of servers, one for the Database and another one for the Management Server and Management Console.

I had everything working fine at last, which was not easy to do, but there was still an issue with the Management Server.

See, there is the Windows Service "Sophos Management Service" which had the credentials of the SophosDatabase user to start.

The credentials were entered during the setup, and there was no error starting the service nor the Management Console after that.

The thing is, the server reboots everyday at 6 am, and then the service "Sophos Management Service" does not start, because for some reason, he's lost the correct credentials for the SophosDatabase user.

So the Management Console wouldn't start until we'd change the properties of the service with the right password.

I called the Sophos Technical Support, and they advised me to reinstall Sophos, so I did.

But my issue now is that it won't install, I get this error every time I try, no matter the given solution I try: Sophos Management Server Installation Failed - MSI terminated unexpectedly.

The Bootstrapper log ends with this :

20/09/2012 17:09:47, INFO : Start state: Idle
20/09/2012 17:09:47, INFO : Deactivate state: Idle
20/09/2012 17:09:47, INFO : Activate state: Installing
20/09/2012 17:09:47, INFO : Verifying files in folder
20/09/2012 17:09:47, INFO : Target folder verification completed successfully
20/09/2012 17:09:47, INFO : Copied SmAgentAPI.dll from C:\sec_51\ServerInstaller\pre-reqs\SmAgent\SmAgentAPI.dll into C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 11\win32_x86\plugins\auth\secLDAP\SmAgentAPI.dll
20/09/2012 17:09:47, INFO : Verifying files in folder
20/09/2012 17:09:48, INFO : Target folder verification completed successfully
20/09/2012 17:09:48, INFO : About to install Server64.msi
20/09/2012 17:10:26, INFO : Processing INSTALLMESSAGE_ERROR or INSTALLMESSAGE_FATALEXIT message from MSI
20/09/2012 17:10:26, INFO : Deactivate state: Installing
20/09/2012 17:10:26, INFO : Activate state: Failing
20/09/2012 17:10:34, INFO : Installation of Server64.msi failed with error code: 1603
20/09/2012 17:10:34, INFO : Ended installing Server64.msi
20/09/2012 17:10:36, INFO : Installation failed with error code: 1603
20/09/2012 17:10:36, INFO : Deactivate state: Failing
20/09/2012 17:10:36, INFO : Activate state: Failed
20/09/2012 17:10:36, INFO : Entered Installation failed page.
20/09/2012 17:10:39, INFO : Finished Bootstrapper
20/09/2012 17:10:39, INFO : Cleaned up socket.
20/09/2012 17:10:39, INFO : Uninitialized COM in main thread

 And the Server64msi file:

About to call: Initialize
Succeeded: Initialize
Calling API function: CreateMiscClassInstance().
Completed API function: CreateMiscClassInstance().
About to call: Initialize
Succeeded: Initialize
About to call: SetDatabaseConnectionString
Succeeded: SetDatabaseConnectionString
About to call: ResetCertificateStore
Succeeded: ResetCertificateStore
About to call: AddP12ToCertStore
Succeeded: AddP12ToCertStore
About to call: AuthenticateOfficer
MSI (s) (BC!2C) [17:10:26:484]: Product: Sophos Management Server -- 1: Certificat introuvable. 

Exception thrown by custom action:
System.Reflection.TargetInvocationException: Une exception a été levée par la cible d'un appel. ---> EncryptionCustomActions.SgnApiException: Certificat introuvable.
   à EncryptionCustomActions.CustomAction.CallFunction(String functionName, Func`1 function, Session session, Base baseObject)
   à EncryptionCustomActions.CustomAction.AddMsoCertToStoreAndRegisterServer(Session session)
   --- Fin de la trace de la pile d'exception interne ---
   à System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   à System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   à System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   à System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
   à Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr)
CustomAction RegisterServer returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (BC:F8) [17:10:26:516]: User policy value 'DisableRollback' is 0
MSI (s) (BC:F8) [17:10:26:516]: Machine policy value 'DisableRollback' is 0
Action ended 17:10:26: InstallFinalize. Return value 3.

So please if anyone has any idea of what's wrong here, or any advice on how to fix this, please help.

I've already called several times (like 20) the Sophos Technical Support, and I've sent them the error logs 10 days ago, still no answer ...

Sorry for the long post, I wanted you to have all the info ^^

Thanks,

Wii

:31533


This thread was automatically locked due to age.
Parents
  • After the reboot, the Sophos services wouldn't start, so I launched a repair installation, then the only service left was the Sophos Management Service, it just wouldn't start.

    I fixed it by using the UpgradeDB.exe in the command line with the right arguments, and it worked.

    Now I am waiting on a reboot to see if the services will start by themselves or not, in this case, I'll be back to square one, before that whole reinstallation mess ...

    Wii.

    :32183
Reply
  • After the reboot, the Sophos services wouldn't start, so I launched a repair installation, then the only service left was the Sophos Management Service, it just wouldn't start.

    I fixed it by using the UpgradeDB.exe in the command line with the right arguments, and it worked.

    Now I am waiting on a reboot to see if the services will start by themselves or not, in this case, I'll be back to square one, before that whole reinstallation mess ...

    Wii.

    :32183
Children
No Data