Bug when internet connection is interrupted

Comments

9 comments

  • Matt S.

    Eugene,
    I am sorry to hear that you and your team have been dealing with these connection issues recently and I want to do all that I can get you into a good spot.
    I believe that you are correct in that this is not an issue that we have came across in the past, however I will do what I can on our end to investigate this and find a viable solution.
    That being said, I have opened a ticket with you while we continue to address this issue.

     

    -Matt
    ShipWorks Support Team

    0
    Comment actions Permalink
  • Philip Doolittle

    I reported this same issue on May 05, 2019, Request # 10126.  My comment was as follows:

    "When internet connectivity is lost and restored, Shipworks will not download unless it is restarted. App complains of not being able to reach Shipworks server."

    The response was:
    "Unfortunately ShipWorks cannot "refresh" until you close and open the software after internet connection is lost. I have submitted a feature request on your behalf to get a 'refresh' feature added to ShipWorks so you will not have to restart the program each time you lose internet. "

    Over the past few months it appears to have gotten better (i.e. it auto recovers when connectivity is restored), but is not 100%.

    0
    Comment actions Permalink
  • Eugene Wright

    I'm on the latest version and it still acts the same way. It never did that until they changed the plan structure. Before, when each commerce channel was a separate license, SW would check license status individually prior to shipping or downloading. Now it is all grouped together, and somewhere in there, a line of code is out of order. If Wes was still at the company they would have fixed it in ten minutes, it is clearly a bug, but I can't even prove it to them now. In our workflow situation it is a huge annoyance that I have to deal with daily. IDK if Windows version has anything to do with it, but I doubt it.

    1
    Comment actions Permalink
  • Philip Doolittle

    I agree that the start coincided with the code change.

    FWIW, I am on Win 7 pro running Sql Express locally.

    0
    Comment actions Permalink
  • Philip Doolittle

    Happened again. No recovery without application restart this time.


    0
    Comment actions Permalink
  • Gerald

    Phillip,

    I apologize that this is consistently causing interruptions in your shipping process. I would like to create a support ticket, using this account, to reach out and see if we can discuss further.

     

    Thank you,

     

    Gerald

    0
    Comment actions Permalink
  • Philip Doolittle

    Ticket # 10126

    0
    Comment actions Permalink
  • Eugene Wright

    Same here,  Win 7 pro with Sql Express locally.

    0
    Comment actions Permalink
  • Philip Doolittle

    If the on-screen error messages are to be believed, the problem is caused by the application being unable to resolve the DNS name for the ship Works server. Once it is unable to resolve the name the dns component in shipworks gets stuck.

    If we knew the specific hostname the application was trying to resolve we could create it as a static entry in our own DNS. This might prevent the compiled the DNS component from failing a look up and getting stuck. I might dig into the log file tomorrow and give this a try.

    That said, if we don't find a workaround this is going to be with us for a while. Shipworks has stated that this issue (bug#  31899) is not on their development roadmap this year.

    0
    Comment actions Permalink

Please sign in to leave a comment.