This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot communicate with servers

Not sure when this started, probably a couple of days ago, but from my MAC I cannot connect to the Garmin servers. It sync's and updates activities but not apps.

What's going on Garmin?

ciq.forums.garmin.com/.../1387157.png
  • Express just said it's getting updated. Installed the same 6.7.0.0 version and is now working. Still getting comms error though.
  • Former Member
    0 Former Member over 6 years ago
    I am having the same problem with Express, on Mac. Version 6.7. Wont sync my Fenix 5S or update to 10.0 from 9.20. Watch is syncing normally to Connect on my smart phone via Bluetooth
    Just to see, I installed Express on a PC I have access to, and it fails to download on that machine as well. Fails at the download phase, just like on the Mac version. Does this both on my home network, at work, and on a mobile hotspot LTE from my iPhone. ciq.forums.garmin.com/.../1388455.png
  • Former Member
    0 Former Member over 6 years ago
    I have had exactly the same problem after updating Express to 6.7 on Mac while I had no problem when login in Connect with same credentials. Then I realised that going to 'About' window in Express and clicking any of the links (Privacy policy, for example) it got me to a non existing webpage. Weird. The reason is that these clever guys from Garmin take language ISO code from OS to create the webpage URL but then they do not support all language ISO codes. In my case my OS is configured in Catalan (ca-ES ISO code) so they are redirecting to a https:///www.garmin.com/ca-ES which does not exists. My guess is that they did the same for the login http call and I simply change OS language to spanish to have a ISO code es-ES which I knew it was supported. I was right, it worked without problem and it logged in. My advice is to change OS language to english and country in Express advanced preferences to US and it should work. Once logged in you can revert the changes. As a developer & engineer I still do not believe how this basic bug has passed Garmin QA.
  • Former Member
    0 Former Member over 6 years ago
    I have the same problem, started about 2 weeks ago (think it coincided with express 6.7 update), I'm on beta firmware 10.52 on Fenix 5x - Mac. I tried the above suggestion and have cleaned all the caches, keychain items , added removed device multiple times with different settings. I tried on authentication domain US with system language / date time English (US) and VPN in US (auth domain was en-US) no dice.

    Definitely a bug.

    Here is a snapshot from the logs:
    2018-08-14 11.18.48 (GMT+10:00) | 775 | E | ServerRequest failed with Error:Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../GetPreloadedMapUpdates}
    2018-08-14 11.18.48 (GMT+10:00) | 775 | E | Error getting map updates for [XXXXXXXXX]: Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../GetPreloadedMapUpdates}
    2018-08-14 11.18.48 (GMT+10:00) | 57699 | I | Update Check Complete: [(null)]
    2018-08-14 11.18.48 (GMT+10:00) | 57699 | W | AvailableUpdates: updatesForDevice [XXXXXXXX]: failed to retrieve update group
    2018-08-14 11.18.48 (GMT+10:00) | 64791 | I | Could not clean map cache. Error getting available updates: Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../GetPreloadedMapUpdates}



  • Yep same errors:

    2018-08-14 06.38.40 (GMT+10:00) | 775 | W | AvailableUpdates: updatesForDevice [xxxnxxx]: failed to retrieve update group
    2018-08-14 06.38.40 (GMT+10:00) | 775 | I | Update Check started for device xxxnxxx
    2018-08-14 06.38.40 (GMT+10:00) | 775 | I | MapUpdateEx Flow: UpdateCheck init xxxnxxx
    2018-08-14 06.38.40 (GMT+10:00) | 775 | E | Error reading app info cache at /Users/xxxxxx/Library/Application Support/Garmin/Express/RegisteredDevices/xxxnxxx/IQAppInfo.plist
    2018-08-14 06.38.40 (GMT+10:00) | 775 | I | ConsentService - getConsent:
    2018-08-14 06.38.41 (GMT+10:00) | 775 | E | ServerRequest failed with Error:Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../GetPreloadedMapUpdates}
    2018-08-14 06.38.41 (GMT+10:00) | 775 | E | Error getting map updates for [xxxnxxx]: Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../GetPreloadedMapUpdates}
    2018-08-14 06.38.42 (GMT+10:00) | 60455 | I | Update Check Complete: [(null)]

    Look if I was to guess I'd say the backend has not been setup for our devices. I am also using a 5x with the beta software.
  • Former Member
    0 Former Member over 6 years ago
    I have same problem after updating to 6.7 version, I tried to completely uninstall garmin express and reinstall re-downloaded setup file. Still same error.

    Date/Time: 2018-08-16 23:00:07 +0300
    OS Version: Mac OS X 10.13.6 (Build 17G65)
    Architecture: x86_64h
    Report Version: 26

    Data Source: Stackshots

    Command: Garmin Express
    Path: /Applications/Garmin Express.app/Contents/MacOS/Garmin Express
    Identifier: com.garmin.renu.client
    Version: 6.7.0.0 (6070000)
    Parent: launchd [1]
    PID: 942

    Event: hang
    Duration: 3.60s (process was unresponsive for 255 seconds before sampling)
    Steps: 36 (100ms sampling interval)

    Hardware model: MacBook9,1
    Active cpus: 4

    Time Awake Since Boot: 2100s


    --------------------------------------------------
    Timeline format: stacks are sorted chronologically
    Use -i and -heavy to re-report with count sorting
    --------------------------------------------------

    Heaviest stack for the main thread of the target process:
    36 start + 1 (libdyld.dylib + 4117) [0x7fff503c1015]
    36 NSApplicationMain + 804 (AppKit + 23154) [0x7fff25ae3a72]
    36 -[NSApplication run] + 250 (AppKit + 222851) [0x7fff25b14683]
    36 -[NSApplication finishLaunching] + 315 (AppKit + 223980) [0x7fff25b14aec]
    36 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 (Foundation + 26823) [0x7fff2a6668c7]
    36 _CFXNotificationPost + 599 (CoreFoundation + 358839) [0x7fff285569b7]
    36 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1664 (CoreFoundation + 362624) [0x7fff28557880]
    36 ___CFXNotificationPost_block_invoke + 225 (CoreFoundation + 633569) [0x7fff28599ae1]
    36 _CFXRegistrationPost + 458 (CoreFoundation + 634282) [0x7fff28599daa]
    36 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 (CoreFoundation + 634588) [0x7fff28599edc]
    36 -[AppDelegate applicationWillFinishLaunching:] + 647 (Garmin Express + 515385) [0x10c650d39]
    36 -[AppDelegate checkAndLaunchService] + 550 (Garmin Express + 523346) [0x10c652c52]
    36 -[AppDelegate isServiceAvailable] + 435 (Garmin Express + 524291) [0x10c653003]
    36 -[IPCClient setupConnection] + 544 (Garmin Express + 335629) [0x10c624f0d]
    36 -[NSConnection rootProxy] + 64 (Foundation + 571838) [0x7fff2a6eb9be]
    36 _CF_forwarding_prep_0 + 120 (CoreFoundation + 528872) [0x7fff285801e8]
    36 ___forwarding___ + 748 (CoreFoundation + 529756) [0x7fff2858055c]
    36 -[NSConnection sendInvocation:internal:] + 1197 (Foundation + 576772) [0x7fff2a6ecd04]
    36 -[NSConnection _sendBeforeTime:coder:doAuthenticationCheck:] + 357 (Foundation + 588613) [0x7fff2a6efb45]
    36 -[NSMachPort sendBeforeDate:msgid:components:from:reserved:] + 96 (Foundation + 589072) [0x7fff2a6efd10]
    36 +[NSMachPort sendBeforeTime:streamData:components:to:from:msgid:reserved:] + 1401 (Foundation + 590495) [0x7fff2a6f029f]
    36 mach_msg_trap + 10 (libsystem_kernel.dylib + 78346) [0x7fff5050820a]
    *36 hndl_mach_scall64 + 22 (kernel + 125414) [0xffffff800021e9e6]
    *36 mach_call_munger64 + 509 (kernel + 1513245) [0xffffff800037171d]
    *36 mach_msg_overwrite_trap + 891 (kernel + 398667) [0xffffff800026154b]
    *36 ipc_kmsg_send + 599 (kernel + 322519) [0xffffff800024ebd7]
    *36 ipc_mqueue_send + 294 (kernel + 337574) [0xffffff80002526a6]
    *36 thread_block_reason + 175 (kernel + 550463) [0xffffff800028663f]
    *36 ??? (kernel + 554618) [0xffffff800028767a]
    *36 machine_switch_context + 205 (kernel + 1584605) [0xffffff8000382ddd] (blocked by mach_msg send owned by Garmin Express Service [489])
  • Former Member
    0 Former Member over 6 years ago
    Same Issue for me..... frustrating to say the least as I have tried everything.....
    ciq.forums.garmin.com/.../1396018.png
  • Been having the same problem for the same duration as the OP, tried different networks, etc., but no luck. Both my Edge 1000 and F3 have the same issue, but strangely when I plugged in my old Edge 500, that seems to work









  • Update: three different Macs; five different networks with different router types. All on latest software reinstalled for good measure; firewalls disabled temporally. Unable to connect to servers. As I said previously before the current version the unable to connect issue had gone away for a bit. But over the now it is back and stuck perhaps until the next version. Of course, moderator, the software and the system isn't flakey. It must be all those Macs and networks and routers. I yes, I should spend time talking to different support people educating them that their software/system isn't unstable, its us. Similar situation to when syncing from the Index scale was trashing data. It was our fault, not the flakey software or system. Until garmin admired the problem and apologised after months. So yes, I should just call support.

    Garmin experience summary solid feeling and looking hardware. Unstable software and systems. But it's probably my Mac or my phone isn't it?