1.06.04RC1 - No more auto-import

[e2e4]

Salut,

i've installed the version above yesterday. Since them there is no more "Auto Import" working. All statistics are the same and no more longer updated.

Client: Vista Ultimate, Partypoker

Any ideas?

Regards.

[morny]

Please answer these questions so i can hlp you http://www.holdemmanager.net/faq/afmviewfaq.aspx?faqid=174

Also please create a new database http://www.holdemmanager.net/faq/afmviewfaq.aspx?faqid=146 and let me know if that works

[e2e4]

The HUD is working and showing me all the statistics on the table.


4) Check to see if the Hand Histories are showing up in the correct folder. Go to Options > Configure Auto Import Folders and check the location of the folder HM checks for the Hand Histories.

I did checked and reconfigure again. Therefore I tried to import a Handhistory manually, but no action! The HHs are in english language.


Also please create a new database

I did and tried to import the Handhistory-folder manually and here it works fine.

[morny]

You are probably best off starting a new database and reimporting. To do this export the hand histories from the old one http://www.holdemmanager.net/faq/afm...aspx?faqid=173 and then create a new database http://www.holdemmanager.net/faq/afm...aspx?faqid=146 and reimport the hands

The 2 most common causes of this problems with corrupt databases are 1) powering off your computer or having your computer lose power while the database is doing something and 2) an old drive with bad sectors on it. Basically what happens is a small portion of a file gets slightly corrupt and then when you reboot and windows goes into that checkdsk procedure it finds the bad section and, thinking it is doing a good thing, removes it. Postgres then loads the table and a portion of it is gone so it doesn’t like that and blocks access to the entire table. Normally when this happens it is on a completely useless file that you'll never even notice is now gone and quite often it will happen to an index in the DB which can easily be rebuilt but in your case it happened to a system table.

So, to protect against this

1) keep you hands histories in case you do need to reimport
2) use a power bar and avoid hard shutdowns (when you flick the power switch on the pc)
3) if your drive is old consider replacing it with a new one. They are cheap and much faster now than even a few years ago.

[e2e4]

You are probably best off starting a new database and reimporting.

I did and it seems to be working fine, thanks!