Manifest / Quick Ship error: source

QuickShip
1

This one does not seem to have been covered in the other posts regarding Manifest/QuickShip errors.

When freighting, we get this error: Value cannot be null. Parameter name: source —

Shipment details:

Ship via: FedEx Ground
Billing Type: FedEx Collect
Account number: populated and appears valid
Ship to address fully populated

Package code is defined in Epicor and in QuickShip; codes match
FedEx Ground is defined in Epicor and in QuickShip; codes match

Anyone have any thoughts on this?

Thanks.

Sam

2

Double-check your customer/ship to address. Is Address1, Address2, etc. all in the correct location? Sometimes we would have the Address1 field missing a value or Address1 and Address2 inverted and that would cause errors like these. It is possible the street address needs to be in the first address field.

Ross

3

The Ship To address is formatted correctly.

The Bill To address is a PO Box - should that make a difference?

4

No, only the address that is being shipped to is used in the Freighting process.

Ross

5

We keep notes on QuickShip issues and this has normally related to an invalid Fedex account number. We see this error when provided an incorrect account number or a number that doesn’t match the shipping address.

6

Do you have access to the logs? Most of the time I find FedEx returns the info needed and it doesn’t get back to the UI.

1 Like
7

Thanks, all.

@Doug.C – you are correct. The needed information did not get back to the UI. The zip code was invalid for the state (or the city, not sure which).

Interestingly, Epicor Support tried to ship it via UPS and UPS returned a meaningful error message. Not sure why the FedEx information does not get back.

8

We found that during testing. If it didn’t work on FedEx, try it on UPS and see what the error was.

What version of QS are you using?

9

5.1.0.9761

10

Same here. Evidently the newer versions are better on error feedback.

11

@Doug.C

Me again. Same issue has surfaced and shipping via UPS does not give the answer. I can find print monitor logs but not logs that show error messages.

We have an application server, a database server and a “third party apps” server, which is where Quick Ship is. Found the print monitor logs on the third-party apps server, but nothing else, log-wise.

Thanks.

12

If it’s enabled in your web.config file, then you should have a CarrierXMLFile in your base QuickShip website directory. In there you will find all of the log files pertaining to the shipments.

For Example UPS:

  1. EpicorRequest_SiteID_PackNum.xml
  2. shipmentRequest_<<GUID>>.xml
  3. UPS_APIShipRequest_#####.xml (5 digit number)
  4. UPS_APIShipReply_#####.xml (same 5 digit number)
  5. shipmentResponse<<GUID>>.xml
  6. EpicorResponse_SiteID_PackNum.xml

For Example FedEx:

  1. EpicorRequest_SiteID_PackNum.xml
  2. shipmentRequest_<<GUID>>.xml
  3. shipmentResponse<<GUID>>.xml
  4. FedExShipmentRequest_#####.xml (5 digit number)
  5. FedExShipmentReply_#####.xml (same 5 digit number)
  6. EpicorResponse_SiteID_PackNum.xml

The web.config file should look like this in order to generate these XML files:

    <add key="Archive" value="True"/>
    <add key="ClientSettingsProvider.ServiceUri" value=""/>
    <add key="GenerateXMLFiles" value="true"/>
    <add key="DaysToKeepXMLFiles" value="31"/>
1 Like
13

Thanks soooooo much. Figured it out. Much appreciated.

14

Good! I just upgraded us to 5.4 … It reports errors much better.