error running a report
hi all. having this error running a report in report builder version 1 on a sql 2008 server.
any ideas? thanks
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The operation completed successfully
at System.Drawing.BufferedGraphicsContext.CreateCompatibleDIB(IntPtr hdc, IntPtr hpal, Int32 ulWidth, Int32 ulHeight, IntPtr& ppvBits)
at System.Drawing.BufferedGraphicsContext.CreateBuffer(IntPtr src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at System.Drawing.BufferedGraphicsContext.AllocBuffer(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.AllocBufferInTempManager(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.Allocate(IntPtr targetDC, Rectangle targetRectangle)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.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)
Thanks again
April 19th, 2011 5:21pm
Hi Dino_2,
According to the error message that you supplied, the issue is much more likely an memory problem based on my research. In general, the System.Drawing.BufferedGraphicsContext.CreateCompatibleDIB calls the Windows API CreateDIBSection, you can refer
to the article below,
CreateDIBSection Function:
http://msdn.microsoft.com/en-us/library/dd183494(VS.85).aspx
According to the doc, CreateDIBSection generally fails with invalid parameters.
For now, I am not sure what did you do before the issue occurred. But, I would suggest you remove some of the elements from the Report, or preview the Report in IE instead.
Moreover, you may decide to try Report Builder 2.0 or Report Builder 3.0 which can be downloaded from follows,
Report Builder 2.0:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9f783224-9871-4eea-b1d5-f3140a253db6&displaylang=en
Report Builder 3.0:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d3173a87-7c0d-40cc-a408-3d1a43ae4e33&displaylang=en
At last, since the problem is an application crash of Report Builder 1.0, I think we need to enable Windows Error Reporting in order to gather a userdump to further work on this error. Please read follows,
Collecting User-Mode Dumps:
http://msdn.microsoft.com/en-us/library/bb787181(VS.85).aspx
With WER, the system generates a user-mode mini dump in the location “%LOCALAPPDATA%\CrashDumps” by default. You can copy the dump file to your development
machine configured with symbols files, and open it in Visual Studio 2008. Next, you can analyze the error / exception, and call stacks to see why the error happens. You may also consider sending the dump to Microsoft CSS support. Support Professionals from
Microsoft will assist you to solve the problem.
Thanks,
Eileen
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2011 9:04am