Additional Async Server Setup: The product key is not compatible with the installed version of Microsoft Dynamics CRM.

(0) Share

Report

Posted on by JoeO

234

Hi,

We have an on-premise setup of Dynamics CRM version 8.2.3.8. Were trying to add a second back-end Async server. I started the setup from the original 2016 ISO (downloaded from the volume license portal). The Setup failed with two errors:

The product key is not compatible with the installed version of Microsoft Dynamics CRM.
Could not connect to the following SQL Server: 'SQLSeverName'. Verify that the server is up and running and that you have SQL Server administrative credentials. [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error.

For the first error, i found articles suggesting to add the IgnoreChecks registry (assuming to the server running CRM, not the SQL server), which i did, but it not help (even after rebooting the CRM server). I also confirmed that the Product Key the setup is populating is identical to the one i found in the MSCRM_CONFIG database, the error is obviously misleading. For the second error, i haven't found anything. Interestingly enough, if i run the exact same setup - to the same deployment/sql server - using a 9.0 ISO, its passing with flying colors, except that im not about to update my org to v9.0. See both screenshots below.

All responses (5)

Answers (0)

JoeO 234 on at

Like (1)

Report

RE: Additional Async Server Setup: The product key is not compatible with the installed version of Microsoft Dynamics CRM.

Thats it, I just missed the "Now-Clickable" next button despite the ugly error message :)

The moral of story, look at the positive, not the negative...
Suggested answer

saurabhtiwarii on at

Like (0)

Report

RE: Additional Async Server Setup: The product key is not compatible with the installed version of Microsoft Dynamics CRM.

Thanks JoeO for these updates. I'm glad that the "[ConnectionOpen (SECCreateCredentials()).]SSL Security error" exception has now been resolved post examining the secure channel protocols.

The IgnoreChecks registry key should be on the box where we are installing the new Dynamics 365 CE server role.

One more interesting thing which may go unnoticed even after the application of this IgnoreChecks registry key on to the problematic server is that, you would see this exception however, it would allow you to proceed Next.

Let me know if this helps.
JoeO 234 on at

Like (1)

Report

RE: Additional Async Server Setup: The product key is not compatible with the installed version of Microsoft Dynamics CRM.

Just wanted to update, the second issue was indeed TLS 1.2 related. The SQL server was configured to only accept TLS 1.2. I enabled all the older TLS protocols on all server involved (CRM, SQL, and the new Async server), and it resolved the second issue. I guess the 2016 setup doesn't support TLS 1.2? So after the setup, i can change all servers back to only support TLS 1.2, or am i perhaps missing a service pack?

Btw, IIS Crypto is a great free tool for anyone who needs to mess with these protocols.
JoeO 234 on at

Like (0)

Report

RE: Additional Async Server Setup: The product key is not compatible with the installed version of Microsoft Dynamics CRM.

Hi Saurabhtiwarii,

Thanks for the response. As mentioned in the OP, i have already created this reg key, and im still having an issue.
Suggested answer

saurabhtiwarii on at

Like (0)

Report

RE: Additional Async Server Setup: The product key is not compatible with the installed version of Microsoft Dynamics CRM.

Hello JoeO,

Yes, the first exception which is "The product key is not compatible with the installed version of Microsoft Dynamics CRM" can be addressed by adding the IgnoreChecks registry key to the computer that is running Microsoft Dynamics CRM.

Click Start, click
Run, type regedit, and then click
OK.
In the registry, locate the following subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
Right-click MSCRM, point to
New, click DWORD Value, and then type
IgnoreChecks.
Double-click IgnoreChecks, and then type 1 in the Value data field.

For the 2nd exception which is "Could not connect to the following SQL Server: 'SQLSeverName'. Verify that the server is up and running and that you have SQL Server administrative credentials. [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error."

Seems to be appearing as a result of secure communication channel protocol exception where the client (in this case our CRM server installation wizard) initiates the SSL/TLS handshake to agree for a communication upon a compatible version of this technology.

There are few things which you may check::

1. Check if the the Force Protocol Encryption option is turned on for SQL Server.

How SQL Server uses a certificate when the Force Protocol Encryption option is turned on ::

If you enable Force Protocol Encryption on the client, you must have a certificate on the server and the client must have the Trusted Root Authority updated to trust the server certificate.

support.microsoft.com/.../how-sql-server-uses-a-certificate-when-the-force-protocol-encryption-o

2. Please check the SQL server version and the support-ability of such protocols for this version like TLS 1.0/1.1/1.2. The easiest way to avoid this would be to enable older/newer secure channel communication protocols during the time of the installation for both the clients and the servers (SQL + CRM box). Once the installation passes through, you may fallback to the newer protocols and disable the older ones provided the .NET versions and necessary patches are installed to support SQL service on such technologies.

TLS 1.2 support for SQL ::

docs.microsoft.com/.../sql-server-native-client

3. This seems a bit unlikely as you acknowledged that v9 could be installed without any issues, validate if the SQL boxes being used for these two installations are different. If yes, check the above 3 points for the affected box and also validate the below point.

The Dynamics CRM Server 2016 wizard requires connectivity check through Microsoft OLE DB Provider for SQL Server to start database creation. The installation documentation lists software installed during the setup. This includes the Microsoft SQL Server Native Client. The setup uses this native client and during the phase of the configuration database creation, OLE DB connection is required.