Upgrade from 5.5.1 to 5.5.2 fails

Hi folks,

today i've tried updating Enterprise Console from 5.5.1 to 5.5.2.

 

At first i've upgraded the databases on our cluster, with no errors.

 

After that i've started the SEC-Setup an it fails when trying to install server64.msi. MSI-Log tells the following error:

Action ended 14:45:09: FormatInteger. Return value 1.
MSI (s) (BC:B4) [14:45:09:101]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2429.tmp, Entrypoint: DeobfuscatePassword
Action start 14:45:09: DeobfuscatePassword.
DeobfuscatePassword:  Initialized.
DeobfuscatePassword:  Deobfuscating: REGISTRYSERVERPASSWORD to SERVER_USERNAMEPASSWORD
DeobfuscatePassword:  Deobfuscation skipped: REGISTRYSUMPASSWORD to SUM_USERNAMEPASSWORD
MSI (s) (BC:00) [14:45:09:148]: Doing action: SetServerUserNamePasswordFromCommandLineValue
Action ended 14:45:09: DeobfuscatePassword. Return value 1.
Action start 14:45:09: SetServerUserNamePasswordFromCommandLineValue.
MSI (s) (BC:00) [14:45:09:148]: Doing action: SetServerUserNameDomainFromCommandLineValue
Action ended 14:45:09: SetServerUserNamePasswordFromCommandLineValue. Return value 1.
Action start 14:45:09: SetServerUserNameDomainFromCommandLineValue.
MSI (s) (BC:00) [14:45:09:148]: Doing action: SetServerUserNameFromCommandLineValue
Action ended 14:45:09: SetServerUserNameDomainFromCommandLineValue. Return value 1.
Action start 14:45:09: SetServerUserNameFromCommandLineValue.
MSI (s) (BC:00) [14:45:09:148]: Skipping action: CredStore.GetDBCredentials (condition is false)
MSI (s) (BC:00) [14:45:09:148]: Skipping action: SetSUMUserNamePasswordFromCommandLineValue (condition is false)
MSI (s) (BC:00) [14:45:09:148]: Skipping action: SetSUMUserNameFromCommandLineValue (condition is false)
MSI (s) (BC:00) [14:45:09:148]: Doing action: CredStore.GetSUMCredentials
Action ended 14:45:09: SetServerUserNameFromCommandLineValue. Return value 1.
MSI (s) (BC:00) [14:45:09:163]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2459.tmp, Entrypoint: GetSumCredentialsFromCredStore
Action start 14:45:09: CredStore.GetSUMCredentials.
GetSumCredentialsFromCredStore:  Initialized.
GetSumCredentialsFromCredStore:  GetUsername operation results: 80131577
GetSumCredentialsFromCredStore:  Error 0x80131577: Failed to get username
CustomAction CredStore.GetSUMCredentials returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 14:45:09: CredStore.GetSUMCredentials. Return value 3.
Action ended 14:45:09: INSTALL. Return value 3.

 

Anyone else facing the same problem or has any clue to solve this issue?

 

Best regards,

 

R. Gorek

  • In reply to QC:

    Yes 551 und console  is still working.

    I got a reply from the support: they asked me, if the sum updatemanager password includes special characters. The only special charakter ,which is included in the password, is the underscore charakter "_"

  • In reply to Eren777:

    Hello Eren777,

    fine, no need to take action.

    What's special and what not ... wouldn't say that an underscore is special (wonder what "special" character Gorek uses). This would be somewhat dissatisfying, it's not that the password just sat there all the time just waiting for the deobfuscation to fail with the 5.5.2 upgrade. Changing the SUM password to test the "special character" theory might not be such a doddle - you'll have to amend the updating policies. As an aside - it looks like passwords will be taken out from the updating policy editor, you specify a username but its password is managed centrally so no need to amend umpteen policies. Just a guess.

    Christian

  • In reply to QC:

    Hi,

     

    we do have special characters in our password. For testing purpose i've changed it to one with no special characters, but still the same issue.

     

    Best regards,

     

    Robby Gorek

  • In reply to Gorek:

    Hi,

    i had the same problem. I tried a few times, at last step-by-step (thx for the snapshots ;-)

    My solution at this time: during installation of SEC 5.5.2 watch the services by services.msc in a second windows. Refresh the view by F5 all the time.

    In that moment the "Sophos Credential Store" service is beeing created open the properties of the service and change the "log on as" credentials to "local system".

    You have to do it quickly, before the installation process generates the error.

    At my systems it works. Now all components are on 5.5.2.

     

    Good luck!

    Marco

     

     

     

     

  • In reply to Marco Dressler:

    Hi Marco,

    Do you have Local Security Policy > Local Policies > User Rights Assignment > Log on as a service configured by Group Policy?  It might be the newly created SophosCSMSA$ account doesn't have this permission on your SEC server.

  • In reply to MEric:

    Hello,

    no, I didn't.

    At the moment it works with "local system", such as the most other services.

    It's not fine that there was no way to change the service account during the setup process and nothing to find about the account created by sophos in the manual.

    Our GPOs are managed by the domain, so changing the local policies would only help until they are updated.

    Regards,

     

    Marco

  • In reply to Marco Dressler:

    Hello Marco,

    You have to do it quickly
    a SEC install or upgrade is not Prince of Persia. There should be no need for auxiliary monitoring with rapid key-pressing and meticulously timed clicks. Did you get the GetSumCredentialsFromCredStore: No Sophos Credential Store Service found: 80070005 error in the Server64msi log? As far as I can see this CustomAction is only called when the deobfuscation fails (DeobfuscatePassword:  Deobfuscation skipped:) in which case assuring that the service runs wouldn't help as it had not yet stored the credentials at this point. Rather, I think, you got the error near the end where SaveToCredentialStore is called.

    The Sophos.Credential.Store.Service uses a Virtual Service Account (VSAs are not a new concept) NT Service\Sophos.Credential.Store.Service. Normally the Log on as a service right is assigned (amongst others) to NT SERVICE\ALL SERVICES. As MEric has suggested your group policy might not assign this right.

    Christian 

  • In reply to Gorek:

    Hello Robby and Eren777,

    has the issue been resolved? Could you upgrade?

    Christian

  • In reply to QC:

    Hi Christian,

     

    not yet. My issue has been escalated to the development team. I am still waiting for a response .

  • In reply to QC:

    Hi Christian,

     

    we got the same situation issue is escalated to the developement team and still waiting for a reply.

     

    Robby

  • In reply to Gorek:

    Finally got an answer from Sophos Support.

     

    Theres an KB article https://sophos.com/kb/114627 which solved the issue.

     

    SEC is now on 5.5.2 and seems to work properly.

     

    Thanks for the help.

  • In reply to Marco Dressler:

    I also tried all the suggestions in this thread as well as watching Sophos support spend hours on my server trying to get this installed.  The end following this tip of changing the log on to local as it was being installed was the only thing that worked for me.

     

    Thanks!