As of the update, we had to update the Edge Agent and our prints our now resulting in print preview a majority of the time instead of printing.
We print to Local Printers
I am filling out a ticket with support, but I think they have been bogged down with the many issues.
Anyone else seeing this issue?
I’m having a similar issue getting reports to render (just to get a print preview). So… unfortunately can’t help at the moment… but, you’re not alone!
Yes, we are seeing this too. We’ve been able to work around it by pressing the Print icon twice. Sometimes it prints instead of previews the second time around.
Yes, hahaha. Everyone here spams the print button until it Prints! Usually they get a “be patient,” but the next time it seems to force the print WAY faster than waiting for Epicor to decide to print it when only pressing once… very buggy; but, I’ve never reported it.
Did you happen to get a PRB on this?
Not yet. They wanted to see if it was a specific report or an issue with the smart client so I am trying to explain that part to them and waiting for their reply.
The main difference is that printing will send the printer name regardless where it fails to actually print and sends a preview instead.
The top line is the actual print preview.
We are being asked to recreate steps, but this seems random. If anyone has had luck identifying the steps to recreate, I’d appreciate the help!
I am still working through our ticket. Support connected and was able to print successfully 5 times with the Edge agent at 2 different periods during the day.
We are waiting to connect on a call in the next 2 days hopefully.
We are working through our ticket too – I think it has something to do with the cache. Once it starts happening, we clear the ECM cache and that will stop the problem for some time.
Hi David - Wondering if you’re still running into this issue or if you’ve been able to solve it. I’m not getting anywhere with support unfortunately.
Well, yes and no. I’ve gotten over my hurdles, but with no help from EpiCenter.
But I don’t think MY issue was the same as the original post. You guys couldn’t PHYSICALLY print, you would get the preview. In my case, I couldn’t even get the preview.
In my case, I had issues with SOME of our OrderAcks that (until the latest update 2024.2.4) never had an issue. After the update, various OrderAcks would get hung up in a “Report Rendering” state and the task would get stuck there… never rendering, and I had to get a data fix just so I could kill them and continue testing.
Because it was a customized RDL, they basically said, “yeah, that sucks… I guess you need to rebuild it.”
I eventually found the smoking gun in a bad table join. I was trying to pull in Bill-To Contact information by connecting the CustCon table (I think) and I botched it. I think I finally found a different path in a linked table that worked for what I was doing. So I rebuilt that portion and the problem went away.
Why it was working before (with my bad join) without issue and after the update caused problems, I still can’t say. I have to assume they (Epicor) tightened down some screws and my bad join that was technically getting through before couldn’t pass the muster any more.
So… root cause: ME
Did EpiCare help identify or repair the issue: Nope
And yes, in this case, since it was a bad customized RDL, it shouldn’t be their issue. My only gripe was that, in MY case, the system wasn’t producing any errors. It basically acted like the report passed through okay, but got stuck in rendering. So, I flat out told them the problem was almost certainly on my end… but without an error, how do I even know where to start looking for the problem.
I basically duplicated a problematic Sales Order in our Pilot environment and, while comparing it to other orders that WOULD print, slowly started changing fields one-by-one until I got to the point where it finally printed.
Our support case was a dead end, we did a bunch of reinstalling and trying other report styles and resetting parameters. It still happened but the random nature of it leaves support stumped.
I went back and looked at the calls happening. I’m seeing a consistent pattern after its submitted to edge agent:
It looks like 2 updates get sent every time a report is submitted and one gets locked out by the other. I’m adding this to my ticket and maybe that will get some traction.
Sending a doc to Edge Agent is like flying into the Bermuda Triangle. We’ve had people with the preview problem - completely at random and rare to occur. We’ve even had issues where users had to sign off/on to get something to print. If possible, use the Network Print option rather than Client Print…seems to eliminate the Edge Agent problem and improved speed for us
Thanks, we haven’t tried the Network Print option but we will look into it.
I’ve run into this same scenario with support too many times to count 
Is there some way to step through report generation to see when something fails (like seeing a query execution plan in SQL)? Or add stop-go (I don’t know the right term) breaks in SSRS?
Great that you got it figured out, at least.
Would running the report via the client on a classic screen have successfully generated the print preview?
If there is, I’m not aware of it. Especially being a cloud customer, with little access to the servers.
That’s a good question. Now I can’t remember if any of my printing trials were via the Client or not. If I find time later, I’ll reactivate the buggy report style and test it again in the Client.
We have a PRB PRB0293655
