I don’t know if anyone else is having thus issue. We are unable to print a customized Pack Slip (standard pack slip works).
This is NOT a surprise - we found this testing Pilot over a month ago and gave support multiple warnings that this issue needed to be fixed before Go-Live.
I thought OK maybe this is something I did? However, i made a copy of the standard report style and the copy previewed correctly. However, when I made a duplicate of the PackSlip RDD i get the error message. So I am NOT ABLE to fix this.
I had this entered as a High priority and only got support to say last week that it was fixed in 2025.2.7 - WRONG! I tested early last week and let them know it was still broken.
I was hoping that somehow Live would be different from Pilot - it is not and here we are at the end of day 1 after the upgrade and we went an entire day of production Unable to print pack slips or labels.
Just wondering if anyone else is having a similar issue? or are we alone here?
Our management is asking serious questions right now - and I cannot blame them or give them answers - Like when can we be back in Business?
I had to rebuild our RDD for our Pack Slips today after go live with 2025.2.7 over the weekend. It oddly tested fine in Pilot but in Prod today it’d take over a minute for the print to work though it’d eventually print. With the new RDD it’s still 20ish seconds to get the Pack to print.
So no we don’t have the same issue as you’re seeing. Did you use Kinetic UI or Classic to copy the RDD? I used Kinetic and it worked I did edit the Style in Classic as Kinetic you can’t download the Standard-SSRS RDL file anymore while you can in Classic.
I was getting errors this morning for the exact same problem, but only on certain pack slips. To me, it appeared to only be on phantom packs. While I was looking into the issue, it just started working as expected without me changing anything.
Edit: Shipping had removed the phantom pack without me noticing. That is why is worked.
Yup tried a phantom pack and seen this error in the System Monitor:
Program Ice.Services.Lib.RunTask when executing task 3705172 raised an unexpected exception with the following message: RunTask:
System.ArgumentNullException: Value cannot be null. (Parameter ‘key’)
at System.Collections.Generic.Dictionary2.FindValue(TKey key) at System.Collections.Generic.Dictionary2.TryGetValue(TKey key, TValue& value)
at Ice.Core.RptTaskBase`1.XMLDumpTable(IRow row, String rptTableId) in C:_releases\ICE\ICE5.1.100.7\Source\Server\Internal\Lib\TaskLib\RptBase\RptTaskBase.cs:line 265
at Erp.Internal.SR.PackingSlipPrint.doShipHead() in C:_releases\ERP\ERP12.1.100.7\Source\Server\Internal\SR\PackingSlipPrint\PackingSlipPrint.cs:line 2305
at Erp.Internal.SR.PackingSlipPrint.RunProcess(Int64 Instance_TaskNum, String OutputFile) in C:_releases\ERP\ERP12.1.100.7\Source\Server\Internal\SR\PackingSlipPrint\PackingSlipPrint.cs:line 1088
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
Brilliant - Thank you @Randy and @brendanphilbin At least i can offer that to Support - if we ever hear from them again.
Sadly we create Phantoms for almost every shipment (UPS and FedEx) - however, I will ask them to try not using Quickship to see we can at least print pack slips and Labels.
Let us know when you hear back please - I hadn’t put in a ticket because I figured support would tell me to go to CSG since base works but my custom style doesn’t.
Anyone know where there’s some detailed documentation on what they actually changed about the RDDs? Couldn’t find reference to this change in the release notes, at least not with any real technical information.
You can build the “phantom” pack in Quick Ship, it’s what our users are used to doing. We have tried to get them to switch to Phantom Packs so our customer service team can see the tracking numbers but change is hard.
Yep, we have been troubleshooting this same thing all morning. Apparently it’s tied to PRB0308509, which shows it was opened 22 days ago and listed as “Defect, no workaround”.
We got this at 8:10pm last night from Support. At least someone answered, our CAM is Ghosting us.
There is a known issue in Kinetic 2025.2.7 when printing a PackSlip that includes a phantom pack (erp.CartonTrkDtl) using a Report Data Definition other than the base PackSlip. This issue is now linked to your EpicCare case and has been escalated to our development team. Support will provide an update as soon as new information becomes available
This is terrible for us, the customer shipment notifications were done by routing rules, and now they aren’t triggered as the report is erroring. I hope they fix this quickly..
Mr. @Evan_Purdy: I hope so also, right now I am fighting the corporate platitudes like “I will let you know when we hear from Development” - Whaaaat, we need answers in Hours NOT Days.
I mean for larger teams they can probably develop workarounds and deploy them while they wait for Epicor to do something. Tiny one man places are saturated just putting in tickets and answering panicky users - I don’t have the bandwidth to deal with these kinds of issues.
I chased this down this morning with a debugger, the issue is that the new Packing Slip report IF a Phantom is present assumes there is a “Data Source” (table) in the RDD called “CartonTrkDtl”
The fix is pretty easy, open the ofending RDD
New → Table
ReportTable: CartonTrkDtl
Schema Name: CartonTrkDtl Echema: ERP
change is hard.
