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

SEC 5.5.2 wont upgrade

Hello!

We tried to upgrade SEC 5.5.0 to 5.5.2. At first attempt we had tu upgrade SQL 2008 wth SP4 that went OK. SEC 5.5.2 upgrade started again, but the in the middle some error stopped upgrade process with server restart request. After restart and SEC 5.5.2 upgrade start again, I receive error: The current credentials do not permit access to SOPHOS552 database and installer stops.

Please advise.

Best regards

This thread was automatically locked due to age.

0 QC over 3 years ago

Hello KingRolo,

this is a local SQL Server 2008 instance?
Please check (under Programs and Features) the versions of the following Sophos components: Credential Store, Management Console, Management Database, and Management Server. Also post the latest Sophos_bootstrapper log (it contains servername and installing user so you might want to anonymise them).

Christian,

.
Cancel
Vote Up 0 Vote Down

Cancel
0 KingRolo over 3 years ago in reply to QC

Yes its local instance upgraded to 2017.

Oh and yes I forgot to mentioned that after unsuccessful attempt I uninstalled Management Database because it was on version 5.5.2 while the rest of two were on 5.5.0. If I try to install Database Management component from 5.5.0 its the same issue with credentials.

There is an error: Failed to create impersonation token for: XXXXXX\sophos.db 6 - the handle is invalid.

BR
Cancel
Vote Up 0 Vote Down

Cancel
0 KingRolo over 3 years ago in reply to KingRolo

Christian, I found this one: https://community.sophos.com/on-premise-endpoint/f/sophos-enterprise-console/121406/sophos-upgrade-from-5-5-0-to-5-5-2/442576

I checked their case and my and same errors can be found in my log
Cancel
Vote Up 0 Vote Down

Cancel
0 QC over 3 years ago in reply to KingRolo

Hello KingRolo,

would have referred you to the same thread but had to think about what the problem is and why these steps are necessary (didn't do it then, TL;DT). You've probably already figured out that the presence of the SOPHOS552 database triggers a workflow that makes certain assumptions thus dropping the database is necessary.

Christian.
Cancel
Vote Up 0 Vote Down

Cancel