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

Does Garmin Expression still support Forerunner 301?

Garmin Expression worked fine with my dinosaur Forerunner 301. My last successful sync was on January 20.

I have been trying all kinds of ways to upload new activities to no avail since yesterday.

I have tried restarting Garmin Expression, rebooting my PC, and running GE on both Windows 11 and Windows 10. Nothing works. GE does not show any error messages, and it says the sync works, but no new activities created after January 20 have been uploaded.

The Forerunner 301 works fine, and everything appears normal. I can check its history to see all the activities after January 20. There are about a dozen of them.

Top Replies

FlowState 4 months ago +1

Try opening the Garmin Express logs folder on your Windows PC:

C:\ProgramData\Garmin\Logs\Express

(Here's a related support article, which you don't need to read, but I'm only including for reference…
FlowState 4 months ago +1

"Does Garmin Expression still support Forerunner 301?"

I don't think any non-employees can answer that question for you [*], but according to the Garmin Express (Windows) release notes pinned…
FlowState 4 months ago in reply to zipswich +1

It looks like on January 29 (today), Express found no activities to sync.

However, since you had this problem starting January 20, I would look for entries on that day (search for "2025-01-20"), especially…

All Replies

0 FlowState 4 months ago

Try opening the Garmin Express logs folder on your Windows PC:

C:\ProgramData\Garmin\Logs\Express

(Here's a related support article, which you don't need to read, but I'm only including for reference. It's intended to help you send logs to Product Support, but since apparently no Garmin employee will support FR301, there would likely be no point in sending logs to Garmin. Here I'm suggesting you read the logs yourself to see if you can figure out why syncing is failing.)

Select the file called Express.log, which should be the latest non-detailed log file, and open it in a text editor such as Notepad. For example, the Express logs folder on my PC includes the following files (sorted by newest to oldest):

(I don't use Express very often)

Search the Express.log file for "SyncUploadOperation", "sync", "TCX", "fail" or "error". Do you see any interesting logs relating to a failure to sync TCX files from your Forerunner 301?

For example, I see log entries relating to activity FIT files which failed to upload because they already existed on Connect ("Not uploading file [...] because it was matched by connect") or because they were corrupt ("integrity check failed").

Hopefully your log will have something that sheds some light on the problem.

0 FlowState 4 months ago

"Does Garmin Expression still support Forerunner 301?"

I don't think any non-employees can answer that question for you [*], but according to the Garmin Express (Windows) release notes pinned at the top of this forum:

- the latest version (v7.24.0) was released in November. I can confirm this is the version that is offered to me when I open Garmin Express on my Windows PC (I haven't opened Express in a long time)

- there's nothing in the release notes (going back to 7.15) which mentions anything about dropping support for Forerunner 301 or any other devices

That doesn't rule out something changing in the back end, but again none of us end users could say either way [*]

[*] unless you can find other users who still have a Forerunner 301 and use Express to sync it.

0 FlowState 4 months ago in reply to FlowState

EXPRESSCUSTOMERCARE

0 zipswich 4 months ago in reply to FlowState

Thank you for all the tips.

Here are the contents for a session of Garmin Express:
2025-01-29 18:38:00.1184 | 16 | I | WinDeviceWatcher[E28B] - HandleDeviceArrival \\?\USB#VID_091E&PID_0003#9&28a7f0a1&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2025-01-29 18:38:00.1184 | 16 | I | WinDeviceWatcher[C99F] - HandleDeviceArrival \\?\USB#VID_091E&PID_0003#9&28a7f0a1&0&4#{2c9c45c2-8e7d-4c08-a12d-816bbae722c0}
2025-01-29 18:38:00.1184 | 16 | I | DeviceService[C99F,96DA] - Device Connected (GarminMode) \\?\USB#VID_091E&PID_0003#9&28a7f0a1&0&4#{2c9c45c2-8e7d-4c08-a12d-816bbae722c0}
2025-01-29 18:38:00.1352 | 16 | I | WinDeviceWatcher[C36C] - HandleDeviceArrival \\?\USB#VID_091E&PID_0003#9&28a7f0a1&0&4#{894a7461-a033-11d2-821e-444553540000}
2025-01-29 18:38:10.5132 | 9 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:10.5132 | 23 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:10.5359 | 9 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:10.5490 | 23 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:10.5490 | 9 | I | UpdateService[C99F,96DA] - Skipping software updates for GarminMode
2025-01-29 18:38:10.5616 | 18 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:10.7656 | 47 | I | UpdateService[C99F,96DA] - Skipping software updates for GarminMode
2025-01-29 18:38:10.9015 | 9 | I | SyncService[C99F,96DA] - GarminDevice.xml has not changed for device 3399140076. Not uploading to Connect.
2025-01-29 18:38:10.9015 | 38 | I | UploadUtil[C99F,96DA] - Getting sync upload settings for device 3399140076
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - Looking for files for data type FitnessHistory
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - 0 files found.
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - Looking for files for data type FitnessHistory
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - 0 files found.
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - Looking for files for data type ExpectedSource
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - 0 files found.
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - Looking for files for data type ExpectedSource
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - 0 files found.
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - Looking for files for data type ExpectedSource
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - 0 files found.
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - Looking for files for data type ExpectedSource
2025-01-29 18:38:19.4901 | 9 | I | SyncUploadOperation[C99F,96DA] - 0 files found.
2025-01-29 18:38:19.4901 | 9 | I | OperationQueue[C99F,96DA] - Removing operation Garmin.Omt.Service.Operation.Sync.Upload.SyncUploadOperation from queue.
2025-01-29 18:38:19.4901 | 21 | I | SyncDownloadOperation[C99F,96DA] - No file to sync (download).
2025-01-29 18:38:19.4901 | 21 | I | OperationQueue[C99F,96DA] - Removing operation Garmin.Omt.Service.Operation.Sync.Download.SyncDownloadOperation from queue.
2025-01-29 18:38:19.4901 | 35 | I | SyncUploadOperation[C99F,96DA] - Sync upload Complete for device 3399140076, 0 files uploaded.
2025-01-29 18:38:19.4901 | 35 | I | SyncService[C99F,96DA] - Sync completed successfully.
2025-01-29 18:38:19.4901 | 18 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:20.0684 | 36 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:20.0684 | 23 | I | UpdateService[C99F,96DA] - Skipping software updates for GarminMode
2025-01-29 18:38:20.0684 | 35 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:20.0859 | 18 | I | UpdateService[C99F,96DA] - Skipping software updates for GarminMode
2025-01-29 18:38:20.0859 | 23 | I | DeviceService[C99F,96DA] - No XML repair required
2025-01-29 18:38:20.0859 | 29 | I | UpdateService[C99F,96DA] - Skipping software updates for GarminMode
2025-01-29 18:38:37.4265 | 1 | I | App[] - Client instance launched with command args:
2025-01-29 18:38:58.3271 | 1 | I | SyncService[] - GarminDevice.xml has not changed for device 3399140076. Not uploading to Connect.
2025-01-29 18:38:58.3271 | 21 | I | UploadUtil[] - Getting sync upload settings for device 3399140076
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - Looking for files for data type FitnessHistory
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - 0 files found.
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - Looking for files for data type FitnessHistory
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - 0 files found.
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - Looking for files for data type ExpectedSource
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - 0 files found.
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - Looking for files for data type ExpectedSource
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - 0 files found.
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - Looking for files for data type ExpectedSource
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - 0 files found.
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - Looking for files for data type ExpectedSource
2025-01-29 18:39:06.8328 | 21 | I | SyncUploadOperation[] - 0 files found.
2025-01-29 18:39:06.8328 | 21 | I | OperationQueue[] - Removing operation Garmin.Omt.Service.Operation.Sync.Upload.SyncUploadOperation from queue.
2025-01-29 18:39:06.8328 | 17 | I | SyncDownloadOperation[] - No file to sync (download).
2025-01-29 18:39:06.8328 | 17 | I | OperationQueue[] - Removing operation Garmin.Omt.Service.Operation.Sync.Download.SyncDownloadOperation from queue.
2025-01-29 18:39:06.8328 | 36 | I | SyncUploadOperation[] - Sync upload Complete for device 3399140076, 0 files uploaded.
2025-01-29 18:39:06.8328 | 36 | I | SyncService[] - Sync completed successfully.
2025-01-29 18:39:06.8328 | 21 | I | DeviceService[] - No XML repair required
2025-01-29 18:39:07.4260 | 24 | I | DeviceService[] - No XML repair required
2025-01-29 18:39:07.4320 | 38 | I | UpdateService[] - Skipping software updates for GarminMode
2025-01-29 18:39:07.4320 | 17 | I | DeviceService[] - No XML repair required
2025-01-29 18:39:07.4320 | 9 | I | UpdateService[] - Skipping software updates for GarminMode
2025-01-29 18:39:07.5106 | 24 | I | DeviceService[] - No XML repair required
2025-01-29 18:39:07.5271 | 21 | I | UpdateService[] - Skipping software updates for GarminMode

My non-expert eyes do not see any hints, unfortunately.

0 FlowState 4 months ago in reply to zipswich

It looks like on January 29 (today), Express found no activities to sync.

However, since you had this problem starting January 20, I would look for entries on that day (search for "2025-01-20"), especially entries containing "SyncUploadOperation".

If Express.log has no such entries, then open the next oldest non-detailed log ("Express_00.log"). Then move onto the next log, if necessary ("Express_01.log"). And so on.

You should be able to get a good idea of which file to open by looking at the Date Modified and Date Created columns in File Explorer. Date Created should be January 20 (or earlier) and Date Modified should be January 20 (or later).

If there are no problems on January 20, then move onto January 21 (and so on).

I will also say that my logs (for a Forerunner 955 which uses FIT files) include lines like this:

SyncUploadOperation ... Looking for files for data type FIT_TYPE_4
SyncUploadOperation ... 194 files found

Since your FR301 does not use FIT files, I would not expect log entries that look like that (and indeed they don't appear in the text you pasted).

I also see "expectedsource" lines as you do (and 0 files are found).

What I don't see in my logs are lines including "FitnessHistory" (as you do):

"SyncUploadOperation - Looking for files for data type FitnessHistory"

So perhaps those are the log entries you are looking for (around January 20).

0 FlowState 4 months ago in reply to FlowState

I would also make a backup of the logs folder, just in case some of these files with relevant errors go away. Very unlikely in the near future, but It does seem that Garmin only keeps up to 15 backups of each kind of log (including the current log).

0 FlowState 4 months ago in reply to FlowState

e.g. This is the complete list of files in my Express log folder (15 of each type):

0 zipswich 4 months ago in reply to FlowState

Here is what I did:

I did a sync on Jan 21. I kept using the 301 but never did any sync until today. This exactly what the logs show:

File Express_11.log shows successful sync:

2025-01-21 02:19:05.2728 | 34 | I | SyncUploadOperation[F5B3,0A0F] - Looking for files for data type FitnessHistory
2025-01-21 02:19:05.2728 | 34 | I | SyncUploadOperation[F5B3,0A0F] - 40 files found.
2025-01-21 02:19:05.2728 | 34 | I | SyncUploadOperation[F5B3,0A0F] - Looking for files for data type FitnessHistory
2025-01-21 02:19:05.2728 | 34 | I | SyncUploadOperation[F5B3,0A0F] - 0 files found.
2025-01-21 02:19:05.2728 | 34 | I | SyncUploadOperation[F5B3,0A0F] - Looking for files for data type ExpectedSource
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - 0 files found.
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - Looking for files for data type ExpectedSource
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - 0 files found.
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - Looking for files for data type ExpectedSource
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - 0 files found.
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - Looking for files for data type ExpectedSource
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - 0 files found.
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-01-000628.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-01-095332.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-02-203505.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-03-103613.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-04-102936.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-07-105320.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-08-110839.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-09-210153.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-11-154456.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-16-202600.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-17-201957.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-20-145706.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-20-145736.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-25-105800.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-26-110036.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-27-111439.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-29-144623.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-29-144656.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-11-29-192434.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-06-111244.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-17-105240.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-21-195411.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-23-193318.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-24-163453.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-25-142128.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-26-141752.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-26-143236.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File 2024-12-27-151825.TCX has already been uploaded, skipping upload to Connect
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2024-12-28-135546.TCX -> 2024-12-28-135546.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2024-12-31-231948.TCX -> 2024-12-31-231948.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-05-153348.TCX -> 2025-01-05-153348.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-06-135324.TCX -> 2025-01-06-135324.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-06-160610.TCX -> 2025-01-06-160610.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-06-202453.TCX -> 2025-01-06-202453.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-12-145417.TCX -> 2025-01-12-145417.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-12-153152.TCX -> 2025-01-12-153152.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-12-163938.TCX -> 2025-01-12-163938.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-13-154517.TCX -> 2025-01-13-154517.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-13-220251.TCX -> 2025-01-13-220251.TCX (type FitnessHistory)
2025-01-21 02:19:05.2888 | 34 | I | SyncUploadOperation[F5B3,0A0F] - File to transfer 2025-01-20-201314.TCX -> 2025-01-20-201314.TCX (type FitnessHistory)
2025-01-21 02:19:05.4948 | 25 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2024-12-28-135546.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:05.4948 | 25 | I | OperationQueue[F5B3,0A0F] - Removing operation Garmin.Omt.Service.Operation.Sync.Upload.SyncUploadOperation from queue.
2025-01-21 02:19:05.4948 | 9 | I | SyncDownloadOperation[F5B3,0A0F] - No file to sync (download).
2025-01-21 02:19:05.5094 | 9 | I | OperationQueue[F5B3,0A0F] - Removing operation Garmin.Omt.Service.Operation.Sync.Download.SyncDownloadOperation from queue.
2025-01-21 02:19:05.8111 | 41 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:05.8111 | 41 | I | SyncUploadOperation[F5B3,0A0F] - The file[2024-12-28-135546.TCX] was processed successfully with code: 202
2025-01-21 02:19:05.8111 | 41 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2024-12-28-135546.TCX to upload records.
2025-01-21 02:19:05.8111 | 41 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2024-12-31-231948.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:06.0501 | 25 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:06.0501 | 25 | I | SyncUploadOperation[F5B3,0A0F] - The file[2024-12-31-231948.TCX] was processed successfully with code: 202
2025-01-21 02:19:06.0501 | 25 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2024-12-31-231948.TCX to upload records.
2025-01-21 02:19:06.0501 | 25 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-05-153348.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:06.7421 | 25 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:06.7421 | 25 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-05-153348.TCX] was processed successfully with code: 202
2025-01-21 02:19:06.7421 | 25 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-05-153348.TCX to upload records.
2025-01-21 02:19:06.7421 | 25 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-06-135324.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:06.9296 | 25 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:06.9296 | 25 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-06-135324.TCX] was processed successfully with code: 202
2025-01-21 02:19:06.9296 | 25 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-06-135324.TCX to upload records.
2025-01-21 02:19:06.9296 | 25 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-06-160610.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:07.1952 | 25 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:07.1952 | 25 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-06-160610.TCX] was processed successfully with code: 202
2025-01-21 02:19:07.1952 | 25 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-06-160610.TCX to upload records.
2025-01-21 02:19:07.1952 | 25 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-06-202453.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:07.5332 | 25 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:07.5332 | 25 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-06-202453.TCX] was processed successfully with code: 202
2025-01-21 02:19:07.5332 | 25 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-06-202453.TCX to upload records.
2025-01-21 02:19:07.5332 | 25 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-12-145417.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:07.7222 | 41 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:07.7222 | 41 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-12-145417.TCX] was processed successfully with code: 202
2025-01-21 02:19:07.7222 | 41 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-12-145417.TCX to upload records.
2025-01-21 02:19:07.7222 | 41 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-12-153152.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:08.0573 | 41 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:08.0573 | 41 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-12-153152.TCX] was processed successfully with code: 202
2025-01-21 02:19:08.0573 | 41 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-12-153152.TCX to upload records.
2025-01-21 02:19:08.0573 | 41 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-12-163938.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:08.3363 | 41 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:08.3363 | 41 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-12-163938.TCX] was processed successfully with code: 202
2025-01-21 02:19:08.3363 | 41 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-12-163938.TCX to upload records.
2025-01-21 02:19:08.3363 | 41 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-13-154517.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:08.6318 | 6 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:08.6318 | 6 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-13-154517.TCX] was processed successfully with code: 202
2025-01-21 02:19:08.6318 | 6 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-13-154517.TCX to upload records.
2025-01-21 02:19:08.6318 | 6 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-13-220251.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:08.7898 | 6 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:08.7898 | 6 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-13-220251.TCX] was processed successfully with code: 202
2025-01-21 02:19:08.7898 | 6 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-13-220251.TCX to upload records.
2025-01-21 02:19:08.7898 | 6 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-20-201314.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:09.1254 | 6 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:09.1254 | 6 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-20-201314.TCX] was processed successfully with code: 202
2025-01-21 02:19:09.1254 | 6 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-20-201314.TCX to upload records.
2025-01-21 02:19:10.2595 | 33 | I | SyncUploadOperation[F5B3,0A0F] - Sync upload Complete for device 3399140076, 12 files uploaded.
2025-01-21 02:19:10.2725 | 32 | I | SyncService[F5B3,0A0F] - Sync completed successfully.

