Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 6420 views
  • Users 0 members are here
Options
Suggested
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

Problem upgrading databases from 5.2.2 to 5.4.0

Remabec

Hello,

I read the documentation about upgrading the Enterprise Console from version 5.2.2 to version 5.4.0 but can't seem to make it work.

The databases are stocked on a remote SQL server, I read that I have to upgrade it first.

I did a backup of the 4 DBs :

- SOPHOS521

- SOPHOSENC52

- SOPHOSPATCH52

- SophosSecurity

I tried this for upgrading the DBs :

  1. Run the console installer (Setup.exe) on the remote SQL server and choose the database component.  If you are performing an upgrade the installer will detect the existing components and perform an upgrade of them (you cannot remove components during an upgrade - use Add/Remove Programs if required)

But when I try this with the installer on the remote SQL server with database component only I get the message saying that there is already a DB named SOPHOSENC52 in the instance and to remove all DB of Sophos Enterprise Console before continuing.

Do I have to remove only this BD to make it work? Because it says that the installer will detect the existing components and perform upgrade..

I've found and tried this too, didn't work and the is no clues of issues in the log file when it fails :

https://www.sophos.com/en-us/support/knowledgebase/116768.aspx

Please help.

Thank you!

Richard N.



This thread was automatically locked due to age.
Parents
  • 0

    Hello Richard N.,

    does it actually say to remove all DB? If so, is the Sophos Management Database listed under Programs and Features? If not, the databases have likely been installed manually, i.e. by running the scripts instead of the installer/setup.exe. Simply follow appropriate section in the article (from 5.2.2 to 5.4.0 it'd be running InstallDB.bat, UpdatePatchDB.bat, and UpdateSophosSecurity.bat.
    I've found and tried this - the scripts above? Or are you referring to setup.exe (which wouldn't get as far as running the scripts)? 

    BTW - you might have to remove the Encryption feature on the management server. and

    Christian

  • 0 in reply to QC

    Hello Christian,

    Thank you for the quick response and support as always.

    Good for the Encryption feature, I will note that when the databases will be updated and I will be good to go to upgrade the Enterprise Console.

    Indeed I verified and there was no Sophos Management Database listed under the Programs and Features so I guess you're right that the person who installed it must have been installed it manually with the scripts like you said.

    I copied all the folder sec_540 on the remote SQL server to be sure and tried the script InstallDB.bat [server name]\[SQL instance name] [NetBiosDomainName] SOPHOS540 Sophos_InstallCore540DB.log

    But unfortunatly it fails and the only thing I get in the log is this :

    InstallDB.bat [Server Name]\[SQL Instance Name] [NetBios DomainN ame] SOPHOS540 Sophos_InstallCore540DB.log

    Started

    30/06/2016

    09:28

    ==============

    I validated the informations that I entered and everything seems ok, on the server name section I tried (local) as the name too and didn't work.As far I'm stuck at that part I didn't try the other scripts yet is there something I'm missing to make it work?

    Thank you!

  • 0 in reply to Remabec

    Hello Richard,

    InstallDBEx.bat (the "actual" script) does not redirect STDERR to the log so you won't get an output in case of syntax errors. Nevertheless it jumps to the :Error label and outputs the Failed message. sqlcmd should exist on the server but as a quick test just type sqlcmd -? at the command prompt. If it talks to you the next command to try would be sqlcmd -E -S [Server Name]\[SQL Instance Name] -Q "SELECT name from sys.databases".

    Christian

Reply
  • 0 in reply to Remabec

    Hello Richard,

    InstallDBEx.bat (the "actual" script) does not redirect STDERR to the log so you won't get an output in case of syntax errors. Nevertheless it jumps to the :Error label and outputs the Failed message. sqlcmd should exist on the server but as a quick test just type sqlcmd -? at the command prompt. If it talks to you the next command to try would be sqlcmd -E -S [Server Name]\[SQL Instance Name] -Q "SELECT name from sys.databases".

    Christian

Children
No Data
Unfiltered HTML