Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 5864 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

Management server connection failed

DAMLA

Hi everyone,

I am trying to run sophos enterprise console 4.5.1 on windows server enterprise 2008 service pack 1.

And I am receiving this error

Could not connect to the Management server. 

Management server connection failed 

This may be due to one of the following: 
Local network problems 
Management service has stopped on the server  

Your database server has stopped

A firewall is blocking the connection.

I have tried the solution which was provided by sophos

http://www.sophos.com/support/knowledgebase/article/16195.html

However, the problem still continues to occur. Can anyone share some ideas about this issue? 

Regards

:5313


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

    HI,

    When you list the databases in the instance you list only one SOPHOS database, if this is an upgrade It should work as follows:

    For an upgrade scenario from SEC4 to SEC45, you should start with just a SOPHOS4 database in the SQL instance as used by SEC4.  You then install SEC45, this creates a empty SOPHOS45 database in the same instance. Later on the during the install upgradedb.exe, attempts to move the data from SOPHOS4 to SOPHOS45 and then sets the upgrade status to a 2 in the table upgrade of the SOPHOS45 database when complete.

    Is the database in the SQL instance SOPHOS4 or SOPHOS45 at this stage, that wasn't clear to me?

    If it's just SOPHOS45, then you have nothing to migrate data from and in this case you're starting again,  You can therefore set the upgrade value in the upgrade table to a 2 and the management service should start.

    If you just have a SOPHOS4 database, this suggests you need to create a SOPHOS45 database first.  To do so you can run InstallDB.bat, please run installDB.bat /? to see the required switches.  Once you have a SOPHOS4 and SOPHOS45 database side by side, you should then be able to run upgradedb -sourceVersion=4, once this has moved the data from SOPHOS4 to SOPHOS45 it should then set the upgrade status to 2 and the management service will be able to start.

    If not the application event log will give the reason why it can't.

    I hope this is helpful.

    Thanks,

    Jak

    :5335
Reply
  • 0

    HI,

    When you list the databases in the instance you list only one SOPHOS database, if this is an upgrade It should work as follows:

    For an upgrade scenario from SEC4 to SEC45, you should start with just a SOPHOS4 database in the SQL instance as used by SEC4.  You then install SEC45, this creates a empty SOPHOS45 database in the same instance. Later on the during the install upgradedb.exe, attempts to move the data from SOPHOS4 to SOPHOS45 and then sets the upgrade status to a 2 in the table upgrade of the SOPHOS45 database when complete.

    Is the database in the SQL instance SOPHOS4 or SOPHOS45 at this stage, that wasn't clear to me?

    If it's just SOPHOS45, then you have nothing to migrate data from and in this case you're starting again,  You can therefore set the upgrade value in the upgrade table to a 2 and the management service should start.

    If you just have a SOPHOS4 database, this suggests you need to create a SOPHOS45 database first.  To do so you can run InstallDB.bat, please run installDB.bat /? to see the required switches.  Once you have a SOPHOS4 and SOPHOS45 database side by side, you should then be able to run upgradedb -sourceVersion=4, once this has moved the data from SOPHOS4 to SOPHOS45 it should then set the upgrade status to 2 and the management service will be able to start.

    If not the application event log will give the reason why it can't.

    I hope this is helpful.

    Thanks,

    Jak

    :5335
Children
No Data