I was recently made aware of the functionality to edit reports utilizing the “SSRS Report Design” in Epicor via Knowledge Article EpicCare Login - EpicCare.
I followed the instructions -
set user to edit SSRS reports.
Opened Invoice Tracker - an available Invoice
Chose Print
Chose my custom made Report Style
In the "Print Invoice screen, I select “Generate For Design”
In System Monitor I select the record and “Design SSRS Report”
I save a copy of the report definition to a Desktop folder
The ARForm report opens in Report Builder
The first step is to alter the footer area to match my E10 report
==================
at Ice.Cloud.ProxyBase1.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer) at Ice.Cloud.ProxyBase1.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Ice.Cloud.ProxyBase`1.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Ice.Proxy.BO.SsrsReportDesignImpl.UploadAndRenderDesign(Guid sysRowID, Byte[] compressedReportDefinitions, String outputFormat)
at Ice.Adapters.SsrsReportDesignAdapter.UploadAndRenderDesign(Guid sysRowID, Byte[] compressedReportDefinitions, String outputFormat)
at Ice.UI.App.SsrsReportDesign.Transaction.UploadAndRender()
at Ice.UI.App.SsrsReportDesign.ReportDesignForm.BaseToolbarsManager_ToolClick(Object sender, ToolClickEventArgs e)
at Infragistics.Win.UltraWinToolbars.ToolClickEventHandler.Invoke(Object sender, ToolClickEventArgs e)
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
at Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick()
at Infragistics.Win.UltraWinToolbars.ToolMenuItem.OnClick()
at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.DoClickProcessing(MouseEventArgs e)
at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.TextUIElementBase.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
at Infragistics.Win.UltraWinToolbars.PopupControlBase.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.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)
This has something to do with JPG’s. When I delete just the corporate logo jpg it previews fine. If i try to put it back in it errors out.
I tried saving the jpg as a PNG - no luck still get the error.
Note: If i leave the JPGs in the report and manually upload it and run it - it prints fine. It looks like a something to do with preview function in ssrs designer?
DaveO
I have done a little more testing on this issue. I found that by reducing the size of a couple of my images i could get the report to show without error.
At First i thought this was related to one Logo that i had imported because if i deleted the image the report worked. I tried multiple types i.e. BMP, PNG, JPG all with varying settings for quality.
in the end i reduced all my images (mostly signatures) to 96DPI as JPGs saved for Compression size with made them all about half their size and I now have all my images and they work.
I tried searching Report Builder Image Size Limt - however, it did not help - but this sure feels like some kind of size limit for images.
I came across this same error message today and can confirm that removing any images shown under Report Data → Images that were no longer in use did indeed fix the issue.
)