Shipped check box problem

Kinetic ERP
1

Since last weekend’s Epicor cloud update, I have three customer shipments that will not allow me to check the Shipped box. When I check it and save, I receive an Internal Server Error, and the Shipped box does not remain checked.

The affected shipments involve different customers and different part numbers. The quantities are correct, sufficient stock is available, and none of the parts are lot- or serial-controlled. One affected sales order also had other line items ship successfully during the previous few weeks.

I can print the packing slips, and the parts have physically shipped, but Epicor will not mark the packs as shipped. Therefore, I cannot bring the shipments into an invoice group and create the invoices.

This does not happen on every shipment. I have also tried using an Incognito browser window, but that did not help. Classic is no longer available.

Has anyone else experienced this since the recent update? Is this a known 2026.1 issue, and is there a workaround that will let me mark these packs as shipped or invoice them without deleting and recreating the shipments?

2

This isn’t a QuickShip issue, is it?

3

I see this PRB new with 2026. Different error message, but sounds quite similar:

image
image1076×842 41.5 KB

4

Can you get the server logs with the full error?

Do you have any bpms?

5

We have one in the UK when we ship it says cant update record sys row ID and after a few refreshes it works does this sound similar ?

6

We have been experiencing a similar issue since the upgrade to 2026.1. Freighting is successful but errors trying to mark as shipped. Our solution was to delete the pack and order and re-create from scratch, I will submit that our orders only had 1 our 2 line items so this was not to painful. Not sure if it matters but the problem orders had jobs attached.

“Erp:BO:CustShip/CustShipSvcContract/UpdateMaster”

DBExpressionCompiler msg="Query failed to run System.InvalidOperationException: The LINQ expression ‘DbSet<OrderRel>() .Where(row => row.Company == @company_ex && row.OrderNum == @orderNum_ex) .GroupBy(row => row.ReqDate) .Select(releases => releases)’ could not be translated. Additional information: Translation of ‘Select’ which contains grouping parameter without composition is not supported. Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to ‘AsEnumerable’, ‘AsAsyncEnumerable’, ‘ToList’, or ‘ToListAsync’…

7

Yes, i disabled them and the problem is gone. The bpm’s have to be updated

8

The problem was active BPM’s that need to be updated

9

This error has been reported and it is currently being worked on.

10

We are getting a very similar error. We tried deleting and recreating the Pack slip. No luck. Tried disabling BPM’s - No Luck.

<DBExpressionCompiler msg="Query failed to run System.InvalidOperationException: The LINQ expression 'DbSet<OrderRel>() .Where(row => row.Company == @company_ex && row.OrderNum == @orderNum_ex) .GroupBy(row => row.ReqDate) .Select(releases => releases)' could not be translated. Additional information: Translation of 'Select' which contains grouping parameter without composition is not supported. Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to 'AsEnumerable', 'AsAsyncEnumerable', 'ToList', or 'ToListAsync'.
11

We get the same one on the CSF for UK