Unable to export TCX, GPX, or Google Earth

Same here... This sucks, again. I wish Garmin would do more for the quality of their software.

Cheers
Peter

Ditto

Yup no tcx file downloads 8(

workarounds

I have this problem too sometimes, especially with Cycling. Sometimes I select the elevation correction and it works, sometimes that doesn't. The Java server side indicates my Activity is empty, but of course it's not - I can see the route and data on Garmin Connect. If I export to Google Earth, the kml file is just a 232 byte file activity_0.kml.

The workaround I've been using is to export the .fit file and convert it into .kml externally.

count me in

same situation here, server error during the last 24 hours:mad:

GPX download

Same here.. are these threads monitored by Garmin?

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error that prevented it from fulfilling this request.

exception

java.lang.NullPointerException
com.garmin.connect.service.download.activityexport.provider.ActivityGpxSerializer.buildDocument(ActivityGpxSerializer.java:73)
com.garmin.connect.service.download.activityexport.provider.ActivityGpxSerializer.serialize(ActivityGpxSerializer.java:36)
com.garmin.connect.service.download.activityexport.provider.ActivityProvider.writeTo(ActivityProvider.java:38)
com.garmin.connect.service.download.activityexport.provider.ActivityProvider.writeTo(ActivityProvider.java:21)
com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1448)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1360)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1350)
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:716)
javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
org.springframework.security.oauth.provider.filter.ProtectedResourceProcessingFilter.onValidSignature(ProtectedResourceProcessingFilter.java:87)
org.springframework.security.oauth.provider.filter.OAuthProviderProcessingFilter.doFilter(OAuthProviderProcessingFilter.java:168)
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:214)
org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
com.netflix.hystrix.contrib.requestservlet.HystrixRequestContextServletFilter.doFilter(HystrixRequestContextServletFilter.java:53)
note The full stack trace of the root cause is available in the Apache Tomcat/7.0.57 logs.

As mentioned in another thread, I've reported this to Garmin. I've noticed that occasionally the GPX export will work. Though slightly inconvenient, sandiway's workaround is what I've been using.

The workaround I've been using is to export the .fit file and convert it into .kml externally.

I kept exporting an activity to tcx several times and it did succeed. To be more precise, all I did was to reload the page with the error message and I noticed my browser downloaded a tcx file. That's how I knew it worked somehow.

Workaround

I also could get it to download as a Google Earth kml file by refreshing the download link multiple times (basically flooding it). I did this for two activities. I think the success rate was something like 1 in 20 refreshes.

I think the success rate was something like 1 in 20 refreshes.

I think I'll use the workaround for now. :rolleyes: