Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Complied application doesn't work for client (Crystal 2008 & VS 2008)

I am creating a VS 2008 (.NET 2.0) application. I am using Crystal Reports 2008 (v12). Everything works fine on my PC. When I move it to one of my client's computers and try to run a report from within the application it bombs out.

I am loading the reports into the Crystal Reports Viewer as objects. It has always worked in the past.

Thanks for insight

Here is the trace:

System.Runtime.InteropServices.COMException (0x8004180B): The document has not been opened.

at CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.set_ProductLocaleID(CeLocale pVal)

at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.CreateRptDoc()

at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper..ctor()

at CrystalDecisions.CrystalReports.Engine.ReportDocument.Initialize()

at CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor()

at CrystalDecisions.CrystalReports.Engine.ReportClass..ctor()

at KaneyFoods.Reports.CustomerInvoice..ctor()

at KaneyFoods.Forms.CRViewer..ctor()

at KaneyFoods.Forms.Invoices.btnInvoiceByNumber_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Former Member


It might be possible that your reports are using the SQL native client connection and the machines prompting for logon might have not native client installed.

Install the native client on a machine and it would resolve your issue.

Hope that works!!



0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question