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

Sophos Enterprise Console 5 - Cannot connect to SQL Instance

BrickMan

Kind of getting stumped on this one.

We are installing SEC5 on a clean (up-to-date) Server 2008 R2 machine and trying to connect it to an SQL 2008 R2 server where the SOPHOS database will reside.

We have created a domain user domain\sophosdb and have given it appropriate rights to the SQL server and have mapped it and provided full GRANT rights to the SOPHOS50 instance we have created on this SQL Server.


During the install of SEC5 where I tell it which server\instance to connect to and provide the sophosdb user credentials, it sits there for about 15 seconds and then says the credentials do not have access to the instance. Well, it certainly does !

I've verified a few things, such as entering incorrect credentials, which immediately responds that they are incorrect and do not have rights (which I expected it to do) - so thus when I enter the correct credentials, it takes quite a bit longer so it is getting part of the way there !

We have a lot of other applications that access this SQL server, and we have setup access for SEC5 in the same fashion as we have for everything else, but it refuses to work.


Is there something 'odd' we should be aware of ? Did we miss something 'non-obvious' ?

So to recap, we have ;

Created a SOPHOS50 instance on SQLSERVER.OURDOMAIN.COM
Created SOPHOSDB user within OURDOMAIN.COM
Granted SOPHOSDB user access to SQLSERVER AND the SOPHOS50 instance with FULL rights
Started the SEC5 installer and it will not connect to the instance saying the credentials are wrong.

SQL resolves and pings fine from the SEC5 machine.
Both machines are on the same domain.
All pre-requisites for SEC5 installation have been met.
Definitely no firewall issues anywhere.

:23733


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

    HI,

    You refer to a SOPHOS50 instance, the SQL instance can be called anything but the database within the instance should be named SOPHOS50.  On a distributed install you should:

    1. Create a DB user.

    2. Run the installer on the database computer to create the SOPHOS50 and SOPHOSPATCH databases in the SQL instance.  You just select the database component and choose the account you created, this account will then be added to the "Sophos DB Admins" group created by the installer to grant it database access.   You can use an existing SQL instance or the installer will create you a default SQL Express 2008 SP2 SOPHOS named instance for you.

    Note: if you don't like the idea of running an installer on a SQL server you can manually create the "Sophos DB admins" group and then run the batch files to create the databases as per: http://www.sophos.com/support/knowledgebase/article/116768.html .

    3. Once you have the databases created (SOPHOS50 and SOPHOSPATCH) you run the installer on the management server and choose the management server and optionally the console component.

    Note, when the SEC installer creates the SOPHOS database instance (SQL Express 2008 SP2) in a database only install it enables remote connections to SQL.  You may want to check that the SQL instance your using is configured to allow TCP/IP from the "SQL Server Configuration Manager" tool.  Without this when the setup.exe tries to check the instance for the required databases it will fail as would the management service.

    Regards,

    Jak

    :23743
Reply
  • 0

    HI,

    You refer to a SOPHOS50 instance, the SQL instance can be called anything but the database within the instance should be named SOPHOS50.  On a distributed install you should:

    1. Create a DB user.

    2. Run the installer on the database computer to create the SOPHOS50 and SOPHOSPATCH databases in the SQL instance.  You just select the database component and choose the account you created, this account will then be added to the "Sophos DB Admins" group created by the installer to grant it database access.   You can use an existing SQL instance or the installer will create you a default SQL Express 2008 SP2 SOPHOS named instance for you.

    Note: if you don't like the idea of running an installer on a SQL server you can manually create the "Sophos DB admins" group and then run the batch files to create the databases as per: http://www.sophos.com/support/knowledgebase/article/116768.html .

    3. Once you have the databases created (SOPHOS50 and SOPHOSPATCH) you run the installer on the management server and choose the management server and optionally the console component.

    Note, when the SEC installer creates the SOPHOS database instance (SQL Express 2008 SP2) in a database only install it enables remote connections to SQL.  You may want to check that the SQL instance your using is configured to allow TCP/IP from the "SQL Server Configuration Manager" tool.  Without this when the setup.exe tries to check the instance for the required databases it will fail as would the management service.

    Regards,

    Jak

    :23743
Children
No Data