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

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
  • Hi,

    There are a couple of paths from here to getting it working.

    I'll assume that SOPHOS4 and SOPHOS45 are both ok, I.e. SOPHOS4 contains the previous data from the SEC 4 install and SOPHOS45 has been created correctly by the SEC 4.5.1 installer.

    If you wish to try and keep the data from SOPHOS4 (I'm not sure if you do or not) and move it into SOPHOS45 I would suggest:


    As an administrator, run:

    "%programfiles%\sophos\Enterprise Console\UpgradeDB.exe" -sourceVersion=4 -debug -reset

    I see you ran this before and got an error:

    Error. std::exception thrown SP Erro: 35 (ErrorUnexpected)

    Exit code 5 (Failed to transfer data from old database.)

    But I didn't see the -sourceVersion=4 switch and I think, if I remember rightly it defaults to source version 3 if not told otherwise.  If this completes, it should set the upgrade status in the database to 2 and the management service should then start,

    If you have no interest in trying to save anything from SOPHOS4 and just want to start again with SEC 4.5.1 and the SOPHOS45 database, I would suggest as follows:

    1. Drop or rename the SOPHOS4 database:

    I'll suggest a rename as it's safer, to do so in a command prompt run:

    OSQL -E -S .\SOPHOS -Q "EXEC sp_renamedb 'SOPHOS4', 'SOPHOS4R'"

     To drop/delete the database you could do:

    osql -E -S .\SOPHOS -Q "DROP DATABASE SOPHOS4"

     2. Update the Upgrade status of SOPHOS45 manually.

    To do so:

    OSQL -E -S .\SOPHOS -d SOPHOS45 -Q "update dbo.UPGRADE set UpgradeStatus=2"

    3. Finally, double check that the management service is pointing at the SOPHOS45 database in the right instance:

    To do so check:

    HKLM\Software\Sophos\EE\Management Tools\DatabaseConnectionMS
    or if on 64-bit

    HKLM\Software\wow6432node\Sophos\EE\Management Tools\DatabaseConnectionMS

    It should contain:

    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS45;Data Source=[servername]\SOPHOS;
    where the values to check are:
    Initial Catalog=SOPHOS45 is the name of the SOPHOS45 database
    Data Source=[SERVERNAME]\SOPHOS is the combination of the machine name and the database instance name.
    4. Start the management service.
    To do so, open services.msc, hopefully the service now starts.  If not can you open the application event log and read the latest error from the management service.
    I hope this gets you up and running,
    Regards,
    Jak
    :5431
Reply
  • Hi,

    There are a couple of paths from here to getting it working.

    I'll assume that SOPHOS4 and SOPHOS45 are both ok, I.e. SOPHOS4 contains the previous data from the SEC 4 install and SOPHOS45 has been created correctly by the SEC 4.5.1 installer.

    If you wish to try and keep the data from SOPHOS4 (I'm not sure if you do or not) and move it into SOPHOS45 I would suggest:


    As an administrator, run:

    "%programfiles%\sophos\Enterprise Console\UpgradeDB.exe" -sourceVersion=4 -debug -reset

    I see you ran this before and got an error:

    Error. std::exception thrown SP Erro: 35 (ErrorUnexpected)

    Exit code 5 (Failed to transfer data from old database.)

    But I didn't see the -sourceVersion=4 switch and I think, if I remember rightly it defaults to source version 3 if not told otherwise.  If this completes, it should set the upgrade status in the database to 2 and the management service should then start,

    If you have no interest in trying to save anything from SOPHOS4 and just want to start again with SEC 4.5.1 and the SOPHOS45 database, I would suggest as follows:

    1. Drop or rename the SOPHOS4 database:

    I'll suggest a rename as it's safer, to do so in a command prompt run:

    OSQL -E -S .\SOPHOS -Q "EXEC sp_renamedb 'SOPHOS4', 'SOPHOS4R'"

     To drop/delete the database you could do:

    osql -E -S .\SOPHOS -Q "DROP DATABASE SOPHOS4"

     2. Update the Upgrade status of SOPHOS45 manually.

    To do so:

    OSQL -E -S .\SOPHOS -d SOPHOS45 -Q "update dbo.UPGRADE set UpgradeStatus=2"

    3. Finally, double check that the management service is pointing at the SOPHOS45 database in the right instance:

    To do so check:

    HKLM\Software\Sophos\EE\Management Tools\DatabaseConnectionMS
    or if on 64-bit

    HKLM\Software\wow6432node\Sophos\EE\Management Tools\DatabaseConnectionMS

    It should contain:

    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS45;Data Source=[servername]\SOPHOS;
    where the values to check are:
    Initial Catalog=SOPHOS45 is the name of the SOPHOS45 database
    Data Source=[SERVERNAME]\SOPHOS is the combination of the machine name and the database instance name.
    4. Start the management service.
    To do so, open services.msc, hopefully the service now starts.  If not can you open the application event log and read the latest error from the management service.
    I hope this gets you up and running,
    Regards,
    Jak
    :5431
Children
No Data