PT4 crash report is failing and program does not run

[d0zer]

Hey,

So PT4 started doing some strange things (HUD double-loading on a table as in it incorrectly displayed stats everywhere) and I wanted to restart PT4. Now when I open it, it starts sending the "crash log", which takes something like 10 minutes for some reason, but once it is "done" and the green bar gets to the end, it just starts the process again. When I cancel it, PT4 starts but then I quickly get the message of "fatal crash has happened and next time you start PT4 you will be asked to send a log" and then when I close that window, PT4 closes as well. So it is a bit of a dead circle.

I am running the latest version, what should I do?

Thanks

[Flag_Hippo]

That sounds like a database issue. Open File Explorer in Windows and copy/paste the following in the address bar and press enter:

%localappdata%\PokerTracker 4\Config\

In the window that appears open the 'PokerTracker.cfg' file with NotePad. Under the 'Database' section you will have something like this:

Code: Select all

[Database]
Default.Postgres.Server=localhost
Default.Postgres.Port=5432
Default.Postgres.User=postgres
Default.Postgres.Password=dbpass
DB1.Name=Database
DB1.Type=postgres
DB1.Postgres.Database=Database
DB1.Postgres.Server=localhost
DB1.Postgres.Port=5432
DB1.Postgres.User=postgres
DB1.Postgres.Password=dbpass
DB1.Default=Y

Delete everything except the default settings so you are left with:

Code: Select all

[Database]
Default.Postgres.Server=localhost
Default.Postgres.Port=5432
Default.Postgres.User=postgres
Default.Postgres.Password=dbpass

and save the change. Restart PokerTracker 4 and it should prompt you to create a new database. Create a new database with a different name from the one you were using. Does that allow PokerTracker 4 to start?

[d0zer]

Yes this seems to have solved the issue, thanks a lot!

[Flag_Hippo]

OK great. If you want to add the original database(s) back to the configuration you can go to "Database -> Database Management -> New -> Browse Databases'. Do not make the database you were having an issue with active as you may run into the same issue again if it is corrupt. If the database isn't large you can try and fix it by running the following in the database management window:

1. Reindex
2. Cluster
3. Vacuum/Analyze

After the housekeeping is complete rebuild the database cache via 'Rebuild Cache -> Full Cache Rebuild'. When that's done you can try making the original database active again.

If you want to keep the new database instead you can delete the original after you have added it back to the configuration if you're sure you don't need anything from it.