Skip to content

Troubleshooting

This guide covers common issues and how to resolve them.

nShift API Connection

"Create Base Setup" fails or returns no data

Possible causes:

  • Incorrect UF API Key ID or UF API Secret Key in ECShip Setup
  • The nShift account does not have API access enabled
  • Network connectivity issues between Business Central and the nShift API

Resolution:

  1. Verify the API Key ID and Secret in ECShip Setup match what was created in nShift Online
  2. Log in to unifaunonline.com and confirm the API key exists under Maintenance → API Keys
  3. If the key was recently created, wait a few minutes for it to become active
  4. Try creating a new API key if the current one does not work

Shipment processing returns an error

When nShift rejects a shipment, an error dialog appears showing the specific error from nShift.

Common errors:

Error Likely Cause Resolution
Missing required fields Address fields incomplete Verify receiver name, address, city, post code, and country are filled
Invalid carrier/service Carrier or service code not recognized Re-download carrier data with Create Base Setup
Account number missing Carrier requires a freight account Set up carrier account numbers (see Carrier Setup)
Invalid weight/dimensions Weight is zero or dimensions are missing Ensure parcels have weight and, if required by the carrier, dimensions

General steps for any processing error:

  1. Read the error message carefully — nShift errors are usually descriptive
  2. Correct the issue on the shipment document
  3. Retry sending — the document remains in Open status after an error

PrintNode Connection

"Test PrintNode Connection" fails

Possible causes:

  • Incorrect PrintNode API Key in ECPrintNode Setup
  • PrintNode account is inactive or expired

Resolution:

  1. Verify the API key in ECPrintNode Setup
  2. Log in to app.printnode.com and confirm your account is active
  3. Generate a new API key if needed

Printers not showing after "Show Printers"

Possible causes:

  • The PrintNode client is not running on the print server
  • The PrintNode client is not connected to the correct account
  • The computer running the PrintNode client is offline

Resolution:

  1. Verify the PrintNode client is running on the computer/server
  2. Check the PrintNode dashboard at app.printnode.com — registered computers and printers should appear there
  3. Restart the PrintNode client service if needed

Possible causes:

  • Wrong printer selected (check default printer settings or per-user routing)
  • Printer is offline or in error state
  • The PrintNode client has lost connection

Resolution:

  1. Check ECPrintNode Printers — verify the printer State is online
  2. Verify the correct printer is set as default in ECShip Setup
  3. If using per-user routing, check Printer Selections for the user
  4. Check the PrintNode dashboard for failed or pending jobs
  5. Restart the PrintNode client if the computer state shows as disconnected

Debug Mode

Enable Debug Mode in ECShip Setup to get additional diagnostic information during shipment processing.

When debug mode is enabled:

  • Additional details are logged during API calls to nShift
  • Error messages include more technical information
  • Useful for diagnosing issues with specific carriers or services

Note: Disable debug mode after troubleshooting to avoid unnecessary overhead.

Test Mode

Use the Use Test Flag to test the entire workflow without dispatching to carriers:

  1. Enable Use Test Flag in ECShip Setup (applies to all shipments) or on individual shipment documents
  2. Create and process a shipment normally
  3. nShift validates and processes the shipment, returning tracking numbers and documents
  4. The shipment is not forwarded to the actual carrier

This is useful for:

  • Verifying initial setup and configuration
  • Testing new carrier services or addons
  • Training users on the shipment workflow
  • Validating addon parameter configurations

Common Questions

Can I re-send a shipment that was already sent?

No, once a shipment is in Sent status it cannot be re-sent. If you need to make changes, you would need to handle the cancellation in nShift Online and create a new shipment in Business Central.

Why are parcel numbers missing the leading 00?

Parcel numbers (SSCC codes) are stored without the application identifier 00. This is by design — the full SSCC code includes the 00 prefix, but ECShip stores only the reference portion.

Can I use ECShip without PrintNode?

Yes. PrintNode is optional. Without it, you can still:

  • Create and send shipments to nShift
  • Download shipping documents and labels as PDF files from the Auxiliary Data section

How do I update carrier data after nShift adds new services?

Run Create Base Setup in ECShip Setup again. This re-downloads all carriers, services, addons, and package codes from your nShift account.

Next Steps