Has anyone run into the following vague error when trying to connect Shipstation. I have followed the Shipstaion documentation here:
But get the following error shown below.
Any ideas on what the issue maybe?
Page 1 / 1
Hi
Thanks
Hi
Contact ShipStation Support – ShipStation Help U.S.
Hi
HI
Were you ever able to find a solution? I am dealing with this now and all ShipStation support said was “ask your VAR” (which, is my next step...)
Here are some common issues experienced by users, potential causes, and available troubleshooting tips.
| Issue | How to troubleshoot or resolve |
|---|---|
| Connection timeout after upgrade | If you have upgraded your Acumatica package to 23R1 or 23R2 and are experiencing a connection timeout, refusal, or unauthorized message, follow these steps to resolve the issue: Go to Web Service Endpoints and click on KNShipStationEndpoint. Click Delete. Then, go to Customization Projects(SM204505)>>Shipstation package>>Customization Project Editor>>Publish>>Publish with Cleanup. |
| Error Message: “An error occurred attempting to update orders: Error in XML. Reason: The element 'Item' has incomplete content. List of possible elements expected: 'Name, Quantity, UnitPrice, SKU'.” | Add a description on your product within your Acumatica dashboard, for a successful import. |
| The Order Date in ShipStation is different than the Order Date in Acumatica. | This usually occurs because the Acumatica server is using a different timezone than the timezone set in the store's settings in ShipStation, which causes the Order Date to be thrown off when converting the timestamp based on time zone. Update the store's settings so the store is using the same timezone as the server your Acumatica store is hosted on. |
| Orders placed late in the day are not importing into ShipStation. | Similar to the issue above, this typically occurs because the Acumatica server is using a different timezone than the timezone set in the store's settings in ShipStation, which causes our import process to inadvertently skip ahead. Update the store's settings so the store is using the same timezone as the server your Acumatica store is hosted on. |
Thank you
Fortunately, I was able to resolve my connection issue easily enough by entering in the required fields on the Starship Configuration screen in Acumatica (SS101000). Apparently required fields are… required!
I need to reach out to StarShip to have them update their Acumatica > Starship setup instructions to include that step, as it is never referenced before the connection is established in the Kensium manual, or the Starship help page
My reply is for Acumatica 24R1. This still relates to the generic issue of getting the same error message from Shipstation as was originally posted. However, in even after following the steps to delete the endpoint and republish, we had the same issue. Finally, I was contacted be a developer at Kensium, who created the Acumatica package for Shipstation. They informed me that the Currency Rate Type within the Acumatica configuration settings must be populated for the connection to work. Since this is not yet updated in the Shipstation documentation, I am posting it here for others on their search journey.
Additional Note on 24R1: After publishing the ShipStation package for the first time, the access rights to the new ShipStation screens default to "Not Set" for all Roles. To use these screens, you will need to assign the appropriate access rights.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.