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

Transfer SophosDB to remote server

Hi,

Need advice to transfer my sophosDB in a central console to remote server. 

Running SEC 4.7 

updrage to SEC 5.1 

what is the steps to do this? 

Regards,

tedz

:28377


This thread was automatically locked due to age.
Parents
  • Hi,

    That all looks good on the SQL side, if the "RSA\SophosManagment" account can call that Stored Procedure without error

    So the error at the SEC server in the Windows application event log when you try and start the Sophos management service is still:

    [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

    More than likely you get this if the management server just can't see the SQL instance. because either:

    • It can't resolve the address in the connection string, in this case SQLSERVER
    • A firewall is on the SQL Server blocking access to the SQL port
    • SQL Server is not confgiured to listen on TCP/IP.

    Your connection string that the management service is using is in (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\EE\Management Tools\DatabaseConnectionMS)

    and should be:

    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS47;Data Source=Sqlserver\SOPHOS;

    for this setup and is what you reported.  So that seems ok.

    If you create a text file on the management server called: "TestSophos.UDL" with the contents:

    [oledb]
    ; Everything after this line is an OLE DB initstring
    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS47;Data Source=Sqlserver\SOPHOS;

    Run it, then click "Test connection" it succeeds, so this tests the connection string is ok, meaning the address is resolvable from the management service and that the SOPHOS47 database can be accessed.

    Also just check that the keys under:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\EE\Management Tools\DatabaseUser\

    reflect the correct user:

    DatabaseUserDomain  = RSA

    DatabaseUserName     = SophosManagment

    As you have SQLCMD.exe on the management server (from the local SQL instance), you should also be able to run:

    sqlcmd -E -S SQLSERVER\sophos -d SOPHOS47 -Q "exec dbo.SDDMBootstrapDataGet"

    either as rsa\SophosManement or just as your account, both test the SQL instance is accesible from the management server but running the command in a command prompt running rsa\SophosManagement is a closer simulation to what the management service is doing.

    If that succeeds I'm a bit flummoxed and befuddled

    Regards,

    Jak

    :29051
Reply
  • Hi,

    That all looks good on the SQL side, if the "RSA\SophosManagment" account can call that Stored Procedure without error

    So the error at the SEC server in the Windows application event log when you try and start the Sophos management service is still:

    [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

    More than likely you get this if the management server just can't see the SQL instance. because either:

    • It can't resolve the address in the connection string, in this case SQLSERVER
    • A firewall is on the SQL Server blocking access to the SQL port
    • SQL Server is not confgiured to listen on TCP/IP.

    Your connection string that the management service is using is in (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\EE\Management Tools\DatabaseConnectionMS)

    and should be:

    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS47;Data Source=Sqlserver\SOPHOS;

    for this setup and is what you reported.  So that seems ok.

    If you create a text file on the management server called: "TestSophos.UDL" with the contents:

    [oledb]
    ; Everything after this line is an OLE DB initstring
    Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS47;Data Source=Sqlserver\SOPHOS;

    Run it, then click "Test connection" it succeeds, so this tests the connection string is ok, meaning the address is resolvable from the management service and that the SOPHOS47 database can be accessed.

    Also just check that the keys under:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\EE\Management Tools\DatabaseUser\

    reflect the correct user:

    DatabaseUserDomain  = RSA

    DatabaseUserName     = SophosManagment

    As you have SQLCMD.exe on the management server (from the local SQL instance), you should also be able to run:

    sqlcmd -E -S SQLSERVER\sophos -d SOPHOS47 -Q "exec dbo.SDDMBootstrapDataGet"

    either as rsa\SophosManement or just as your account, both test the SQL instance is accesible from the management server but running the command in a command prompt running rsa\SophosManagement is a closer simulation to what the management service is doing.

    If that succeeds I'm a bit flummoxed and befuddled

    Regards,

    Jak

    :29051
Children
No Data