SQLite Agent Database Engine

Starting with 10.7, the SysTrack agent uses SQLite as its only supported database engine for all supported operating systems.

Q: Why did the SysTrack agent get updated to SQLite?

A: By moving to a more robust and resilient technology, we are able to provide you an even more reliable experience.

Q: What is going to happen?

A: Starting with the 10.7 release, the SysTrack agent will be using SQLite for its database engine. JET databases and Local DB are no longer supported and will be migrated to SQLite. The existing JET or Local DB database will be backed up locally in the agent directory before any conversion takes place. This is an automatic process when the agent is first run.

Q: What do I need to do?

A: Nothing. The conversion process is automatic once you have rolled out the new agent to your environment.

Troubleshooting

Q: What happens if there is a conversion failure?

A: The conversion should not fail. However, if the agent is unable to convert the JET database to SQLite, the agent will attempt the conversion multiple times before it creates a new blank SQLite database. You can use the included SQLite Conversion Status dashboard to track any conversion failures.

If your current JET database is corrupted, a conversion failure may occur. If it does, follow the steps below, or contact technical support for assistance.

  1. Check the MDB folder to make sure it has a LsiDBConv.zip file which should include the original database.

  2. Stop the agent.

  3. If the new SQLite database exists, delete it from the MDB folder.

  4. Copy the original database from the zip file.

  5. Delete the zip file which is recreated the next time the agent runs the conversion.

  6. Delete the registry key:  Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lakeside Software\DBConv

  7. Start the agent.

  8. The agent will try to convert the database

  9. If it succeeds you are done.

    1. If it fails and you see a new SQLite database was created, then the existing JET database is corrupted beyond repair.

    2. If no new SQLite database was created and the old database is still there, contact technical support for assistance.