SEPM install gives wrong credentials to SQL causing connection to fail

Products

• Endpoint Security Complete

Issue/Introduction

During installation of a new SEPM and setting up database configuration in the Management Server Configuration Wizard or "MSCW", correct SQL credentials are entered to connect to an external SQL server, but you are unable to connect or continue the installation.

This error;

"Error 11501: Unable to connect to the database. Make sure that you have entered the correct database parameters, and that a firewall is not blocking the connection, then try again. Please click here for more information."

is displayed.

Even after validating that all of the information is correct it is still giving the error.

Looking over the SQL server logs we noticed that the incorrect username is being passed to the SQL server. 

The name that was being passed was the username for the user that was currently logged into the Windows server, running the MSCW.  This user does not have access to the SQL server.  MSCW is passing the currently logged in users credentials instead of what is specified in the dialog box for the authentication.

 

Environment

Release : 14.3 RU7

SQL Database Version    13.00.7024

Windows authentication must be used.  Does not happen with SQL authentication.

Cause

SEP Management Server Configuration Wizard is passing incorrect credentials to SQL server, causing authentication failure.

 

Resolution

There is not a current fix for this at this time however there is the following workarounds available.

To workaround this problem, create a domain Administrator that has the same username and password as the SQL credentials required for the database, and login as this user before running the MSCW.  You could also have this user in the domain and run MSCW using SHIFT + Right Click, and Run as Different user and Specify that Administrators credential in the dialog box.

This will now pass the correct credentials to the SQL server, since they are the local logged in users credentials and the authentication will work.

Another workaround would be to change the SQL server authentication to SQL Authentication and not Windows Authentication, this will work since this issue is only present for Windows authentication.