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

HTTP Error 500.21 when trying to test localhost/sgnsrv IIS7.5 SGN 8

I've tried installing Sophos Safe Guard 8.04 for a customer with the help of the following video:
https://www.youtube.com/watch?v=sZDWXM5AtbQ

I've pretty much followed every step but now when I try to test SGN by entering https://localhost/sgnsrv in the browser, I get the following error:

 

I'm suspecting this might be an IIS error, but I'm really not sure. Another thing I've noticed is that the "make this computer an sgn server" button is missing in safeguard management center.
I've tried restarting the server, resetting IIS, but no luck.

Maybe someone has an idea, what could be causing this, because I'm kind of stuck.



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

    thanks! That worked beautifully.

    Although when I try to test the connection now, I get the following error:

    <?xml version="1.0" encoding="UTF-8"?>
          <string xmlns="http://tempuri.org/"><Dataroot><WebService>OK</WebService>< DBAuth>failed</DBAuth>< Error> Missing Server Configuration</Error></string>

     

    I already restarted the IIS and searched for a solution and I suspect that the SGN Server hasn't been configured properly, however I still do not see the "make this computer an SGN server" option. Is there another way of creating the needed packet for this?

    EDIT: Okay so I've added the server under the "server" tab by importing the corresponding certficiate. I can now create the server package and install it. Sadly the dbauth-error still persists.

     

    EDIT number 2:
    So it turns out I must have missed something along the way. I followed the best practices guide here:
    https://www.sophos.com/en-us/medialibrary/PDFs/documentation/sgn_7_bpg_eng_installation_best_practice.pdf

    And now I can successfully connect and I get no more DBAUTH errors. I think it might have had something to do with the SQL-Agent startup type being disabled. Anyway, it seems to be working now and I'll be sure to keep sticking to the best practices guide in the future.

    Thanks for your help!