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

[colin_f]

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

[JWiseman · Accepted solution]

Hi Colin_F,  I'm running SQL Server 2019:

• OLE to SQL Server works for me with V 18.6.5.0 of the 64 bit driver.
• Also using a 64 bit DSN with the SQL Server Wire Protocol (version installed with CR 2020) works as well.
• ODBC with 64 bit SQL Server Driver 18 works AOK.

Do the other (non-OLE) options listed above work for you?  One step when moving to 2020 from earlier versions is that DSNs must be moved to the 64 bit versions as well as do drivers and clients if applicable.

[colin_f · Accepted solution]

Hi JWiseman, first bullet point: this driver you mention: is this part of crystal reports? How do you get this version? Second point: sorry, don't understand this. Third point, odbc: when attempting to use an ODBC datasource I add a connection string with SSPI, but keeps asking for password. Final paragraph, I don't quite follow you re non-ole. I don't know alot about this sort of thing but have always used ole db provider. Also re 64 bit DSN, I think this relates to odbc only, does it?

[JWiseman · Accepted solution]

Sorry I should have asked if you are using the Crystal Reports designer (CRW) or an SDK? If the latter can you please give some specifics.

If using CRW, you can get the latest OLE 64 from here and hopefully that will resolve the issue of nothing showing up in the Microsoft OLE DB Driver for SQL Server connection dialogue after you enter the DB info.

If you ran a complete install of CR 2020 then the DataDirect Wire Protocol drivers should be installed. Go to the Windows > 64 bit ODBC Data Source Administrator > System DSN > Add and you should see a CR SQL Server Wire Protocol ODBC Driver 8.0.x. Note that if you eve ruse Oracle there's also a Wire Protocol driver for that which negates having to install an Oracle client.

The 3rd point is also related to using a DSN in the Windows ODBC Data Source Administrator as well. 

[colin_f · Accepted solution]

Thanks. I will be using designer (Crystal reports 2020), for creating the report, but will also have .net applications to consume those reports, which will be using the Crystal reports for visual studio developer edition runtime. The application will be installed on user machines, and possibly windows server 2016. User machines will be windows 10/11. Re using CRW, I will try installing the latest OLE64. Could you clarify something: these SQL drivers do not come already as part of crystal reports CRW, or are they already included in Windows 10/11/windows server? Re complete install: I will check later; I did a typical installation.

[JWiseman · Accepted solution]

As mentioned for SQL Server the Wire Protocol can be installed with CR but you need to do a Custom Install and ensure that the Wire Protocol option is selected. The other SQL Server drivers you need to get yourself. Afterwards, you can see which ODBC drivers (including Wire Protocols) were installed with Crystal by going to the 64 bit ODBC Data Source Administrator and look at the Drivers tab...they are prefixed by "CR".

[colin_f · Accepted solution]

Sorry, not got back to this for a while. We have decided to stick to OLE (rather than direct wire). I modified the report to use microsoft OLE Driver (MSOLEDB.1) , which works just fine on 2016; however, this is driver is not installed on standard user machines so cannot use this driver. Have reverted the report back to ole DB Provider (SQLOLEDB) which does work on user machines, but does not work on 2016 server as described in initial problem. The only workaround I think is to not use windows server 2016, but instead use 2019 or 2022.

[DonWilliams]

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.