The next log file with syn activities is Express_02.log, which was created today. It found no files to sync, as shown by entries in one of my previous posts.

0 FlowState 4 months ago in reply to zipswich

And you’re sure that all of those files (e.g. the files from 2025-01-13 and 2025-01-20) were uploaded successfully? The log messages are interesting:

e.g.

2025-01-21 02:19:08.6318 | 6 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-13-220251.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:08.7898 | 6 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:08.7898 | 6 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-13-220251.TCX] was processed successfully with code: 202
2025-01-21 02:19:08.7898 | 6 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-13-220251.TCX to upload records.
2025-01-21 02:19:08.7898 | 6 | I | SyncUploadOperation[F5B3,0A0F] - Uploading C:\ProgramData\Garmin\CoreService\Devices\3399140076\Sync\FitnessHistory\2025-01-20-201314.TCX to connectapi.garmin.com/.../upload
2025-01-21 02:19:09.1254 | 6 | W | FileIdParser[F5B3,0A0F] - FIT File Integrity Check Failed
2025-01-21 02:19:09.1254 | 6 | I | SyncUploadOperation[F5B3,0A0F] - The file[2025-01-20-201314.TCX] was processed successfully with code: 202
2025-01-21 02:19:09.1254 | 6 | D | SyncUploadOperation[F5B3,0A0F] - Adding file 2025-01-20-201314.TCX to upload records.
2025-01-21 02:19:10.2595 | 33 | I | SyncUploadOperation[F5B3,0A0F] - Sync upload Complete for device 3399140076, 12 files uploaded.

