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

Route export (TCX/GPX) failing this morning?

Maybe it's a temporary thing, but the TCX and GPX files I export from one of my activities can't be processed by other programs this morning. The exported file is non-zero in size but seems to have no information. Export to Google Earth fails (jumps to "This webpage is not available"), and so does the "Save as Course" function (the new course shows a start point but no routed path).

The problematic activity is publicly visible, so here it is: http://connect.garmin.com/activity/616306043

I tried another, more recent, activity and the export worked fine. But a third activity I randomly chose also failed to export correctly. Any ideas?

0 JimDonahue over 10 years ago

Bumping my own thread. I'm hoping that someone else will either add an example of their own activity that won't export successfully (confirming the general problem) or see if they can successfully export a TCX file of my activity and then upload it to another site or to other software (showing the problem is isolated to me).

0 Former Member over 10 years ago

Not necessarily related, but I cannot export to any format: I get a Tomcat error page when I attempt it telling me that I don't have permission to export.

0 TexasChip over 10 years ago

I'm experiencing the same problem. Here is the error message I get:
HTTP Status 403 - You do not have sufficient privileges to view the activity with id 651118723.
type Status report
message You do not have sufficient privileges to view the activity with id 651118723.
description Access to the specified resource (You do not have sufficient privileges to view the activity with id 651118723.) has been forbidden.
JBossWeb/2.0.0.GA

If I go and change the activity privacy to Everyone, then I am able to export. This was not the case a few months ago when I was using Export frequently.

0 JimDonahue over 10 years ago

Coming up on three months and Garmin still hasn't addressed the activity corruption issue reported in mid-December 2014. This was officially reported through Garmin's support system, with confirmation via email from Garmin Tech Support that the bug is real. Not only were they able to replicate the corruption bug, I supplied the original (un-corrupted) tcx file which happened to still reside on my Edge 800 at the time so Garmin developers could try to root-cause the corruption problem.

I exchanged email with Garmin in January and the response was that there was still no ETA for a fix. There's been no update from Garmin since then. The exported TCX file is still corrupted today, and request for export to Google Earth just barfs. Here's what that failure looks like -

This is frustrating for users who assumed cloud storage was a safe repository for their activities, and embarrassing for Garmin. What can we do except continue to bump these threads? They already have our money.

0 Former Member over 10 years ago

Looking at the TCX file from this activity with any text editor: I only see lap summaries, no individual trackpoints within the laps. So there are data in the TCX file, only they are too aggregated for what you typically want to do with it.

0 wolsonjr1 over 10 years ago

1st occurrence for me: https://connect.garmin.com/modern/activity/717984918
I was okay, Edge 500, as of 20150309. On the 12th I got the permissions message, but that cleared and I was able to export tcx (which I need for altitude data). I think the permission problem was due to the ongoing 'name' updates.
My specifics:
Connect shows elevation data for all rides. I can go back and export tcx for any prior (to Mar 12) ride and get a good file with altitude data. I can export Mar 12 file to tcx and get a good file BUT THERE IS NO ALTITUDE TAG/DATA. The altitude data shows on the elevation graph on the Connect page, so why for this ride doesn't the data export?

0 Former Member over 10 years ago

I have a similar problem with my Fenix 3. Went on a 7km walk this morning. Came home and auto WiFi downloaded the activity to GC. Everything looked good in GC. I then tried to look at the track by exporting to Google Earth. First attempt was notified that I couldn't export to GE. On second attempt it "worked", but the track consisted of 1 point. Successfully exported to GPX and the track opened and looked good in Basecamp. Tried GE from within Basecamp with the same results as above, a single point. Then, used the web based GPXtoKML on the GPX file and opened in GE to the same single point result. Tried different sync methods (auto WiFi, USB) without success. It's definitely not GE or even the export function itself as I am able to successfully export and view previous (two days ago) activity. Really weird.

0 Former Member over 10 years ago

I have a Garmin Forerunner 10. I can export to other formats, but export to Google Earth is not working. Getting the "Webpage Not Available" error.

0 JimDonahue over 10 years ago

It has been six months since I reported this problem to Garmin. Detailed paths for many of my previously-uploaded activities, entrusted to the Garmin servers, are GONE. PERMANENTLY GONE. Garmin responded to the information I emailed to them in December 2014, confirmed the bug, and said they were working on it. They have gone silent since the beginning of 2015. Just a friendly reminder:

---> DO NOT ENTRUST YOUR ACTIVITY DATA TO GARMIN <---

I have no way to store my data from my Forerunner 405 running watch locally at all, because Garmin Express provides no access to the .fit files before uploading them to my Garmin account. I do locally store data from my Edge 800 because that's accessible when the Edge 800 is connected to my computer. I also now have my Garmin account connect to Strava, which will hopefully be more carefully about not corrupting my previously-loaded activities.

0 JimDonahue over 10 years ago

Quick update after another month of waiting

Garmin was still silent on this issue so the other day I sent an email asking for an update. I was surprised by a quick reply that this bug had (coincidentally) just been fixed that very day (Jul 14). Of course I went back to my one example activity and found that a Google Earth export still fails.

It's incredible. Patience exhausted, I fired off a snarky & unhelpful reply suggesting, basically, that they test it again with my publicly-visible example. *sigh*.

I'd encourage other users seeing this same problem to reply to this thread with a pointer to the publicly-visible activity that's failing to export.

Since I'd like to bump the visibility of this thread again later, I'll come back if/when I have any new information. Later I'll post every email exchange I've had with Garmin to highlight how badly they treat their loyal customers who are submitting detailed bugs and providing prompt followup information when it's requested.

My Garmin Edge 800 hardware continues to work flawlessly. Garmin's back-end web software is simply broken and apparently beyond their ability to repair. It's disappointing.