Pt3 suddenly doesnt work anymore!

[Kade]

Today i wanted to start Pt3 software i clicked begin autoimport and i got this error:

Some diffrent license_ of those
2011/01/15 18:17:14: Full Tilt: Unable to load hand history file: C:\Program Files (x86)\PokerTracker 3\Processed\License_9_6.txt

I Get this like 100x
2011/01/15 18:17:23: Unable to begin feeder import process. Reason: Unsupported database type: PokerTracker 3 Database ()
2011/01/15 18:17:23: Unable to begin feeder import process. Reason: Unsupported database type: PokerTracker 3 Database ()


And it pops up "The HUD cant connect to the configured databases, please check your settings!"

What is wrong what i have2do to make this work??
Has someone a idea?
What can i do?

[WhiteRider]

Firstly, you should not be importing from the Procesed folder - please check the Full Tilt configuration guide and/or tutorial: Auto Import for how to set up the import.

However, it looks as if the PostgreSQL service is not running correctly. Did you update anything on your computer? Anti-virus or Firewall software can often cause this kind of issue.

Please try a reboot first - that can sometimes allow PostgreSQL to start.
Also check our Firewall Guide as that is often a cause of problems with starting PostgreSQL.

If that doesn't help click Start --> Run, type in "services.msc" (without the quotes) and hit enter. Locate the PostgreSQL service and attempt to start it. If it fails to start, click Start --> Control Panel --> Administrative Tools --> Event Viewer and click on Application in the top left pane. Look for an error in the top middle pane relating to PostgreSQL. Double click it to bring up the error message and paste or type it into a Support ticket and that will give us more detail as to what's keeping PostgreSQL from running.

[stream182]

Kade, I've got the same problem. Try to do the following things from the Database Housekeeping section:
1. Cluster
2. Rebuild Cache
3. Reindex

It took several hours on my computers, but now HUD works fine!

Good luck!

[kraada]

Of that list, I'd try them in reverse order and test after each one - it's most likely that reindex fixed the problem, then rebuilding the cache. It's least likely that clustering fixed it - though still possible - but since it takes so long it's probably better to make sure there's still a problem before going that route.