cancel
Showing results for 
Search instead for 
Did you mean: 

Crystal Reports' subreport can't login

Former Member
0 Kudos

Hello,

I am recently switching the data connection of a crystal report from oledb to odbc.

It is tested with 32bit platform, which is fine.

After the report is moved to 64bit platform with Oracle ODBC driver of same DSN name, some subreports cause error as follow:

An exception of type 'CrystalDecisions.CrystalReports.Engine.LogOnException' occurred in CrystalDecisions.ReportAppServer.DataSetConversion.dll but was not handled in user code

Additional information: Database logon failed.

I deleted the subreports from main report, the main report can be shown.

I have set all subreport "data location" from oledb to odbc and verify that all data location is connected to the same ODBC DSN.

Are there any way to determinate which connection is in use at runtime?

Platform: Windows Server 2012R2 64bits

Data Connection: Oracle ODBC Driver 64bits

Connectivity Client: OracleClient12cR1 64bits

Database: Oracle12cR1 64bits

Crystal Report Runtime: SP14

Design Tools: Crystal Report for Visual Studio SP14, Crystal Report for 2013

Development Tools: VS2013

Would anyone please help. thank you very much.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Enable ODBC tracing and see what the cause may be.. Then use a 64 bit ODBC test tool and see if the SQL from the report works also.

Don

Former Member
0 Kudos

Thanks for your help.

I finally got the answer, that's just execute "Verify Database" command

0 Kudos

Ah yes of course, when changing data sources or DB drivers you should always Verify Database.

Always good to check it once in a while also, if you update the client engine that can affect the results also....

Thanks for updating us

Don

Answers (0)