It looks like the backend tries to parse each uploaded file as a FIT file, but fails to do so (because ofc the files are actually TCX files). Then the log says the upload was successful anyway. This could just be a quirk where the backend always tries to parse every uploaded file as a FIT file no matter what the extension is. (You can definitely manually upload a FIT file whose extension is renamed to “GPX” — this is actually a workaround for an iphone/ipad bug where FIT files aren’t selectable when you try to upload a file).

If you look at earlier syncs (like from Express_13.log), do you see something similar (“FIT File integrity check failed”)? I’m guessing you will but just double checking.

BTW I would def make a backup copy of all the logs, as you use Express so frequently that your earliest log file was modified two weeks ago.

The next log file with syn activities is Express_02.log, which was created today. It found no files to sync, as shown by entries in one of my previous posts.

If you can’t find anything interesting in the in-between logs (Express_03 to Express_10.log), then I guess the only options are to:

- either contact product support (but Forerunner 301 is out of support, so they won’t help you)

- take my earlier suggestion to use Training Center to export TCX activity files from your watch and use the Connect website to manually upload them. Maybe the process of using Training Center to grab files off your device will also coincidentally fix whatever problem you’re having with Express (assuming Express / the Connect API haven’t actually changed to drop support for FR301)

0 zipswich 4 months ago in reply to FlowState

I never connected my 301 to the PC between Jan 20 and Jan 29 though I used it every day during this period.

I have Backblaze to back up all my files (about 1 TB) to the cloud daily, so I can restore any file if it disappears somehow.

Yes, all activities before Jan 21 were uploaded successfully.

I will start using my Forerunner 10 tomorrow after it has been sealed for over 10 years.

If this issue cannot be resolved by Garmin, I will use the Training Center to get the new activities out and say goodbye to 301.