PokerTracker

Access violation (0) (Flags: 0; Address 0x00933d1e; EIP : 0x00933D1E


Been getting the above message every time i load up my Pokertracker. I've upgraded to the latest beta but still getting the error message. My hands import but the HUD doesnt load up.

What do I need to do ?

Please enable logging, restart PT3 and next time you see the problem attach your PokerTracker.log file to a support ticket. Attach the crash log file too if one is written (you'll get a message box in that case, telling you where it is).
Thanks.
Tutorial: Submitting a Bug Report

I got similar error message.

I have both 8.3 and 8.4 versions of PostgresSql installed. The problem occured when PT3 connected to my database through 8.3 version. When I changed PT3 to use 8.4 version(different port) the problem disappeared.

Odd; 8.3 shouldn't cause that sort of problem. If you get it again (using 8.3 or 8.4) please report it so that we can investigate the cause and get it fixed.

joonasta wrote:The problem occured when PT3 connected to my database through 8.3 version.

Do you know what revision of 8.3 you are running?

To find out, Click Start --> Programs --> PostgreSQL --> psql to 'postgres'. At the prompt type:
SELECT version();

Versions are:

8.3:
PostgreSQL 8.3.7, compiled by Visual C++ build 1400

8.4:
PostgreSQL 8.4.2, compiled by Visual C++ build 1400, 32-bit

Actually when I got the error PT3 also said that my database was "Invalid" and asked me to activate some other database. That happened during startup of PT3. Then I noticed from 'Database management" window that port defined for the database was postgers 8.3's port. I chaned 8.4's port there and PT3 was able to use the database again.

I am not able to reproduce the situation because for some reason I am not able to edit database configuration settings anymore. The settings are grey in "Configure PostgresSQL Database" window. Is it possible to change those setting only if the database is not working?

The error didn't happen straight away after I upgraded PT3 to version 30.0. I don't remember all things that I did before the error but at least I did these:
- Housekeeping
- Backuped the database. Backuping process jammed and I had to kill PT3 process
- Strated purge for couple of sessions but cancelled it
- Exported hands from couple of sessions
- Tried to backup again but it jammed also this time

If you click New in the Database Management window, then Browse, you should be able to choose other database options; then you can click Browse Databases to find and attach to databases on other ports. Could you give that a try and see if you can reproduce this error?

That doesn't work because the db is in postgres 8.4 server, not in 8.3 server. PT3 doesn't allow me to select existing db and then change port in new database window.

I really don't understand what has happened. I have been using this db for several months and it has been working properly. The db has always been in postgres 8.4 server. I think I tried to restore the db from a backup before the error occured because I thought that I had accidently removed couple of session from the db. The restore failed and then it turned out that those sessions were still in the db. Could it be possible that the port changed during the restore? Postgres 8.3's port is 5432 and 8.4's 5433. The first one is default value for the port so it could make sense that in some certain error situation the restore process accidently changes port to default value?

However, it looks that I am not able reproduce the situation and I don't remember for sure what I did before the error occured. It may be very hard to figure out what happened in this case.