Related

Basecamp Database crashes upon exit and won't restore backups,

kweagle

I am trying to create a database of ATV Trails where trail is its own GPX file.  I have a couple hundred trails am am using lists to sort different types.   Every time I close basecamp i get an error, and all my data is lost when i reopen it.  i have tried making a backup before closing, but basecamp crashes every time i try to restore the backup.  the only way i have been able to save my progress is by exporting all my tracks in a GPX format or transferring them to my device before closing basecamp.  by doing this i lose all my lists though.  I have uninstalled and reinstalled to no effect.  i have tried restoring the backup on a different computer and it will not restore there either.  i have tried this several times and get the same result.  Any help would be appreciated.

  • 0

    I take it when you say uninstall and reinstall that's BaseCamp you're doing it to? Have you tried just trying with one track? Please report back with what happens when you do that.

  • 0

    I sounds like something is preventing writing to a database file which are AllData.gbd and FolderData.gfi located by default in "C:\Users\<computer user>\AppData\Roaming\Garmin\BaseCamp\Database\4.7" but can be anywhere as specified in general options.  An unknown to me is whether Basecamp stores data in a temporary location during a session then writes it to the database files on close but if it does, that would explain the loss of data at close.  Potential issues that come to mind are inadequate file permissions, syncing (eg: OneDrive or similar), inadequate storage space.

    What is the error message?

  • 0 in reply to Peobody

    After a ton of trial and error, I found the problem was with a couple specific .GPX files in the database.  For whatever reason, those files would corrupt the database when saved and it made it unrecoverable.  Funny that they seemed to work fine in base camp until I saved the Database. 

  • 0 in reply to kweagle

    GPX files are not stored in the database.  All data is stored in a file named AllData.gdb and folder info is stored in FolderData.gfi.  Assuming ".GPX files" means "routes", can you provide any information that would help someone experiencing this crash issue to identify the problem data and the steps required to fix it? (eg: How did you identify the problem data?  Did you delete a specific route, or the contents of an entire list?)

  • 0 in reply to Peobody

    So I am creating a new database of all our local atv trails.  I have been making and collecting .GPX routes from my Garmin 66i and from other users.  I would import all the files I had into basecamp, edit everything to my liking, and the backup the database.  The backup process gave no errors.  When I exit basecamp, I would get an error.  Next time I open it, my database and all tracks are gone.  I tried to load my backup and it would say it was damaged and to try and fix it.  When I say yes the only thing that was recovered was my Birdseye imagery.  No tracks or folders from the database I had created.  

    I did this multiple times and continues to have the same problem.  It was after a few attempts I took more notice of the error when closing basecamp.  

    To troubleshoot, I started importing only a few GPX tracks at a time, backup the data base, then exit.  It began to exit with no errors.  I continued to do this until I got an error when exiting again. It turned out it was a few specific . GPX tracks that would cause the problems.  If i did not import them, I would not have any issues when exiting.  There were about 5 of these tracks in total.  There did not appear to be any issues upon importing these tracks, so not sure why basecamp did not like them.  But everything worked normal if I didn't import them.  

  • 0

    Database crash on exit combined with backup restore failure is a frustrating combination because the backup is supposed to be the safety net for exactly this situation. One thing worth trying is locating the BaseCamp data folder manually and checking whether the database file itself is corrupted or just the index that points to it because sometimes the underlying data is intact even when BaseCamp cannot read it through normal restore. Also worth checking whether antivirus software is interfering with the database write process on exit since some security suites lock files mid-write which causes incomplete saves that corrupt the database silently. Did the crashes start after a specific BaseCamp update or Windows update? 

  • 0 in reply to kweagle
    kweagle said:
    It turned out it was a few specific . GPX tracks that would cause the problems. 

    Garmin is very strict about the proper formatting of gpx files.  This goes as far as the proper order of information.  An online gpx visualizer/editor might be able to read and then export the file in a proper format.

    It appears the JaVaWa has a tool that will try to correct files that do not follow strict protocol.  Do a search for JaVaWa and look under the Online tools for Converteer.  When you get to the page click on the orange button at the top to upload and repair the file.