Custom Sales Orders stuck in "Rendering Report" state (2024.2 issue?)

Kinetic ERP
1

Prior to update no issues. Over the last couple days, however, I keep getting hits with complaints that various sales orders won’t print.

System monitor shows them stuck in “Rendering Report”.

No Errors… so they don’t hit any system logs for me to see what and why they’re getting hung up.

No issues (that I can find) with OrderAck RDL/RDD.

The base, stock, ugly as hell standard SSRS WILL print. but not my custom versions. So, assuming there is an issue with my custom report styles… but all was well prior to the latest update.

Is anybody else seeing any SSRS issues?

Does anybody know of any changes the 2024.2 update made to… well, anything… that may impact this?

I can certainly tweak my RDL/RDD’s as required, but I’m not even sure where to start looking. All I know is they get stuck.

2 Likes
2

I’m having issues. I couldn’t get a certain BAQ Report to run after the upgrade, so I re-created it and it will not run. I keep seeing this error:
Program Ice.Services.Lib.RunTask when executing task 4039776 raised an unexpected exception with the following message: RunTask: Ice.Core.SsrsReporting.SsrsCaller.SsrsException: The SSRS server returned the status code 500 (InternalServerError) with the following error text: The name of the item '' is not valid. The name must be less than 260 characters long. The name must not start with a slash character or contain a reserved character. Other restrictions apply. For more information on valid item names, see https://go.microsoft.com/fwlink/?LinkId=398858. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemNameException

1 Like
3

I’ve been having this issue since before the upgrade but its not reproducible.

4 Likes
4

Yeah, I’ve been scrutinizing every field on sales orders that WILL render vs ones that WON’T and for the life of me, I can’t find a pattern.

Feel like I should start over from scratch and rebuild… but then I keep reminding myself that this report has been in use for a couple years without issue… so something changed on the data, server, and/or service side to cause the issue. But no idea how I’m supposed to find it.

And if it isn’t reproducible… AND it only happens with my custom styles… EpC’s just going to slow play this issue (especially on top of all the other upgrade issues that are flying around).

5

They at least gave me a datafix yesterday so I could delete the stalled reports so I could keep trying. I kept getting the “Bitch, Be Patient!” message every time I tried to tweak something and print again, so troubleshooting at all was impossible until i was able to clear those stuck renders out of active tasks.

3 Likes
6

We are also having issues with two reports. I rebuilt the RDD and re-uploaded the last working version of the RDL. Everything went in fine but we are still receving an error. Currently waiting on a response from Epicare. Heres my error in case it helps…

Program Ice.Services.Lib.RunTask when executing task 842922 raised an unexpected exception with the following message: RunTask:
Ice.Core.SsrsReporting.SsrsCaller.SsrsException: The SSRS server returned the status code 500 (InternalServerError) with the following error text:
The operation you are attempting on item 'ScrapCustom' is not allowed for this item type. ---> Microsoft.ReportingServices.Diagnostics.Utilities.WrongItemTypeException: The operation you are attempting on item 'ScrapCustom' is not allowed for this item type.
   at Ice.Core.SsrsReporting.SsrsCaller.SoapCaller.Call[TContent,TResponse,TSoapHeader](String actionName, TContent content, TSoapHeader soapHeader) in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsCaller\SoapCaller.cs:line 47
   at Ice.Core.SsrsReporting.ReportProcessorBase.IsLatestVersionDeployed(IReportingService reportingService, String itemPath, String contentHashForLatestVersion) in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 394
   at Ice.Core.SsrsReporting.ReportProcessorBase.DeployReportIfNeeded(String printProgram, String fullReportPath, SsrsConfigurationInformation configurationInfo, Func`1 reportingServiceCreator) in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 447
   at Ice.Core.SsrsReporting.ReportProcessorBase.RenderReport_HttpClient(String ssrsRenderFormat, String printProgram, Boolean ignorePageSettings) in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 373
   at Ice.Core.SsrsReporting.ReportProcessorBase.RenderReport(String ssrsRenderFormat, String printProgram, Boolean ignorePageSettings) in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 278
   at Ice.Core.SsrsReporting.ReportProcessorBase.ProcessReportPart(String reportLocation) in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 166
   at Ice.Core.RoutingAndBreaking.ReportPersister.Persist(ReportInstanceInformation reportInstance, Func`2 reportsRenderer, Action`1 fillSysRptLstRow, Action`2 processReport, Func`3 filterTableAttachmentsFunc) in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\RoutingAndBreaking\ReportPersister.cs:line 58
   at Ice.Core.RptBase.ReportSsrsDatabaseBuilder.RenderUnroutedSsrsReport() in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\RptBase\ReportSsrsDatabaseBuilder.cs:line 360
   at Ice.Core.RptTaskBase`1.XMLClose() in C:\_releases\ICE\ICE4.3.200.4\Source\Server\Internal\Lib\TaskLib\RptBase\RptTaskBase.cs:line 224
   at Ice.Hosting.TaskCaller.InnerExecuteTask(IceDataContext newContext) in C:\_releases\ICE\ICE4.3.200.0\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 70
   at Ice.Hosting.TaskCaller.ExecuteTask() in C:\_releases\ICE\ICE4.3.200.0\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 61
   at Ice.Lib.RunTask.BpmFriendlyTaskLauncher.Run(String sessionIdPrefix, IceContext db, Action taskRunner) in C:\_releases\ICE\ICE4.3.200.0\Source\Server\Services\Lib\RunTask\BpmFriendlyTaskLauncher.cs:line 57
   at Ice.Services.Lib.RunTaskSvc.InnerRunTask(Int64 ipTaskNum, Boolean suppressTransaction) in C:\_releases\ICE\ICE4.3.200.0\Source\Server\Services\Lib\RunTask\RunTask.cs:line 471
7

I’m not sure if this is the same issue, but we were receiving a similar issue after our upgrade when the path to the custom report went down another folder past CustomReports.

ex. before the path was “reports/CustomReports/foo/bar”, but when simplified to “reports/CustomReports/bar” it worked fine. I think it looks for the .rdl immediately after CustomReports.

I also had to reupload a few reports that were made in classic report style maintenance from Kinetic using Kinetic’s .zip file upload.

2 Likes
8

@LoganDing That looks like it could be the same issue. So you just fixed it by re-uploading using the kinetic interface and modifying the path?

1 Like
9

Yeah, that fixed it for us.

1 Like
10

Dealing with the same SSRS folder issue since the recent upgrade to 2024.2.5. We’re on cloud so some of the ‘legacy fixes’ (this issue seems to be recurring since 2017) don’t apply.
I’ll try the zip file route and report back.

1 Like
11

No luck on the zip file route. I tried a few times with different folder structures.
Epicor has suggested I recreate the BAQ report using the RDD method (not BAQ Report Designer).
I will try this now and report back.

2 Likes