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.
  • Hello DAMLA,

    is the management service running and can you restart it or does it fail to start?

    I'd suggest this article instead of 16195. To give you some specific help we need a little bit more information about your setup. Is this a fresh install or did you upgrade? Is the database (which version) on the same server? Are you in a domain environment? Is your management server also a DC? Has the user sufficient rights for the database?

    Christian

    :5317
  • Hello DAMLA

    Some other questions :

    1) Was this an upgrade?

    If so did accounts get locked out, any events in the application event logs

    2) Is the database on the same server?

    If so go to the console server in the registry HKLM\software\sophos\EE\Management tools\DataBase User\ 

    Here you will see 4 entries if the database is on the same server as the console the entries should be blank.

    If you see information then remove it if the database is local.

    If it is on another server then a domain level accounts information should be present so enter the correct information as needed.

    3) If this fails then use the sophos site to see how to create a UDL file for database connectivity testing.

    :5331
  • There used to be sophos 4.x version on the server. I have uninstalled that and installed the newer version which is 4.5.1. There wasnt any problem with earlier version.

    When I want to run Sophos Management service it gives me an error 0x80004005: Unspecified error

    and as it was suggested before I have tried this article http://www.sophos.com/support/knowledgebase/article/66028.html

    Is the required database service running?

    Yes

    Does the designated Sophos instance contain a SOPHOSX database?

    It returned those master, tempdb, model, msdb, SOPHOSX.

    Check the upgrade status of the SOPHOSX database.

    It returned the value '0'

    If the returned value is 0 refer to the knowledgebase article http://www.sophos.com/support/knowledgebase/article/65420.html

    I have tried this article and wrote upgradedb.exe -debug

    It returned me..

    08.10.2010 11:27:55      ..succesfully completed.

    08.10.2010  11:27:55    Validating parameter values...

    08.10.2010  11:27:55    succesfully completed..

    ......................................     transferring data to the new databases.

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

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

    Some additional notes:

    Database should be on the same server and the user should have sufficient rights. I am not a PC guru so I am not sure how to check them too.

    Thank you for your help. Looking forward to hearing you more. Have a lovely day.

    :5334
  • 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
  • I ran this command OSQL -E -S .\SOPHOS -Q "SELECT Name FROM SYSDATABASES" 

    returns me.

    master

    tempdb

    model

    msdb

    SOPHOS45

    SOPHOS4

    (6 rows affected)

    HKLM\Software\Sophos\EE\Management Tools\Database Installer\Instance contains SOPHOS.

    OSQL -E -S .\SOPHOS -d SOPHOS45 -Q "SELECT UpgradeStatus from UPGRADE"

    It returns 0

    OSQL -E -S .\SOPHOS -d SOPHOS4 -Q "SELECT UpgradeStatus from UPGRADE"

    It returns 2

    I am confused and I don’’’’t know what I should do after this point. Thank you for your help.

    I am unfamiliar to these terms so if anyone could help me out about this issue , that would be great. Because it is a school, the children started using the computers without the antivirus software. I need urgent help. Thank you so much

    :5430
  • 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