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

Problem with zumo XT and express, cannot connect to server.

I'm trying to download a recently purchased map using Garmin Express to a zumo XT. The error I'm seeing is the common "Sorry, we're having a problem communicating with our servers." error.  I am, however, able to connect using an inReach mini that I also own. Looking through the logs it seems like these are the relevant ones: 

2022-02-10 13.59.44 (GMT) | 53970 | I | Device [3376344247] update with reason: DeviceUpdateRegistration
2022-02-10 13.59.44 (GMT) | 53970 | I | ConsentService - getConsent:
2022-02-10 13.59.44 (GMT) | 53970 | I | ConsentService - getConsent:
2022-02-10 13.59.44 (GMT) | 64993 | I | Looking for DriveHours assets...
2022-02-10 13.59.44 (GMT) | 64993 | I | Looking for DriveLog assets...
2022-02-10 13.59.44 (GMT) | 53970 | E | ServerRequest failed with Error:Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../en_US}
2022-02-10 13.59.44 (GMT) | 53970 | E | Error checking for DLC updates: Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../en_US}
2022-02-10 13.59.45 (GMT) | 53970 | W | OAuthUtil - SSKeychain Error: -25300 - The specified item could not be found in the keychain.
2022-02-10 13.59.45 (GMT) | 64993 | I | Collecting DriveLog assets.
2022-02-10 13.59.45 (GMT) | 53970 | W | OAuthUtil - SSKeychain Error: -25300 - The specified item could not be found in the keychain.
2022-02-10 13.59.45 (GMT) | 64993 | I | Asset successfully collected: DriveLog
2022-02-10 13.59.45 (GMT) | 64993 | I | Looking for ErrorShutdownReports assets...
2022-02-10 13.59.45 (GMT) | 64993 | I | Collecting ErrorShutdownReports assets.
2022-02-10 13.59.46 (GMT) | 64993 | I | Asset successfully collected: ErrorShutdownReports
2022-02-10 13.59.46 (GMT) | 64993 | I | Looking for UsageMetrics assets...
2022-02-10 13.59.46 (GMT) | 64993 | I | Collecting UsageMetrics assets.
2022-02-10 13.59.47 (GMT) | 64993 | I | Asset successfully collected: UsageMetrics
2022-02-10 13.59.47 (GMT) | 64993 | I | Looking for VehicleProfileLog assets...
2022-02-10 13.59.47 (GMT) | 64885 | I | Update Check Complete: [(null)]
2022-02-10 13.59.47 (GMT) | 64885 | W | AvailableUpdates: updatesForDevice [3376344247]: failed to retrieve update group
2022-02-10 13.59.47 (GMT) | 64993 | I | MapUpdateEx Flow: UpdateGroup initWithUpdateGroup 3376769419
2022-02-10 13.59.47 (GMT) | 64993 | I | Could not clean map cache. Error getting available updates: Error Domain=HttpStatusCodeErrorDomain Code=500 "(null)" UserInfo={NSErrorFailingURLKey=omt.garmin.com/.../p
roducts/updates/en_US}

The call to omt.garmin.com/.../en_US which fails with a 500 error uses the zumo XT device ID as a param (3376344247). Hitting that url directly seems to throw a Not Found Error based on the stack trace.

If that same url is hit using the inReach mini ID (3376769419) it doesn't fail explicitly.

I'm seeing the ID's in the RegisteredDevices folder in the Application Support folder for Express. I'm wondering if maybe the ID for my zumo XT is being incorrectly set or if there is a downstream server issue which doesn't recognize either that ID or the api call to that url path entirely. Thanks for any help!