Frustrating Error - Please Help

[#1]

I'm building a windows form app using vb.net, Visual Studio 2008, and CR 2008 (12.0.2000.0). I have a very simple app that loads a report into a viewer control when the form is loaded. About 80% of the time, the report loads with no issue. The other 20% of the time, I receive an exception which Visual Studio doesn't point out where in my code it is, so I'm assuming its the CR viewer that is throwing it. Here is the code I am using, and the associated exception is below. I can't for the life of me figure this out, and the issue has been replicated on a clean system running the CR 2008 SP3 Runtime. Any advice would be GREATLY appreciated.

VB Code:

-

---

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

Dim Report As CrystalDecisions.CrystalReports.Engine.ReportDocument

Report.Load("c:\report.rpt")

crystalreportviewer_main.ReportSource = Report

End Sub

-

---

Exception:

-

---

System.NullReferenceException was unhandled

Message="Object reference not set to an instance of an object."

Source="CrystalDecisions.Windows.Forms"

StackTrace: 3

at CrystalDecisions.Windows.Forms.PageControl.OnMouseMove(MouseEventArgs e)

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

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

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

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

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

at CrystalDecisions.Windows.Forms.PageControl.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Application.Run(ApplicationContext context)

at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

at Rock_Pond_Solutions.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81

at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)

at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)

at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

InnerException:

-

---

Edited by: mlager on Oct 20, 2010 12:41 AM

Edited by: mlager on Oct 20, 2010 12:44 AM

[Former Member]

I can send an RPT file that failed with the following frequencies

(NB. I viewed all 12 pages closed the viewer and then viewed the same report again):-

1st Time

2nd Time

5th Time

(NB. the error always occurs on initial opening of the report and appears to get worse if you go to another window and then return to the application window to view the report. The context change to another windows application and back to the application before viewing the file seems to have an impact on the probability of the error occuring).

Will it help if I post this .RPT file?

Do you need a vb.Net code snippit of the viewer activation code as well as the RPT file?

Edited by: David Smith on Mar 18, 2011 12:18 PM

Edited by: David Smith on Mar 18, 2011 12:19 PM

[Former Member]

Absolutely. I'll contact you over email.

- Ludek

[Former Member]

Due to the intermittent nature of this fault I you need to run my test harness program sequence 20 times rather than 10 times with a <LAST PAGE> <CLOSE> button sequence to view the report using the mouse to be certain the fault will not occur.

However in both the Test harness and our User Interface application:-

If you donu2019t use the form <close> button and use the close window <X> icon in the window frame the problem does not occur!

The company has a global release currently pending that was planned to be released end of this month that we have delayed already.

Have you got any ideas on what the next step is?