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

Safeguard Enterpise 7 auf 8 upgrade <DBAuth>failed</DBAuth> <Error>Datenbank-Ausnahme aufgetreten.</Error>

Hallo zusammen,

ich habe nach der Administrationshilfe

https://docs.sophos.com/esg/sgn/8-0/admin/win/de-de/webhelp/index.htm#concepts/UpdateSGNAbout.htm

Microsoft .Netframework 4.5.2 installiert, dann den Safeguard Server von 7 auf 8 upgedatet. Danach das Management Center.

Nach dem ersten Login am Management Center musste die Verbindung zur Datenbank hergestellt werden.

Dabei wird NT Authentisierung verwendet mit SSL, was allerdings erst geklappt, nachdem ich den FQDN des SQL Express Servers angeben habe.

Clients können jedoch nicht mit dem Server synchronisieren und beim INVOKE Test kommt folgende Fehlermeldung:

<?xml version="1.0" encoding="utf-8" ?>
<string xmlns="tempuri.org/.../WebService> <DBAuth>failed</DBAuth> <Error>Datenbank-Ausnahme aufgetreten.</Error></string>

Die einzige Änderung, die ich bisher vorgenommen habe, ist im ISS bei den Anwendungspools, den DefaultAppPool die "Identität" auf den Windows NT Nutzer gestellt.

Fehlermeldung beim INVOKE Test kommt immer noch.

This thread was automatically locked due to age.

Parents

0 Reinhard Schwarz over 7 years ago

IIS, sorry.
Cancel
Vote Up 0 Vote Down

Cancel
0 MichaelMcLannahan over 7 years ago in reply to Reinhard Schwarz

Hallo - Hast du die Firewall auf dem server deaktiviert oder modifiziert?

Entschuldigungen - benutzt Google übersetzen wahrscheinlich schrecklich Deutsch!
Cancel
Vote Up 0 Vote Down

Cancel
0 Reinhard Schwarz over 7 years ago in reply to MichaelMcLannahan

Problem solved!

I removed the old SafeGuard Server Configuration.

Made a new config.msi with this step by step help.

community.sophos.com/.../iis-error-after-moving-database-to-another-sql-server-certificate-not-found

It worked for me!

Thank you!
Cancel
Vote Up 0 Vote Down

Cancel
0 MichaelMcLannahan over 7 years ago in reply to Reinhard Schwarz

Excellent news! Sorry I had assumed this was a new installation and not an existing one.

Every time I make a change to the server setup it is worth remembering you'll need to create a new configuration MSI for the servers.

I upgraded the WebHelpDesk and spent many hours wasted and couldn't get it to work - same sort of error you received. I then realised I was running an old server configuration...updated it and it sprang into life!

Well done for figuring it out - e-beer time!
Cancel
Vote Up 0 Vote Down

Cancel
0 Reinhard Schwarz over 7 years ago in reply to MichaelMcLannahan

It was an existing installation, i just upgraded from version 7 to 8. So a new server config was needed!

I didnt install the WebHelpDesk, what is it for? Do I need it?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Reinhard Schwarz over 7 years ago in reply to MichaelMcLannahan

It was an existing installation, i just upgraded from version 7 to 8. So a new server config was needed!

I didnt install the WebHelpDesk, what is it for? Do I need it?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 MichaelMcLannahan over 7 years ago in reply to Reinhard Schwarz

Ah ha - Yes new configuration needed for each server.

WebHelpDesk is an IIS portal so that you can allow your colleagues to recover keys without giving them access to the console.

It gives them a nice easy to use webpage which they can log into using their Windows or local credentials. They then follow a simple wizard to get the recovery key for a particular device.

It's VERY useful if you'd like to limit who uses the console and can help keep that server more secure as you could (as I have) installed the WebHelpDesk on another server.

You don't NEED it but depends on how you want your company to be set up for this.

It looks like this (it's a bit basic but does work well and it's a lot easier for my colleagues to use than remoting into a server, launching console etc...
Cancel
Vote Up 0 Vote Down

Cancel