In order to pass a PCI Compliance scan, we needed to disable SSL3/TLS1.0/TLS1.1 on our server running SQL Server.
After getting SQL Server patched to make this possible. We ran our application
against the DB, at first it did not work until we had to make sure that the client PC's
had .NET framework 4.5 or higher (not specifically related). After that the client app worked as it did before
against the SQL server ...Except one thing. Now Crystal Reports won't run against the DB.
Now when we run a report, it will always prompt for DB credentials and even if we provide them it will not connect to the DB.
This is started as soon as disabled the above protocols. In our app, we pass in the DB credentials.. and it worked until now.
So, it is obvious related to disabling the protocols (?).
We then attempted to run CR2008 designer against the same DB, the designer will not connect to that SQL Server either.
Environment
CR 2008 report designer
Tested with both Visual Studio 2013/2015
Tested with .NET 4.0 and.NET4.5 and .NET 4.6
App is compiled as 32bit
Crystal Run Time (tested with both)
Crystal Reports XI Release 2 .NET 2005 Server (11.5)
SAP Crystal Reports, version for Microsoft Visual Studio (latest version sp15/v.13.0.15.1840)
SQL Server: tested with 2012 and 2014
We do NOT use encrypted connections to SQL Server
Anyone know if/why CR run-time uses any of the protocols above? If CR does use ssl in some form,
is there any way to force it to use TLS1.2?
Any other thoughts or suggestions?