Our QA/Testing Manager is reviewing these logs/issues this week. For now, you can use the following instructions to rollback to the previous build, but it will require creating a new database that you will have to use in that version as the schema changed when we added Party parsing support for downloaded hands.

Please close HM3 (if it is actually running) and the HM3 Server and rename the database file - C:\Users\{UserName}\Documents\Holdem Manager 3\Databases\{DatabaseName}.hmdb - to a different name. If you can't see it, turn off the windows option that is hiding that directory. http://faq.holdemmanager.com/questio...es+in+Windows+

Rollback to 3.1.3.0 from this link - https://www.holdemmanager.com/downlo...ersion=3.1.3.0

Now when you start HM3 again it will start the setup wizard so you can create a new database.

Please do not create your HM3 Database in a sub-folder of any cloud file hosting service (Dropbox, OneDrive, Google Drive, etc) as it can cause database corruptions because it will constantly be syncing the database to the cloud while you are playing/importing. You can configure HM3 to archive any auto imported hand history files to a cloud file hosting service folder if you choose to as that will not affect the SQLite database in any way, and you can obviously store any HM3 database backup files you create in a cloud folder instead of the default path HM3 suggests when backing up databases.

Then you can manually import your recent hands from the C:HM3Archive and/or C:\HMArchive folders until we can see what is happening and release a fix so that you can update and then use the previous database again.