cancel
Showing results for 
Search instead for 
Did you mean: 

Crystal Reports 2020 not retrieving databases ... driver/provider?

colin_f
Discoverer
0 Kudos
2,105

Hello,

I have installed Crystal Reports 2020 onto windows server 2016 (Trialling out first before installing on my machine, replacing existing Crystal reports, older version). Trying to connect to sql server 2019 running on windows server 2019. When adding new connection, I select OLE DB (ADO) , then select "microsoft ole db provider for SQL Server". I type in server name, click windows auth tickbox, then when clicking on the database dropdown, nothing happens for a minute, then drop down is empty.

Not quite sure what is happening here, I think this could be something to do with Microsoft OLE DB provider (which I believe is SQLOLEDB) not supporting TLS 1.2. Came to this guess as when I tried selecting the SQL Server native client, the databases did load ok; but my understanding is that this is deprecated.

If this issue is to do with drivers/providers, what is the recommended driver/ provider for Crystal Reports / SQL Server?

Or please let me know if there could be another explanation.

Thank you

View Entire Topic
DonWilliams
Active Contributor
0 Kudos

Also, for the .NET application go here to get the latest SP 35 CR for VS:

https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html

Install the EXE, right click and select Run As Administrator to provide permissions to register all components etc. on your Development PC.

Note there is a 32 bit installer for VS 2010->2019 and a 64 bit installer for VS 2022.

Don't install the MSI packages separately, the VS install does this for you, at the end of the installer do select the 32/64 bit runtime, VS needs both installed.

For distribution include the MSI package for your platform, x86/x64, with your install package or manually install them under an Admin account, same permissions required.

Once you update each report using the info provided by Jamie your reports should run fine, note that if you are going to use TLS 1.2 you must update the reports with a supported MS Client. You can't replace the Client at runtime.