on 01-09-2020 7:37 PM
Hi,
I'm working on VS2019 and CR SP26. My code read data into ADO.NET dataset and I set those datasets as datasource of my reports. When I run program through VS all is good and reports show without error. But when I want to run my program on another computer which only has CR26 runtime installed, it gives an error on calling SetDataSource method for report as below:
System.Runtime.InteropServices.COMException (0x800002CD): Error in File temp_04020c6d-5b84-40d9-8558-bf87b6d5e554 4840_5464_{1C1D3ACF-9F25-45E2-B0EE-BB77F1DDA6B6}.rpt: Failed to load database information. at CrystalDecisions.ReportAppServer.Controllers.DatabaseControllerClass.ReplaceConnection(Object oldConnection, Object newConnection, Object parameterFields, Object crDBOptionUseDefault) at CrystalDecisions.CrystalReports.Engine.Table.SetDataSource(Object val, Type type) at CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSourceInternal(Object val, Type type)
I encounter with this in any program I wrote. Please help to solve this problem.
Thanks in advanced
Sajjad P.
So you don't have the crdb_adoplus.dll file in this folder?
C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86
Did you remove the Legacy... tag in your app.config file?
Look in here: C:\Program Files (x86)\SAP BusinessObjects\InstallData\logs\DateFolder
In there is the install log, search for the file and see what it tells you.
No reason for the file not to be installed on a clean PC.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have point the exact root cause.
crdb_adoplus.dll was missing in my crystal report installation directory.
C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_x64
I have re-installed crystal report runtime with admin privilege crdb_adoplus.dll is installed. And report is opening perfectly.
Thank You
Khalid
Dev reversioned crdb_ado.dll to be in line with 13 versioning, so it's now version 13 and not version 14.
All you need to do is uninstall CR for VS before upgrading.
We are not going to change it back so uninstall first before upgrading.
I have not had any problems with my test images and main PC where I do all my testing.
Don
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Looks like you've had the same problem I'm suffering from. I also use dataset to generate reports and it is not possible to just install the MSI for the end users without repairing the installation or doing a complete reinstallation. What I have come to realize is that the smallest traces of older Crystal Reports will destroy the installation. Unfortunately I have no computer that has been completely without CR so I do not yet know how a clean installation works. Will try to test it today. Actually, a clean installation does not matter if it works or not, end users must be able to both upgrade and install new without error when they start a report.
Se below post
https://answers.sap.com/questions/12937477/sp26-and-installation.html
Mikael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi mikael.kratz, I resolve my problem. A file needed to load datasets does not install with runtime and I manually copy the missing file to client computer and it works perfectly. (crdb_adoplus.dll) you can see complete explanation in following link: This Link
hello Sajjad Pirahesh
Thanks for that! I have gone back to SP24 and VS2017. SAP has for some unexplained reason changed the version of this file (crdb_adoplus.dll) to v13 from v14 despite the known consequences. When upgrading I can imagine that the installer does not install this file as V13 is lower than V14. They should change their installer so that the file is copied regardless of version which is the normal thing to do if you downgrade the version to a file and there is a risk that there may be a version that is higher in version.
I remain on SP24 and await and see if SAP fix this installation bug, if it is not fixed then we are probably forced to start checking for something else. You should not have to cross your fingers with every update and hope that the reports work.
I really hope they fix this for the next service pack.
MikaeI
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.