Untitled Document
Results 1 to 9 of 9

Thread: UPS Pro EOD Error

  1. #1
    Hi Support.

    Mutual customer is running ShipRush UPS PRO v12.1.11.8150 and yesterday received the following error when trying to do the End of Day:
    Upload PLD transaction failed: Error 50510 (details: STAGING_FAILED [5007])

    Nothing is their environment changed but their IT Manager indicated that the area the business is located in had some communications issues yesterday. Tried again today without success and receiving the same error

    They only have 1 UPS Account.

    Any assistance is much appreciated.

    ASU

  2. #2

    Join Date
    Apr 2004
    Posts
    16,960
    SYSOPS is offline
    Try this kbase article first:

    https://www.zfirm.com/Knowledge_Base.../SR3P-0033.txt

    The error would indicate a bad record was generated (shipment) and that is causing the issue

    Thank you,
    SYSOPS
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

  3. #3
    Step D in the Kbase article states:
    d) Identify the most recent 'ready' record

    Can you explain how I do this?

  4. #4

    Join Date
    Apr 2004
    Posts
    16,960
    SYSOPS is offline
    After you set the date range, you should see a status of ready (column) for what should be the last EoD attempt

    HTH,
    SYSOPS
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

  5. #5
    Hi SYSOPS.

    We followed the direction given. We rebooted the server (the software is running on a Citrix Server) and tried the EOD again.

    Still failed. Trying to upload the same PLD? I thought the procedure would generate a new PLD?

    Need additional guidance.

    Thanks,
    ASU

  6. #6

    Join Date
    Apr 2004
    Posts
    16,960
    SYSOPS is offline
    That could mean that there is data in the PLD itself causing this. As a quick solve....follow the same steps, but postpone the EoD for that particular day. If issue persists or crops up again, a review of the shipments for that day will be required to locate the offending shipment. What we've seen in the past is that in an SDK environment, some element for a FedEx shipment is sent with a UPS shipment, throwing a wrench in the EoD process.

    HTH,
    SYSOPS
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

  7. #7
    I am not sure what you mean by postpone the EoD for that particular day which is March 19th. There are other PLD files since the 19th that have been created by not sent. Should I move the PLD out of the directory and let the others go? I will work with the customer to see what is in that shipment. Let me know how to postpone that particular EoD.

    Thanks,
    ASU

  8. #8

    Join Date
    Apr 2004
    Posts
    16,960
    SYSOPS is offline
    The EoD that is failing (March 19th) is more than likely keeping the others from uploading as well. Follow the kbase article to locate that EoD, but instead of doing the steps to force new PLD, select the option to postpone. One missing EoD is better than multiple (all that are not uploading since then).

    HTH,
    SYSOPS
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

  9. #9
    Thank you for your help. Postpone worked and permitted other EoDs to process.

    Stay Healthy!

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •