I've worked with Crystal Reports for several yrs but now with a particular report created by another developer, I cannot change the DB connection/location.
He used an OLE DB connection and created the report for use in a Windows App using Visual Studio. The report works "sort of" in Visual Studio but I have a higher version of VS (VS 2010) than the developer but it is causing issues on the formulas he uses.
I am now just trying to open the report outside of VS directly in Crystal and I can't get it to update the db location.
I created an ODBC linc and tried using it to swap out the db location and it says:
"Data Object cannot be opened/accessed" ... followed by "Unknown Database Connector Error"
I don't know how to troubleshoot this further. Any help will be appreciated. Thanks
I had the same issue, and was able to resolve it by selecting the SQL Server Native Client 10.0 driver rather than the 11.0 one when setting up the ODBC connection.
You have to delete the original if you want to have the same name.
Related
I'm trying to migrate a small .NET application (VS2008, Crystal Report 10, OS Win7 32-bit)
The application has got 2 reports that use some data of an oracle database version 11g Release 2 (11.2.0.1).
When I upgrade the application (VS2019Pro, latest Crystal Report (CR13SP25), OS Win10 64-bit) the application itself runs as expected and the 2 crystal reports show the proper data.
It's only when I open Database Expert in crystal report designer and try to access the Oracle connection, I receive an error when trying to pull the list of tables of that connection.
I've tried all 3 possible Oracle connections and all of them give a (different) error:
(1) Microsoft OLE DB Provider for Oracle (MSDAORA): "ADO error code: 0x80004005 - Error while trying to retrieve text for error ORA-01019"
(2) OLE DB for Oracle (OraOLEDB.Oracle): "ADO error code: 0x8000ffff"
(3) Oracle Server (crdb oracle): "Unknown error in database connector"
Now the weird part is that sometimes I do have access to those 3 connections in Database Expert, meaning the list of tables becomes visible.
This happens very rarely and doesn't last for a long time. I've also noticed that when this happens I can access all 3 different connections, so it's "all or nothing".
This behaviour is the same when I create a new solution and add a new crystal report or when I use Visual Studio 2017 Professional instead of 2019.
Anybody has an idea on how to fix this kind of behaviour?
Thanks in advance!
Finally managed to solve this one.
First I opened the old project in Visual Studio 2019, triggering the conversion screens of both the solution itself and Crystal Reports (choose Yes).
Since my original solution was using the (obsolete) Microsoft OLE DB connection for Oracle I’d first created a new connection, in Database Expert (in An existing Crystal Report), that used the OLE DB provider of Oracle situated in OLE DB (ADO).
Next I replaced the old connection by the new one (again in Database Expert).
After applying this to all of the existing reports, everything was working properly!
I have inherited an SSRS solution that I can't seem to work with. I sat down with the previous owner briefly and he showed me where in TFS to find the solution. The also opened up a few of the RDL files and attempted to give me the gist of modifying a report. Every thing seemed straight forward to me during that session.
Now the original developer is gone and I now have access to the code in TFS. Whenever I try to open one of the RDL files, it opens it up as an XML document instead of opening it in the designer.
I have Visual Studio 2008 and SQL Server 2008 Management studio installed. Any thoughts on what I may be missing like service packs or hot fixes?
Re-run the SQL Server 2008 installer on your machine. You need to install the Business Intelligence Developer Studio component, or whatever it was called in '08.
If you don't have access to an installer, find the SQL Server Express with Advanced Services download (whatever year you need, just make sure it's the "Advanced Services" - here's 2008: http://www.microsoft.com/en-us/download/details.aspx?id=1842 ), and run that; it will also provide an option for BIDS.
ERROR MESSAGE:
Test connection failed because of an error in initializing provider. Unrecognized database format '\nrpi.local\commonData.accdb'
I set up my database and SSIS and everything was working great. However my database was growing and when it got near 100MB i decided to "compress it" The minute I did that my SSIS started to fail 100% of the time and I get the message above.
I have tried using a JET connection, but no luck. I am currently using an ACE OLEDB 12.0
I have tried running SSIS in 32-bit mode, but no luck.
If i pull a backup of the DB before it was compressed everything works again.
Basic Info: Access 2007, Visual Studio 2008 SP1
Any Thoughts?
Download and install the data connectivity componets from Microsoft.
http://www.microsoft.com/en-us/download/details.aspx?id=23734
Then change your provider on the source connection to "Native Oledb\Microsoft Office 12 Access Databse Engine OLEDB Provider"
Also, If your envirnment is 64bit you wont able to use Access as a resource. Go into the properties of your Project and change the Run64BitRuntime property to false in Debugging section and re-try.
Failed to load database information. Details: The database DLL crdb_ado.dll could not be loaded. Error in File (filename) Failed to load database information.
I am receiving this error when i try to run a crystal report from my page. on the server I have installed the CRRedist2008_x86 and the dll file is in the business objects folder, but for some reason it is still not loading. I also checked to make sure I have the msvcp60.dll which is also needed but still am unable to run the report.
The server is running Windows Server 2008, has Visual Studio 2005 installed on it (not sure if that makes any difference). The application ran fine on my local machine, but after uploading it to the server, it's not wanting to play nice.
Any suggestions/help is appreciated.
Thank You
You should get Dependency Walker and open the crdb_ado.dll to confirm all the required files are there. Although checking for msvcp60.dll is generally the right idea, I've found that people are often looking for the wrong version of those files OR that other required DLLs are also missing.
Also, be sure the redist you are using matches the version of Crystal Reports you have referenced in your project. There is a difference between using, say Crystal Reports 2008 on top of Visual Studio 2005,, versus using the BUNDLED Crystal Reports that comes with Visual Studio 2005 (Or 2008, or 2010 for that matter.).
In fact, sometimes people don't realize that their .NET projects are referencing the "comes with Visual Studio" edition of Crystal Reports because they happen to have Crystal Reports version <whatever> installed on their PC.
That said, if you are pretty confident your redist of CRRedist2008_x86 matches what you are using, I'd focus on Dependency Walker to see if it is indicating a missing required file for the crdb_ado.dll.
I have a desktop application that was migrated from .Net 1.0 to .Net 4.0. The application is using Crystal Reports and ttx files as the data definition files. The actual database queries happens in business objects and the data are set using SetDataSource() method.
After I upgraded this to .Net 4.0 (and Crystal Reports for Visual Studio 2010, version 13), the reports still working great on my developer workstation. But when I installed the application on the test machines I started getting errors like this:
Error in File temp_****{****}.rpt: Failed to load database information.
Where the asterics signify some kind of GUIDs.
The odd thing is that the reports that I did not touch continue to work. Only the reports where I had to update the data source (TTX file) generate this error.
I am also getting this error:
The keycode assembly, BusinessObjects.Licensing.KeycodeDecoder.dll, cannot be loaded.
but I do not know if this is related.
The Keycoder error is not the problem. That is currently a warning message that seems to have no effect on anything (as best I can tell).
Don't be confused by the GUID stuff either. It's just a temp name that Crystal gives the report object.
The real error there is simply "failed to load database information". Something in your TTX update is at fault.
You might try running the report in Crystal 2008 on the machine giving you the problem. Your report is out-of-sync with the TTX file.