HUD / auto-import not working with Party tourneys

[Russelldust]

PokerTracker 4 does not appear to be auto-importing my Party/bwin hand histories (and consequently the HUD is not working). I have updated to PT v4.11.10, but still the same problem.

Here's what happens when I start importing:

Code: Select all

06:29:14 pm: Full Tilt: Starting auto-import.
06:29:14 pm: Full Tilt: Monitoring tables for Rush Poker.
06:29:14 pm: partypoker: Starting auto-import.
06:29:14 pm: Full Tilt: Found 2 files to monitor.
06:29:14 pm: Full Tilt: Loading hand history file: C:\Users\MYNAME\Documents\HandHistory\FullTiltPoker\...\FT20140725 Big Little Tournament (Day 1f) (270421842), Entry 1 - NL Hold'em.txt
06:29:14 pm: Full Tilt: Loading hand history file: C:\Users\MYNAME\Documents\HandHistory\FullTiltPoker\...\FT20140725 Big Little Tournament (Day 1f) - (270421842) - Summary.txt

So it can see my Full Tilt HH files ok, but it's not importing anything from my Party HH folders.

I've double-checked my Import Configuration for PartyPoker...

[ x ] "Get hands from site while playing" is checked.

Directories configuration reads:
C:\Programs\Poker\PartyGaming\PartyPoker\HandHistory
C:\Programs\bwincom\bwincomPoker\HandHistory

I've verified that HH files are being generated, for example there are new HH files here:
C:\Programs\Poker\PartyGaming\PartyPoker\HandHistory\MY_PARTY_SCREEN_NAME\20140726
C:\Programs\bwincom\bwincomPoker\HandHistory\MY_BWIN_SCREEN_NAME\20140726

Please help me get my HUD working!

[Russelldust]

I meant to add...
When I click "Stop Getting Hands", PT4 freezes indefinitely. (The three buttons, "Stop Getting Hands" etc, stay greyed out.)

I have been resorting to forcing PT4 to shut down, using the Task Manager.

[xcbrx]

i have similliar issues, import is like 1h per 30minutes and not quitable. to me it seems like the new release fucked up big time, but OP says his issue started out with the latter one.
HUDs obv. not working, too.
one cant explain how useless pt4 is to me and OP right now..... lol.

[kraada]

Please restart PT4 using the logging enabled link on your Start Menu, reproduce this problem and then report it via our support system with the log file - that will help us figure out what is going on here and get it fixed for you. You can find that file by clicking File --> Show User Data Folder in the main PT4 window - the file we need is the text file called PokerTracker4 that is in that folder.

[xcbrx]

in the meantime i tried to run a full cashe rebuild since i wanted to give it a try but i got this error after hours (17GB DB):
http://i.imgur.com/DnGVslG.png
though it seems my mashine is limitet i did do cashe rebuilds in the past so i cant see why me is the problem here. although i do have a few ES HUDs implemented in pt4 (only the free ones, no heat maps which use lots of collums at all). do you think removing those HUDs would help being able to rebuild the cache?

maybe its better to log that failing cache rebuild (does it get logged at all?), what do you think?

[WhiteRider]

in the meantime i tried to run a full cashe rebuild since i wanted to give it a try but i got this error after hours (17GB DB):
http://i.imgur.com/DnGVslG.png
though it seems my mashine is limitet i did do cashe rebuilds in the past so i cant see why me is the problem here. although i do have a few ES HUDs implemented in <span title="pt4" name="vocabhighlighterpt4" id="vocabhighlighter141" class="vh2-PT4">pt4</span> (only the free ones, no heat maps which use lots of collums at all). do you think removing those HUDs would help being able to rebuild the cache?

maybe its better to log that failing cache rebuild (does it get logged at all?), what do you think?

Firstly you have a very old version of PostgreSQL 8.4 (8.4.7) so you should update to the latest 8.4 version (8.4.22). The Directions here refer to 8.3 but the process is the same for 8.4.

Once you've done that update to v4.11.10 if you haven't already (PT4 Download Page) and run PT4. In Database > Database Management click Housekeeping > Revert PostgreSQL Tuning then Tune PostgreSQL and try the cache rebuild again.

If you continue to have problems please open a Support Ticket and report your problem so that we can work with you directly.