Same issue it seems 9 years later
Same issue it seems 9 years later
Same issue it seems 9 years later
Only if there was a Garmin outage the day before.
Did you try using Garmin Express or doing a manual upload?
I just raced the Ironman World Championship in Kona. The data is on my Fenix6S, but it is not uploading. When I attempt to manually upload the activity (connected via USB), I get the message, “We don’t support the file type you tried to import”, but it’s a .fit file directly from my watch.
I CAN’T LOSE THIS DATA! Help!!
Hi, and congrats!! Wow that's an insanely long event! By any chance did the battery die before the end?
Regardless, if you can upload the FIT file here sometimes other users can examine it to see what can be fixed. Also what is the file's size? For an event that long it should be pretty big, like 1MB or more. If it's really small though then it's possible a lot of the data has been lost for some reason.
I get the message, “We don’t support the file type you tried to import”
Attach the fit file (zipped) to this thread. We can take a look to see if it is repairable.
Hope I did this right!
[solved]
Thanks for your reply, Kyle. I sent the link to my Google Drive below. I am uploading the file directly from my watch, connected to my computer via USB. I finished the event in 12:34:57, and the fit file is 1.94MB. The data displayed on my watch matches the official race results almost exactly.
Hope I did this right!
MichelleLingenfelser This will work - [solved]
Fixed using Fit File Repair Tool.
Unzip then do a manual upload to Garmin Connect Web using Import Data page.
Congrats on the finish
Wow this was a really cool file, and hugeeee!! The battery was almost down to 10% at the end, so lucky it lasted! Also liked the little HR increase crossing the line!
Hey seilogramp when you opened this one did FFRT give a bunch of "Overflow" popup messages? Just wondering whether that's the file itself, or if it's my FFRT setup / potato laptop running out of memory.
"Overflow" popup messages?
Yes, it's the file. It's a standard Microsoft Access database error. Happens sometimes when importing corrupted fit files. My understanding is that it could mean that the size of a numeric value that is being imported into a table is too large for the field type. If there aren't too many of these, the activity can be repaired regardless of the errors.