WMS cloud version WMS Agent failed to checkin Errorcode 7700 sub error code 172

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #49703
    RAR
    Participant
    • Total Post: 32
    • Frequent Flyer
    • ★★★

    I get the following error message in the system information.
    WMS agent failed to checkin (heartbeat): Error code: 7700, sub error code: 172
    WMS agent failed to post: Error code: 7700, sub error code: 172
    WMS Agent http get failed: Error code: 7700, sub error code: 172

    Firewall port 1833 is open according to the firewall specialists
    I used WMS 1.3.1 public cloud version

    In the picture the MQTT server URL is displayed green, but the WMS server URL is white. Also you can edit the WMS server URL whereas the MQTT URL does not. Is this intentional? by design?
    The settings are delivered via DNS to the client

    Systeminformation

    #49730
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Which firmware version are you running?
    Is the client visible and checked-in in WMS?

    CG

    #49739
    RAR
    Participant
    • Total Post: 32
    • Frequent Flyer
    • ★★★

    the latest one 8.6_019 and the client is visible and checked in WMS. Any idea what the error code means?

    #49740
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    I’ve seen that but never found the root cause.
    As it was working, I’ve ignored it

    CG

    #51436
    moose09876
    Participant
    • Total Post: 14
    • Regular Joe
    • ★★

    I’ve been working through this issue for several days now, finally found my solution. Figured I’d share so someone else could see it if they were looking.

    Short version is, some of our thins have not been able to contact a time server for several months and the time has drifted which prevents connecting to WMS properly. If I manually set the time to be correct it will pull the correct config and packages.

    The REASON they weren’t able to contact the time server (from what I can find) is that the thins have to successfully ping the time server before it will send the query for the time.  Once network team allowed pinging the time server through the firewall, it picks up the correct time and config.

     

    Mike

    #51450
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Thanks for sharing

    CG

    #52715
    Phibue
    Participant
    • Total Post: 46
    • Frequent Flyer
    • ★★★

    We’re occasionally facing the same error code when our ThinOS clients (firmware 8.6_303 and 8.6_412) start.

    We’re running WMS 2.1 on-prem and I also checked Mike’s solution. Time server is reachable and “pingable”. So that doesn’t seem to be the root cause.

    The users are still able to login correctly so it’s not THAT bad, but I don’t quite understand where the error is coming from.

    Anyone else experiencing this?

    #54070
    Phibue
    Participant
    • Total Post: 46
    • Frequent Flyer
    • ★★★

    Update: The problem persists with firmware 8.6_511 and 8.6_606

    Still no clue where this is coming from. 🙁

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.