# Same SSRS Issues, different message

**URL:** <https://www.epiusers.help/t/same-ssrs-issues-different-message/131885>\
**Category:** Kinetic ERP\
**Tags:** ssrs\
**Created:** [January 12, 2026, 8:43pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885 "2026-01-12T20:43:04Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![kve](https://www.epiusers.help/user_avatar/www.epiusers.help/kve/32/76150_2.png) [@kve](https://www.epiusers.help/u/kve)\
**Post date:** [January 12, 2026, 8:43pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/1 "2026-01-12T20:43:04Z")

</div>

Users still getting massively slowed down by the Epicor Cloud SSRS Printing. Got a new error today, though. Anyone seen this one before?

`Program Ice.Services.Lib.RunTask when executing task 835028 raised an unexpected exception with the following message: RunTask: Ice.Core.SsrsReporting.SsrsCaller.SsrsException at Ice.Core.SsrsReporting.SsrsCaller.RestReportingService.ThrowIfNotSuccess(HttpResponseMessage responseMessage) in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsCaller\RestReportingService.cs:line 351 at Ice.Core.SsrsReporting.SsrsCaller.RestReportingService.CreateCatalogItem(String ItemType, String Name, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, Warning[]& Warnings) in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsCaller\RestReportingService.cs:line 82 at Ice.Core.SsrsReporting.ReportProcessorBase.DeployReportIfNeeded(String printProgram, String fullReportPath, SsrsConfigurationInformation configurationInfo, Func`1 reportingServiceCreator) in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 529 at Ice.Core.SsrsReporting.ReportProcessorBase.RenderReport\_HttpClient(String ssrsRenderFormat, String printProgram, Boolean ignorePageSettings) in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 336 at Ice.Core.SsrsReporting.ReportProcessorBase.RenderReport(String ssrsRenderFormat, String printProgram, Boolean ignorePageSettings) in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 243 at Ice.Core.SsrsReporting.ReportProcessorBase.ProcessReportPart(String reportLocation) in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\SsrsReporting\ReportProcessorBase.cs:line 159 at Ice.Core.SsrsReporting.StandardReportProcessor.ProcessReportParts() in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\SsrsReporting\StandardReportProcessor.cs:line 31 at Ice.Core.RoutingAndBreaking.ReportPersister.Persist(ReportInstanceInformation reportInstance, Func`2 reportsRenderer, Action`1 fillSysRptLstRow, Action`2 processReport, Func`3 filterTableAttachmentsFunc) at Ice.Core.RptBase.ReportSsrsDatabaseBuilder.RenderUnroutedSsrsReport() in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\RptBase\ReportSsrsDatabaseBuilder.cs:line 355 at Ice.Core.RptTaskBase`1.XMLClose() in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\RptBase\RptTaskBase.cs:line 219 at Erp.Internal.PM.POForm.RunProcess(Int64 instanceTaskNum, String outputFileName) in C:\_releases\ERP\ERP12.1.100.0\Source\Server\Internal\PM\POForm\POForm.cs:line 451 at Ice.Hosting.TaskCaller.InnerExecuteTask(IceDataContext newContext) in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 71 at Ice.Hosting.TaskCaller.ExecuteTask() in C:\_releases\ICE\ICE5.1.100.7\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 62 at Ice.Lib.RunTask.BpmFriendlyTaskLauncher.Run(String sessionIdPrefix, IceContext db, Action taskRunner) in C:\_releases\ICE\ICE5.1.100.0\Source\Server\Services\Lib\RunTask\BpmFriendlyTaskLauncher.cs:line 57 at Ice.Services.Lib.RunTaskSvc.InnerRunTask(Int64 ipTaskNum, Boolean suppressTransaction) in C:\_releases\ICE\ICE5.1.100.0\Source\Server\Services\Lib\RunTask\RunTask.cs:line 349`

---

<div class="post-metadata">

