An error message is displayed after upgrading Microsoft .NET Framework to 4.5, on a machine hosting the SafeGuard Enterprise Management Center:
"The connection to the database could not be established or the database does not contain any Security Officers. Would you like to start the Configuration Wizard?"
When clicking "Yes" and starting the configuration wizard, another error message will be displayed when "Use SSL (recommended)" was enabled:
"Connection to the database could not be established. Please check if logon credentials are valid.
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.)"
First seen in
SafeGuard Management Center / Local Policy Editor 6.00.1
What To Do
When using Secure Socket Layer (SSL) protocol to encrypt the communication between the SafeGuard Enterprise Database and the Microsoft SQL Server, make sure to use the Fully Qualified Domain Name (FQDN) and not the NetBIOS name or IP address of the machine, in the "Database Server" field, when establishing the server connection.
Example: Start the SafeGuard Enterprise Management Center again and click on "Yes" when the assistant asks to start the Configuration Wizard. In the "Connection Settings | Database Server: " field, enter the name of the server using the FQDN (i.e. DatabaseServer.domain.com) instead of the NetBIOS name (i.e. DatabaseServer).