ePolicy Orchestrator 5.10.0 Update 2 Fails to Connect to SQL Server

[csavage]

While attempting to apply ePolicy Orchestrator 5.10.0 Update 2, the process is stopped at the point of connecting the the ePO database on SQL Server 2012. "Failed to connect to database" is the result.

The credentials and port have been checked and tested and verified as correct.

At the SQL Server, I see a pair of events for each of these attempts. They are...

Date: 12/11/2018 5:02:13 PM
Log: SQL Server (Current - 12/11/2018 4:54:00 PM)
Source: Logon
Message: Error: 17828, Severity: 20, State: 3.

Date: 12/11/2018 5:02:13 PM
Log: SQL Server (Current - 12/11/2018 4:54:00 PM)
Source: Logon
Message: The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 192.168.xx.xx]

"prelogin packet used to open the connection is structurally invalid" Is there some fix for this?

[cdinet]

In core/config for epo, what is the ssl setting set to - require or try ssl?  Go through the checks in KB81737.

[csavage · Accepted solution]

Thank you for the suggestion regarding KB81737.  ePO was connecting to the SQL Server database okay.  It was only the ePO Updater that would not.  So the situation covered in KB81737 is somewhat similar but not the same.  

I have, since I posted this, handled the matter and have applied Update 2 for ePO 5.10 okay.  The way that I fixed things so that the ePO Updater would run successfully was as follows:  

The SQL Server that hosts the ePO databases is set to Force Encryption in its SQL Server network protocol properties.  I changed this setting from Yes to No, restarted the SQL Server service, then ran the ePO Updater Tool successfully.  When all ePO update procedures were complete, back at the SQL Server, I changed the Force Encryption setting in SQL Server network protocol properties from No back to Yes.  

ePO 5.10.0 Update 2 is running okay with the same, enforced, encrypted SQL Server connections that it was using before the update.  

Apparently, it is just the ePO Updater tool that has a problem with SQL Server enforced encryption.

- Charlie

[cdinet]

I gave the KB because it referenced force encryption setting also for something to check.  Glad you got it working!

[bleeder]

I am having the same problem but do not have the luxury of changing the SQL server to not force encryption due to security requirements

[cdinet]

You might need to follow KB84628