Skip to Content
Former Member
Oct 28, 2009 at 03:22 PM

Error after migration to Crystal Reports 12 for existing reports



We had reports written using Crystal Reports Version 8.5. These reports were not modified for a long time. Recently, we had migrated to Crystal Reports 12 (2008). Some of the these existing reports were modified using the Crystal Reports 2008 designer. After installing our application (we ship Merge Module of Crystal Reports 12 i.e. 2008 which gets installed in GAC)

1) If we create new reports in 2008 designer and try to view these reports, it works as expected without any issue(s).

2 ) However, if these modified reports are tried to be viewed, there is an error which states "Database Logon Failed".


CrystalDecisions.CrystalReports.Engine.LogOnException {"Database logon failed."}

ErrorID CrystalDecisions.CrystalReports.Engine.EngineExceptionErrorID.LogOnFailed

InnerException {"Database logon failed."}

Message "Database logon failed."

Source "CrystalDecisions.ReportAppServer.DataSetConversion"

Stack Trace at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)

at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)

at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToDisk(ExportFormatType formatType, String fileName)

TargetSite {Boolean ThrowDotNetException(System.Exception)}

Also, it is worth to note that if we try to view these modified reports from any environment which has both Crystal Reports 10 and Crystal Reports 12 in GAC, then these reports work as expected.

P.S. We have mechanism in application's code to reset the database connections when any report is being viewed using ReportDocument class' method.

From the above scenario I believe issue is specific to migration to Crystal Reports 12 (2008). Any help /workaround to solve this problem will be highly appreciated.