Is Crystal Reports 11.5 R2 (11.5.12.1838) compatible with Windows 10 Pro 64-bit?

[christian_d_2017]

Hello,

Using Crystal Reports 11.5 R2 (11.5.12.1838), on a Windows 10 Pro 64-bit computer, when trying to run a report based on the Microsoft OLEDB Provider for Oracle (MSDAORA) and using data stored in Oracle 12c database, I get the following error:

Logon failed.

Details: ADO Error Code: 0x80004005

Source: Microsoft OLEDB Provider for Oracle

Description: Error while trying to retrieve text for error ORA-01019

Native Error: 1019 [Database Vendor Code: 1019 ]

However, on the same Windows 10 Pro 64-bit computer, if I first run a report based on the Oracle Provider for OLEDB (OraOLEDB.Oracle) and using data stored in the same Oracle 12c database, then all the reports defined to use Microsoft OLEDB Provider for Oracle (reports that, previously, raised – without exception – the above error) will now be generated successfully, as long as the instance of Crystal Reports ActiveX Designer Run Time Library 11.5 – used to run the first, OraOLEDB.Oracle-based report – is not released!

Is Crystal Reports 11.5 R2 (11.5.12.1838) compatible with Windows 10 Pro 64-bit?

Do you have an explanation for this Crystal Reports 11.5 R2 behavior?

Thanks,

Christian

[christian_d_2017]

1. In the description area for my question, the mention Using Crystal Reports 11.5 R2 (11.5.12.1838) should be interpreted as using the client-side ActiveX viewer, provided by Crystal Reports 11.5 R2 (11.5.12.1838), for the purpose of viewing (running, executing, or generating) reports – and not as the environment for designing reports!

For various reasons, upgrading to the latest Crystal Reports version (2016) – for report viewing purposes – is not an option!

2. I have been able to successfully view (run, execute, or generate) reports, based on Oracle 12c (12.1 and 12.2), and using the client-side ActiveX viewer provided by Crystal Reports 11.5 R2 (11.5.12.1838), by installing ODAC 12.1 Release 1 32-bit, on the client computer.

(https://answers.sap.com/questions/320517/crystal-reports-115-r2-and-oracle-12c.html).

3. In the description area for my question, I have mentioned that I have found a way to successfully view reports, on a Windows 10 Pro 64-bit computer, using data stored in Oracle 12c databases, and the client-side ActiveX viewer provided by Crystal Reports 11.5 R2 (11.5.12.1838). I agree that the solution I found is ugly – but, nevertheless, it works flawlessly.

I have made these comments to help developers that might face similar issues.

Apart from these 3 aspects mentioned above, you prompt answer is accurate.

Thanks for your efforts,

Christian

[former_member614949]

Hi Christian,

I am using Crystal reports 10 and able to view the reports successfully by connecting to the Oracle databases which are lower than Oracle 12.2. But, getting 'Logon failed' error with Oracle 12.2.

Is there any solution for this?

Thanks in advance,

Praveen.

[christian_d_2017]

Hello Praveen,

I assume there is nothing wrong with the username/password you have provided for the reports (I.E. they can be successfully used to connect to the Oracle database) so the problem is elsewhere.

Your environment is clearly different than mine:

• I use the client-side ActiveX viewer, provided by Crystal Reports 11.5 R2 (11.5.12.1838), while you are using report viewer from Crystal Reports 10;
• I use Oracle 12.1c and 12.2c, while you use Oracle 12.2;
• I use Windows 10 Pro 64-bit computer, while I don't know what Windows version is installed on your computer;
• I use reports based on Microsoft OLEDB Provider for Oracle (MSDAORA), while I don't know what OLEDB Provider your reports are using; etc..

However, you could install ODAC 12.1 Release 1 32-bit, on the computer you use to generate the reports, and see if they are now executed without errors.

If you still get errors after installation – and assuming these faulty reports are based on the Microsoft OLEDB Provider for Oracle (MSDAORA) – then you could try the solution I have mentioned in my original question (but keep in mind that I have successfully tested this solution only for Windows 10 Pro 64-bit computers – for Windows 7 32-bit/64-bit computers, this solution is not required, as the reports are executed successfully using ODAC 12.1 Release 1 32-bit, Crystal Reports 11.5 R2 (11.5.12.1838) and Oracle 12.1c/12.2c😞

1. create a new report (what I call an initiator report) based on the Oracle Provider for OLEDB (OraOLEDB.Oracle) and using data stored in your Oracle 12.2 database (any simple report will do; by example, a report that returns the current date/time from the Oracle 12.2 database – see the attached image);
2. execute this initiator report (don't close it);
3. without stopping the initiator report's execution, generate one of your faulty reports.

If the latter is executed without error then you have a solution for your reports. Otherwise, you'll need more investigation.

Regards,

Christian

[DellSC]

That version of Crystal has been out of support for a number of years. It doesn't support either Windows 10 or Oracle 12c. You'll need to upgrade to the latest version which is Crystal 2016.

-Dell