Loadmaster Mobile Error Messages

Loadmaster Mobile Error Messages

Common MobileComm Message Errors that Affect Dispatch






Error Message

Resolution

External Application Error:  Trailer [12802] on message does not match trailer [12902] on current move for order: 0003815

Driver Entered Invalid Trailer Number—Generally occurs on the Empty Consignee form.  The stop record (Consignee) will have to be manually updated.

External Application Error:  Trailer [12808] is not available at stop [BIRMINGHAM, AL 35244] for order: 0004212

Driver Entered Trailer that’s not available at the Stop—Occurs if trailer continuity is enabled.  The stop record (Shipper or Consignee) will have to be manually updated.

External Application Error:  Trailer [12802] is currently in use on load [0003815] for order: 0003866

Driver Entered Invalid Trailer Number—The stop record (Shipper or Consignee) will have to be manually updated.

External Application Error:  Trailer SAME not found for order: 0003771

Trailer Number Entered by Driver Is Not in the System—The stop record (Shipper or Consignee) will have to be manually updated.

External Application Error:  Message (54796) Too far from stop [ATHENS, GA 30604] [386] exceeds allowable radius, unable to Auto-Dispatch for order: 0003798

Driver Sent Form Outside the Designated Stop Radius—The stop record (Shipper, Intermediate Stop, or Consignee) will have to be manually updated.

External Application Error:  Error – missing delivery hub reading on Delivery at EXEL (ATL) in NORCROSS, GA

The Required Hub is Missing on the Departure Form – The stop record (Shipper or Consignee) will have to be manually updated.


External Application Error:  The actual departure cannot be before the actual arrival for order: 0163746

The Stop Form Not Successfully Processed…likely due to the load not being put in progress—The stop record (Consignee and Shipper) will have to be manually updated.

External Application Error:  The actual departure time (06/18/2013 1416) of Pickup at Northern Eufaula Logistics in EUFAULA, AL cannot be later than the actual arrival time (06/18/2013 1356) of the following stop (Delivery at Coca Cola of Atlanta in ATLANTA, GA) for order: 0003887

The Stop Form Not Successfully Processed…likely due to the previous load not being delivered—The stop records (Shipper and Consignee of previous load) will have to be manually updated.

External Application Error: Service

Failure Notification:

A service failure record has been created for LAREDO, TX 78045 on order 0029916. Please update with appropriate reason codes.

For order: 0029975

Update the service failure on the order with the appropriate reason code for the delay. This does not break auto-dispatch.

External Application Error:  Nested exception: Could not update the equipment_group record because another user either changed or deleted it. [com.tms.common.lib.data.NoRowsAffectedException: Could not update the equipment_group record because another user either changed or deleted it.]
for order:

The equipment_group errors happen based on drivers that slipseat. Those often happen when a driver signs into a tractor still labeled “in progress.”

External Application Error:  Stop ID on the message does not match any stop on current or next assigned dispatch
for order:

The Stop_ID errors can come from a number of reasons, namely any changes in a zmitted load. Stop_IDs are a unique identifier created for drivers to clear stops more accurately. They work much more often than they cause issues, but they can change for a multitude of reason (if a load is changed/updated by a user, if a movement is zmitted multiple times to one driver, etc.)