Postgresql 8.3 problem reinnstalling

[lafuente]

Hi.
I have been searching all around pt-forums and the web and cannot seem to solve this problem.
I reinstalled postgresql and it seem to be working fine. But when I try to open PT3 and i get to the "configure PostgreSQL Server" tab and try to connect with default settings, i get the "unable to connect to this database. Please check the configuration". I am almost certain that i used default settings when i installed.

How to fix PT wizards?

[WhiteRider]

Click Start (on XP click Run) and type 'services.msc'.
Do you see PostgreSQL in the list? Is it started? Can you start it?

Did you uninstall PostgreSQL before you re-installed?
If so, did you fully uninstall it as described here?

[lafuente]

Yes, i checked the "services.msc" and postgreSQL is set to "automatic" and runs smoothly when starting.
That's the guide I followed but still it didn't work.

Maybe I changed the default password to something other than "dbpass"? I highly doubt it, but is there somewhere to reset/recover database password?

[WhiteRider]

You can remove the need for PostgreSQL passwords by following this tutorial: How To: Remove PostgreSQL Password.

[lafuente]

Thanks for the prompt answers.
Still no luck. Did as instructed, but still get the "unable to connect to this database. Please check the configuration".
Is there any log or configuration file I can add/view to give you additional information? Anything else I can do?

[kraada]

Just to confirm: in services.msc PostgreSQL is started?

If so, then please restart PT3 with the Logging Enabled link on your start menu, reproduce and report the problem and your log file will help us figure out exactly what is going wrong here for you.

[lafuente]

Yes, postgresql is set to "automatic" and working when started.

I get no further with the "logging enabled" link. Where do I find the log files, so I can manually upload them to support?

[kraada]

They're in the C:\Program Files (x86)\PokerTracker folder - it's a text file called PokerTracker.log (if you have extensions turned off it'll just say PokerTracker).

[lafuente]

It doesn't seem to give very detailed information or information to where the problem lies, at least to me.

2013/03/04 14:58:23.658: [- Main -][System] PokerTracker v3.14.2
2013/03/04 14:58:23.698: [- Main -][SystemInfo] OS: Windows NT 6.1 (build 7601, Service Pack 1)
2013/03/04 14:58:23.714: [- Main -][SystemInfo] Windows Version: 6.1 build 7601 (platform 2) Service Pack 1
2013/03/04 14:58:24.056: [- Main -][SystemInfo] Adobe Flash: 11.6.602.171 Plugin: 11.6.602.171 AIR: Error: Adobe AIR not installed
2013/03/04 14:58:24.115: [- Main -][SystemInfo] Configuration: [WindowInfo]\n\n\n[General]\nLogging=N\nBuildDate=2013/02/26\nRegistrationCode=*** REG CODE REMOVED ***\n\n\n[Import]\nBeepOnCompletion=Y\nClusterOnCompletion=Y\nVacuumOnCompletion=Y\nAnalyzeOnCompletion=Y\nUpCacheOnCompletion=Y\n\n\n\n[Database]\nDefault.Postgres.Port=0\n\n\n[ReportInfo]\n\n\n[HandReplayer]\n\n
2013/03/04 14:58:24.303: [- Main -][System] Attempting to connect to: https://www.ptrackupdate.com/regcheck.php
2013/03/04 14:58:24.338: [- Main -][wxThreadedRead] Starting read thread ...
2013/03/04 14:58:24.358: [000020E0][ConnectorReadThread] Thread [0x000020E0]: Begin
2013/03/04 14:58:24.380: [000020E0][ConnectorReadThread::Entry] Beginning thread.
2013/03/04 14:58:24.408: [000020E0][ConnectorReadThread] Creating socket...
2013/03/04 14:58:24.430: [000020E0][ConnectorReadThread] DNS lookup...
2013/03/04 14:58:24.509: [000020E0][ConnectorReadThread] Socket connect...
2013/03/04 14:58:25.454: [000020E0][ConnectorReadThread] Sending request...
2013/03/04 14:58:25.873: [000020E0][ConnectorReadThread] Reading response...
2013/03/04 14:58:25.916: [000020E0][ConnectorReadThread] Read complete.
2013/03/04 14:58:25.936: [000020E0][ConnectorReadThread] Returning.
2013/03/04 14:58:26.108: [- Main -][wxThreadedRead] Getting data ...
2013/03/04 14:58:26.131: [- Main -][Registration] License written to ...../PokerTracker.lic
2013/03/04 14:58:26.157: [- Main -][System] Registered: true
2013/03/04 14:58:26.178: [- Main -][System] HelpMessages v1.01 is up to date.
2013/03/04 14:58:26.197: [- Main -][System] FullTilt v1.17 is up to date.
2013/03/04 14:58:26.229: [- Main -][System] 888 v1.1 is up to date.
2013/03/04 14:58:26.255: [- Main -][System] Currencies v1.04 is up to date.
2013/03/04 14:58:26.332: [- Main -][System] TournamentDetect v2.71 is up to date.
2013/03/04 14:58:26.407: [- Main -][System] TRP Status: TH: false; TO: false; RH: true; RO: false; PH: true; PO: false;
2013/03/04 14:58:29.233: [- Main -][WindowSplash] Beginning load process
2013/03/04 14:58:31.536: [- Main -][PostgresConnection] Connecting to database: postgres
2013/03/04 14:58:31.665: [- Main -][PostgresConnection (Error)] Unable to login to database (postgres). Reason: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.
2013/03/04 14:58:31.721: [- Main -][PostgresConnection] Connecting to database: template1
2013/03/04 14:58:31.852: [- Main -][PostgresConnection (Error)] Unable to login to database (template1). Reason: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.
2013/03/04 14:58:35.664: [- Main -][PostgresConnection] Connecting to database: postgres
2013/03/04 14:58:35.764: [- Main -][PostgresConnection (Error)] Unable to login to database (postgres). Reason: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.
2013/03/04 14:58:35.783: [- Main -][PostgresConnection] Connecting to database: template1
2013/03/04 14:58:35.880: [- Main -][PostgresConnection (Error)] Unable to login to database (template1). Reason: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.

[kraada]

When you see these things as much as we do that does give you some clues - in particular, we know that the connection was interrupted and it wasn't from a bad password. I'd recommend taking a look at your firewall settings and making sure that PostgreSQL is allowed full access. Our guide to setting up most common firewall and antivirus software is available here.