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

Setting up new SGN 6.1.0 server and having connection issues

Hi all,

I am in the process of setting up a new SGN 6.1.0 server to migrate our old Sophos 5.6 Full disk encryption onto.

Following the instructions I have managed to get it installed, imported the company certificate etc.. Registered said server as the SGN server, I have it listed under the server and created an install package off the back of it.

The issue I am having now is that when I go to browse to the website on the server and check connection then invoke I am getting the following error

<?xml <?xml version="1.0" encoding="UTF-8"?>

<s<string xmlns="http://tempuri.org/"><Dataroot><WebService>OK</WebService>< DBAuth>failed</DBAuth>< Error>A database exception occurred.</Error></string>

I have tried uninstalling the Safeguard Server configuration and then re-installing it. Same issue. Gone onto the SQL database and checked that my user has the necessary rights and I do.

Any suggestions would be greatly appreciated.

This thread was automatically locked due to age.

0 MichaelMcLannahan over 7 years ago

Does sound like access rights for the user. Are you trying to use a fresh clean SQL install, or something to do with your old build?
Cancel
Vote Up 0 Vote Down

Cancel
0 _J_R_ over 7 years ago in reply to MichaelMcLannahan

I think half the issue may be that I was following the migrating from 5.6 to SGN 6.1.0. Which, doesn't say to install IIS before you install the safeguard bits.

Having found the SGN 6.1.0 install notes I am now seeing that the IIS (along with all the specific security and diagnostic roles) needed to be installed before I setup the Safeguard element of it.

Fortunately as it is a VM I made a snapshot of it before I started anything to do with Sophos. So I reverted to that and am now installing all the pre-req's first before then going ahead with the Safeguard server/management.

I'll let you know how I get on with that.
Cancel
Vote Up 0 Vote Down

Cancel
0 _J_R_ over 7 years ago in reply to _J_R_

To answer your question it was a new SQL install. And I have hit the same issue as before. Any suggestions?
Cancel
Vote Up 0 Vote Down

Cancel
0 MichaelMcLannahan over 6 years ago in reply to _J_R_

Basic check but one worth doing all the same - firewall?
Cancel
Vote Up 0 Vote Down

Cancel