There are a number of different issues that HAVE been solved, but the issue with the low disk condition errors is unresolved, and Epicor is waiting for Microsoft to tell them how to solve it.
Interesting. Support had us run those 2 conversions as well, but it did not resolve any of our 3 errors we intermittently get on our standard and custom reports: “not found”, “already exists”, and the low disk condition.
2 Likes
A problem was just created for our case with this issue. PRB0304935 has a description of “When multiple executions of the same report occur at the same time, some instances fail to print due to non-thread-safe logic in the report processing flow. This results in inconsistent behavior and partial failures.”
This sounds about right; our team says that SSRS reports work better in the morning when there are not as many people using Epicor. I was told that development is reviewing it now.
1 Like
Yep, same here, always starts failing in the afternoon. They are supposedly working with Microsoft, going on 4 weeks now.
4 Likes
Ok this might sound dumb, but when you customize reports are you uploading them through the classic menu or kinetic menu?
Classic. I used to use the design ssrs > publish function, but they broke that.
3 Likes
Gotcha. The reason I asked is because when I uploaded the report via the kinetic menu, I kept getting errors. When I uploaded via the classic menu, the reports spit out just fine, albeit with a delay. Maybe try re-uploading all the reports you are having issues with in the classic menu. No idea if that will work for you but it did for me.
Our errors have nothing to do with the reports themselves, this is an infrastructure issue. The error is occuring on out of the box and custom reports alike. Rerunning the same custom report with the same parameters a few minutes later succeeds.
2 Likes
Since publishing straight from the SSRS Report Designer broke, we’ve just been uploading straight from the Classic Report Style Menu. Yesterday, after I had already uploaded reports a couple of times, I was trying to upload another one and started getting the low disk error. Tried probably 4 or 5 times and still got the same error. It wasn’t until I logged out of Epicor and back in that I had success uploading a report, and it took a LOT longer than usual. Hadn’t gotten a low disk error with something like that in the last few months.
1 Like
Microsoft themselves have confirmed its a race condition. There is no amount of uploading reports that will fix it.
3 Likes
Development has apparently fixed this in 2025.2, now just waiting on ETA for hotfix.
3 Likes
Microsoft Development?
Epicor development
1 Like
Okay so Epicor created the race condition and Microsoft helped them find that? Is that what you meant in this post?
Its like you think support actually explained the issue to me, have you ever worked with epicor support? 
5 Likes
We have now been informed that a hotfix for this issue is going into nonprod tonight and production this weekend.
3 Likes
Nice
Has the hotfix actually fixed anything for anyone else?
It hasn’t fixed ANY of our SSRS report errors. Now our support technician is saying:
“The issue is that there are several of the same Report Style being printed within a short period of time.”
This is correct. We have several cases where we need to schedule 1 report 20 different times in the same schedule, all having different filters and going out to different groups of email addresses. We’ve had this setup and working flawlessly for many years, but now the system can’t handle this as of 2025.1. This is intermittently affecting reports that users are running interactively too, not just scheduled reports.
Support recommended using a process set which will not work. You can either save a report to a process set OR email it, not both (that I can find).
Anyone else still struggling with this?
1 Like
Can you escalate it? That doesn’t make any sense. Is that a new “feature”?
Its not fixed for us either. When i complained, support said the hotfix wasnt supposed to fix it, only mitigate it. Straight face. I have escalated this all the way up to the VP level for 7 weeks now. Its just crickets.
2 Likes