**Author:** ![utaylor](https://www.epiusers.help/user_avatar/www.epiusers.help/utaylor/32/64664_2.png) [@utaylor](https://www.epiusers.help/u/utaylor)\
**Post date:** [January 12, 2026, 8:47pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/2 "2026-01-12T20:47:35Z")

</div>

What I find interesting is the first method “DeployReportIfNeeded” and someone somewhere was talking about how the upgrade messed up that flag right? I’d have to find the thread, I forget if it was @aosemwengie1 or someone else talking about all the custom RDDs

---

<div class="post-metadata">

**Author:** ![JMPCONJ](https://www.epiusers.help/user_avatar/www.epiusers.help/jmpconj/32/76359_2.png) [@JMPCONJ](https://www.epiusers.help/u/JMPCONJ)\
**Post date:** [January 12, 2026, 8:49pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/3 "2026-01-12T20:49:10Z")

</div>

Yep. On a scheduled monthend stock status report on 1/1.

> **Screencap inside.**
>
> ![image](https://www.epiusers.help/uploads/default/original/3X/2/1/215022c023b872fe420f6c6c3f65d44f94be9bb3.png)

---

<div class="post-metadata">

**Author:** ![aosemwengie1](https://www.epiusers.help/user_avatar/www.epiusers.help/aosemwengie1/32/95533_2.png) [@aosemwengie1](https://www.epiusers.help/u/aosemwengie1)\
**Post date:** [January 12, 2026, 8:59pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/4 "2026-01-12T20:59:05Z")

</div>

I uploaded a file of 741 ssrs errors last week. I’m sure that one was among them. Only response from support was about completely unrelated BAQ errors in the admin logs.

---

<div class="post-metadata">

**Author:** ![aosemwengie1](https://www.epiusers.help/user_avatar/www.epiusers.help/aosemwengie1/32/95533_2.png) [@aosemwengie1](https://www.epiusers.help/u/aosemwengie1)\
**Post date:** [January 12, 2026, 8:59pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/5 "2026-01-12T20:59:58Z")

</div>

![fire working GIF](https://media1.giphy.com/media/v1.Y2lkPWU5MGVkYmEzeHdjdWNuc3oxMHcxc3J6N2ZraGlkdzhnOW1vaHZhMGY2dHlpeHN2cSZlcD12MV9naWZzX3NlYXJjaCZjdD1n/QQQoLTqkm7v3y/giphy.webp)

---

<div class="post-metadata">

**Author:** ![utaylor](https://www.epiusers.help/user_avatar/www.epiusers.help/utaylor/32/64664_2.png) [@utaylor](https://www.epiusers.help/u/utaylor)\
**Post date:** [January 12, 2026, 9:00pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/6 "2026-01-12T21:00:56Z")

</div>

> [@aosemwengie1](#):
>
> 741 ssrs errors last week

Wild

---

<div class="post-metadata">

**Author:** ![GabeFranco](https://www.epiusers.help/user_avatar/www.epiusers.help/gabefranco/32/80642_2.png) [@GabeFranco](https://www.epiusers.help/u/GabeFranco)\
**Post date:** [January 12, 2026, 9:01pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/7 "2026-01-12T21:01:01Z")

</div>

Similarly, my backlog of errors i’ve logged (which includes the above one in OP) is so long, it literally lags my browser now, so I avoid going into that EpicCare case. Which has been open for many many months. I asked CS if it was useful to continue logging unique errors and was given the helpful guidance “It’s up to me”.

---

<div class="post-metadata">

**Author:** ![aosemwengie1](https://www.epiusers.help/user_avatar/www.epiusers.help/aosemwengie1/32/95533_2.png) [@aosemwengie1](https://www.epiusers.help/u/aosemwengie1)\
**Post date:** [January 12, 2026, 9:01pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/8 "2026-01-12T21:01:55Z")

</div>

Let me translate that for you. Please continue uploading errors to the case so you feel like progress is happening even though no progress is happening. You’re welcome.

---

<div class="post-metadata">

**Author:** ![utaylor](https://www.epiusers.help/user_avatar/www.epiusers.help/utaylor/32/64664_2.png) [@utaylor](https://www.epiusers.help/u/utaylor)\
**Post date:** [January 12, 2026, 9:10pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/9 "2026-01-12T21:10:07Z")

</div>

Is this perhaps an issue that stems from trying to offer a SaaS product on a backbone/architecture/software design that doesn’t fit cloud? Like others started posting on the larger thread? In other words, are they trying to use SSRS in a way it was never designed and that’s why this is happening?

---

<div class="post-metadata">

**Author:** ![aosemwengie1](https://www.epiusers.help/user_avatar/www.epiusers.help/aosemwengie1/32/95533_2.png) [@aosemwengie1](https://www.epiusers.help/u/aosemwengie1)\
**Post date:** [January 12, 2026, 9:12pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/10 "2026-01-12T21:12:58Z")

</div>

We have no idea why this is happening or what the root cause is because all they will tell us is that they are “working with Microsoft” (for over 6 months). I have not heard of anyone on prem running into this which seems to be a good indication its cloud related though.

---

<div class="post-metadata">

**Author:** ![GabeFranco](https://www.epiusers.help/user_avatar/www.epiusers.help/gabefranco/32/80642_2.png) [@GabeFranco](https://www.epiusers.help/u/GabeFranco)\
**Post date:** [January 12, 2026, 9:17pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/11 "2026-01-12T21:17:57Z")

</div>

Possibly.

I think we lack enough information on the customer facing side to determine;  
It appears to be a load/concurrency issue, and SSRS servers in Cloud are 1:many AppServer:SSRS Server, so on the customer side we can’t get a clear picture of the load/task pipeline to arrive at a conclusion.

Among the things Epicor has done/tried is throwing more resourcing at the SSRS server, which caused SSRS reports to return completed sooner, reducing the amount of concurrency, and thus the frequency of the issue.

From my end, it seems as though they could workaround this by implementing a FIFO queue on the SSRS server side, just make things line up, we already wait for reports to process. Additional latency seems preferable over failures. If this slows things down too much, allow limited concurrency (with a check that overlapping report styles aren’t being printed simultaneously, which exacerbates the error)

I suggested this and other approaches, along with volunteering to set up a reproducible scenario on my end. They indicated a queue would be a prohibitive amount of programming at the current time.

I was able to successfully demonstrate a repro scenario and we got more detailed logging out of it (back in September, the error was very generic)

---

<div class="post-metadata">

**Author:** ![utaylor](https://www.epiusers.help/user_avatar/www.epiusers.help/utaylor/32/64664_2.png) [@utaylor](https://www.epiusers.help/u/utaylor)\
**Post date:** [January 12, 2026, 9:20pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/12 "2026-01-12T21:20:41Z")

</div>

I know I’ve asked before @klincecum, but does that emoji mean you need more info?

---

<div class="post-metadata">

**Author:** ![Mark\_Wonsil](https://www.epiusers.help/user_avatar/www.epiusers.help/mark_wonsil/32/51594_2.png) [@Mark\_Wonsil](https://www.epiusers.help/u/Mark_Wonsil)\
**Post date:** [January 12, 2026, 9:25pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/13 "2026-01-12T21:25:02Z")

</div>

> [@GabeFranco](#):
>
> From my end, it seems as though they could workaround this by implementing a FIFO queue on the SSRS server side, just make things line up, we already wait for reports to process. Additional latency seems preferable over failures. If this slows things down too much, allow limited concurrency (with a check that overlapping report styles aren’t being printed simultaneously, which exacerbates the error)

Although the queue solution would be more cloud like. When the queue fills up, the system adds more servers, and as the queue empties, the system shuts down servers.

---

<div class="post-metadata">

**Author:** ![GabeFranco](https://www.epiusers.help/user_avatar/www.epiusers.help/gabefranco/32/80642_2.png) [@GabeFranco](https://www.epiusers.help/u/GabeFranco)\
**Post date:** [January 12, 2026, 9:25pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/14 "2026-01-12T21:25:55Z")

</div>

Epicor does not like to think “Cloud-minded”, methinks.

---

<div class="post-metadata">

**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\
**Post date:** [January 12, 2026, 9:26pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/15 "2026-01-12T21:26:14Z")

</div>

> [@utaylor](#):
>
> does that emoji mean you need more info?

It means I’m thinking.

Which I admit, the older and crankier I get, is increasingly more difficult.

🤔

---

<div class="post-metadata">

**Author:** ![Mark\_Wonsil](https://www.epiusers.help/user_avatar/www.epiusers.help/mark_wonsil/32/51594_2.png) [@Mark\_Wonsil](https://www.epiusers.help/u/Mark_Wonsil)\
**Post date:** [January 12, 2026, 9:30pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/16 "2026-01-12T21:30:49Z")

</div>

> [@GabeFranco](#):
>
> Epicor does not like to think “Cloud-minded”

![shots fired oh snap GIF by Barstool Sports](https://media1.giphy.com/media/v1.Y2lkPWU5MGVkYmEzNnpzbndvNDU4azNzZ2FjY3l1Y2draWx3Y3cxenlveXpxd3ZldzRoNyZlcD12MV9naWZzX3NlYXJjaCZjdD1n/l3PGLmi97ZjRJBuT0L/giphy.webp)

Epicor

![Blocking Shots Fired GIF](https://media1.giphy.com/media/v1.Y2lkPWU5MGVkYmEzNnpzbndvNDU4azNzZ2FjY3l1Y2draWx3Y3cxenlveXpxd3ZldzRoNyZlcD12MV9naWZzX3NlYXJjaCZjdD1n/l1KVaixq8xLxoHEti/giphy.webp)

---

<div class="post-metadata">

**Author:** ![Randy](https://www.epiusers.help/user_avatar/www.epiusers.help/randy/32/51539_2.png) [@Randy](https://www.epiusers.help/u/Randy)\
**Post date:** [January 12, 2026, 9:34pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/17 "2026-01-12T21:34:25Z")

</div>

> [@GabeFranco](#):
>
> implementing a FIFO queue

Our shipping department already is mad at how much longer Pack Slips take to print in Kinetic vs Classic. More delay would just make it worse.

---

<div class="post-metadata">

**Author:** ![utaylor](https://www.epiusers.help/user_avatar/www.epiusers.help/utaylor/32/64664_2.png) [@utaylor](https://www.epiusers.help/u/utaylor)\
**Post date:** [January 12, 2026, 9:34pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/18 "2026-01-12T21:34:42Z")

</div>

Thanks man, I won’t forget that either haha

---

<div class="post-metadata">

**Author:** ![GabeFranco](https://www.epiusers.help/user_avatar/www.epiusers.help/gabefranco/32/80642_2.png) [@GabeFranco](https://www.epiusers.help/u/GabeFranco)\
**Post date:** [January 12, 2026, 9:35pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/19 "2026-01-12T21:35:35Z")

</div>

Imagine how people feel that have scheduled end-of-year reports that may be inventory related or otherwise year end closing related, so the timing of the report is key.

They slept that night, without worry that their reporting would be delivered as needed in their inbox or in server file download. Latency in that case might not be quite so important.

Epicor needs to account for both (all) scenarios in their Cloud product.

---

<div class="post-metadata">

**Author:** ![aosemwengie1](https://www.epiusers.help/user_avatar/www.epiusers.help/aosemwengie1/32/95533_2.png) [@aosemwengie1](https://www.epiusers.help/u/aosemwengie1)\
**Post date:** [January 12, 2026, 9:36pm UTC](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885/20 "2026-01-12T21:36:45Z")

</div>

> [@GabeFranco](#):
>
> without worry

Not sure who you are talking about but I got up at 5am on January 1st because I knew jack shit was going to print correctly

![Tired Spongebob Squarepants GIF](https://media4.giphy.com/media/v1.Y2lkPWU5MGVkYmEzcWRjbG9kMjc1a2MzeDJlOGEyMjd3Ymp1MTVhczdkZ3Z1czhld3B5dyZlcD12MV9naWZzX3NlYXJjaCZjdD1n/xchUhdPj5IRyw/giphy.webp)

[Next page](https://www.epiusers.help/t/same-ssrs-issues-different-message/131885.md?page=2)
