Skip to main content

No response from workstation for Scales via ShipStation Connect

  • Aug 2, 2022 2:05 PM UTC
  • 3 replies
  • 2 views

We have recently started getting the following error: "no response from workstation" when we select the scale/weight during packing/shipping in Shipstation. The issue started a couple of weeks ago, then sort of faded now they are frequently occurring again on multiple stations.

 

I de-activated the scale server via SS Connect and scales, re-added, that corrected the issue for a bit but it now has come back. I also tried the URL/Host fix here: https://help.shipstation.com/hc/en-us/articles/360026157851-ShipStation-Connect#UUID-237be7ba-7203-6bcc-dbd3-9b5ca2bdfa50_UUID-b2481411-f4d6-c1e8-e372-0b6a8543e550

 

We ship via iPads with Shipstation running in Safari. Scales sit on a dedicated PC/workstation at each shipping station linked via ShipStation connect. We have had this setup for years without issue. ShipStation support said they reset something on their side but still no luck. Scales are Mettler Toledo BC-60.

 

Has anyone come across anything like this before? I've all but ruled out hardware as being the culprit so I'm not sure what else to try.

 

 

3 replies

BC-Shipping
  • Employee
  • Aug 2, 2022 5:24 PM UTC

My scale resets every morning (and sometimes during the workday) since being forced over to V3. I have to reselect it daily. I don't get an error message though, so if it randomly resets during the day, I find that most of my shipments have the default weight and I'll have to void and reship all of them.


  • Sep 5, 2022 11:30 PM UTC

I'm having a similar issue with my 24" iMac losing the connection to the scale and label printer daily, multiple times a day since V3 was introduced.  Shipstation Connect is junk since May.  It's unstable at BEST.  I find I have to reboot multiple times throughout a shipping day and eventually just manually enter weights and print labels.  I'm about ready to jump ship and find another alternative. 


  • Jan 28, 2025 5:57 PM UTC

As of today we still have no fix for this issue - we might need to switch out of shipstation