Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 8801 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

Database server connection screen when installing Sophos management console

MichaelLattuca

Attachments added at the bottom: After selecting the server and choosing to utilize NT credentials  for log in  I get the following error :

-----------------------------

Connection to database could not be established. Please

check if the logon credentials are valid.

Additional Information:

A connection was successfully established with the server, but

then an error occurred during the login process. (provider: SSL

Provider, error: 0 - The message received was unexpected or badly formatted.)

--------------------------------------------------------

2nd error when trying to run custom install of PW SD

Failed  to process the configuration file.

--------------------------------------

I had to install the management console for a few people who are now officers, but this one is giving me trouble. I cant make sense of this error. The person is properly added in the correct group in Active directory, they have rights to the server we use, and we have taken away and readded the user as an officer.



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember
    Hi Michael,

    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).

    If the above fails double-check that the user credentials are valid and user has sufficient rights to acess the database.

    Open: Start > All Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager and then SQL Server Network Configuration > Protocols for SQLEXPRESS and make sure that Named Pipes are set to Enabled.

    Restart the SQL server and test again.

    Any problems Michael just let me know.
Reply
  • FormerMember
    0 FormerMember
    Hi Michael,

    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).

    If the above fails double-check that the user credentials are valid and user has sufficient rights to acess the database.

    Open: Start > All Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager and then SQL Server Network Configuration > Protocols for SQLEXPRESS and make sure that Named Pipes are set to Enabled.

    Restart the SQL server and test again.

    Any problems Michael just let me know.
Children
No Data
Unfiltered HTML