|
| We recently upgraded Crystal Reports 11 Rel1 to Crystal Report 11 Rel 2 on our development machines.
Dev Enviornment:
1. Visual Studio 2005 Professional Edition (Installed without Cysrtal repprt components) SP1
2. Crystal Report 11 Release 2 SP2 Developer edition.
Our application/s (Win form or Web) developed in Visual Studio uses COM dll. And was handling the exception errors properly.
Meaning, if any exception error is raised in COM DLL, .net application was able to show the error correctly.
COM DLL is configured in COM+ Application.
But after upgrading to Crystal Report 11 Rel 2, our .Net application has started logging "System.Runtime.InteropServices.COMException: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))" error for every exceptions raised in COM DLL.
On one dev machine, we un-installed Crystal Reports 11 Rel 2 and installed Crystal Reports 11 Rel 1, and now exceptions are getting displayed correctly and Catastrophic failure error has gone off.
Has anyone faced such issue?
Actually, we started off using Crystal Reports 11 Rel 1 in Visual Studio 2005. But our application was intermittently throwing "An communication error occurred. Printing will be stopped." OR "System.Exception: Load report failed." with stack trace as "at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened() --> at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob) --> at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename) --> at CashiersSOReport.RunReport(String sSONo, String sSODate, String sSQLPassword, CrystalReportViewer crViewer)" and according to business objects, applications developed using Visual studio 2005 should be using Crystal Report 11 Rel 2 not Crystal Report 11 Rel 1. Since Crystal Report 11 Rel 1 is not supported for Visual Studio 2005. So that's the reason we upgraded to Rel 2. But we have got into other issue.
Any suggestion/s?
Thanks,
|
|