PostgreSQL 8.3.4 problems with pgAdmin + upgrade; Vista

[PeteX]

Weird problems:
- My PostgreSQL 8.3.4 works ok with PT3, I can create new databases and connect to my existing databases. So, my username & password are correct.
- But when I try to connect to the postgresql-server with pgAdmin III, it can't connect to it. Just asks the password from me and says that the connection failed. I have not touched my PostgreSQL installation for quite a while and pgAdmin III did work just fine before. I have done quite a lot of PT3-database query development with pgAdmin III and it hasn't given any trouble to me before. Last time I used it must have been maybe couple of months ago.

Ok, I thought that I might as well just upgrade PostgreSQL to 8.3.6 -> Well, I stopped my PostgreSQL service and ran the upgrade-installation from the distribution ZIP-package -> Installation goes almost to the end and when the progress dialog shows the text "Publishing product information", I get an error message dialog: "An error occurred during the installation of assembly 'policy.8.0.VC80.CRT.publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",version="8.0.50727.762",processorArchitectureo="x86". Please refer to Help and Support for more information." and the installation rolls back.

I have initially installed PT3 without PostgreSQL and have installed PostgreSQL separately from its site.

I have Vista Home Premium and have the UAC in silent mode with the TweakUAC.

I don't have any need to upgrade the PostgreSQL from 8.3.4, but it would be nice to have the pgAdmin III working so that I could do some SQL-query testing on PT3-database.

Any ideas?

[PeteX]

To continue a bit:

pgAdmin III gives the "Guru"-dialog with this info: "could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 5432? "

Ok, I can understand what could be the issue there, BUT if the server really wasn't running on that port, how would PT3 be able to work and connect to the database?!? And it does work just fine.

The only changes that have happened to my system that I can think of could have some significance since pgAdmin III last worked were some automatic Vista updates + some several Avast updates. But why would those break pgAdmin III and not PT3? And also my own code using .NET PostgreSQL connector works ok, I can connect to the database and query data.

[kraada]

That's definitely very odd. The settings that PT3 uses to connect can be found in the C:\Program Files\PokerTracker 3\Data\Config\Pokertracker.cfg file in the [Databases] section. If you're running on an alternate port, you should see that there.

Could you try connecting via Start --> Programs --> PostgreSQL --> psql to 'postgres' and see if that works?

[PeteX]

That's definitely very odd. The settings that PT3 uses to connect can be found in the C:\Program Files\PokerTracker 3\Data\Config\Pokertracker.cfg file in the [Databases] section. If you're running on an alternate port, you should see that there.

Could you try connecting via Start --> Programs --> PostgreSQL --> psql to 'postgres' and see if that works?

Yep, psql works very well. It's just pgAdmin III that doesn't seem to work. I'm running version 1.8.4 that came included with the PostgreSQL 8.3.4 distribution. And I remind: it did work fine before and AFAIK I haven't done any changes to configurations.

And I'm definitely not running an alternate port, 5432 is the default that I'm using in pgAdmin and in PT3.

Here some output from psql:

Code: Select all

C:\Program Files\PostgreSQL\8.3\bin>psql postgres postgres
Welcome to psql 8.3.4, the PostgreSQL interactive terminal.
....
postgres=# select * from holdem_limit;
 id_limit |    limit_name    | amt_sb | amt_bb | flg_nlpl | val_nlpl_mult
----------+------------------+--------+--------+----------+---------------
        1 | $0.02/$0.04      |   0.02 |   0.04 | f        |             1
        2 | $0.05/$0.10      |   0.05 |   0.10 | f        |             1
        3 | $0.10/$0.20      |   0.10 |   0.20 | f        |             1
        4 | $0.25/$0.50      |   0.25 |   0.50 | f        |             1
        5 | $0.50/$1         |   0.50 |   1.00 | f        |             1
        6 | $1/$2            |   1.00 |   2.00 | f        |             1
        7 | $2/$4            |   2.00 |   4.00 | f        |             1
        8 | $3/$6            |   3.00 |   6.00 | f        |             1
        9 | $5/$10           |   5.00 |  10.00 | f        |             1
       10 | $0.02 NL         |   0.00 |   0.02 | t        |             2
       11 | $0.10 NL         |   0.00 |   0.10 | t        |             2
       12 | $0.50 NL         |   0.00 |   0.50 | t        |             2
       13 | $1 NL            |   0.00 |   1.00 | t        |             2
       14 | $0.50 NL (6 max) |   0.00 |   0.50 | t        |             2
       15 | $0.30 NL         |   0.00 |   0.30 | t        |             2
       16 | $1/$2 (2 max)    |   1.00 |   2.00 | f        |             1
       17 | $0.02 NL (6 max) |   1.00 |   0.02 | t        |             2
       18 | $1 NL (6 max)    |   1.00 |   1.00 | t        |             2
(18 rows)

postgres=#

[pokerrow]

The exact same thing happened to me today. All of a sudden SpadeEye stopped working, and I found that I could not connect through pgAdmin, either.

Since installing PT3 pre-GA, I've never had a PostgreSQL problem. I took the default install. PT3 works fine (seemingly), including HUD when playing on FT.

[PeteX]

The exact same thing happened to me today. All of a sudden SpadeEye stopped working, and I found that I could not connect through pgAdmin, either.

Phew, so I'm not going insane after all; because that's what it sort of started to feel like...

Couple of questions:
- Do you use Vista?
- Do you use avast! antivirus software?
- Did you do any windows updates lately?

Just to see if we have any similarities. Those are the only things that I can think of that could have caused this issue. But I'm utterly confused how PT3 is able to connect to the database when pgAdmin is not. I even turned off the windows firewall and tried pgAdmin then, but no help there, still couldn't connect (and I don't see why that would even make a difference considering that PT3 connects, but one has to try every possible fix...).

[kraada]

Well if you can connect in that fashion, the postgres database is definitely running.

Do you have a firewall installed? Could it possibly be configured to block outgoing access to PGAdminIII? That might cause this sort of result.

[pokerrow]

@PeteX: Yep, Vista, but not Windows updates since 3/11 (since which time I'd played, and Spade Eye was able to connect). I use McAfee antivirus, no firewall. I killed McAfee to see if it that would help, but it didn't. And everything was working welll alongside McAfee anyway.

I agree, it's pretty baffling that PT3 can connect without any problem, while pgAdmin cannot.

[PeteX]

Well if you can connect in that fashion, the postgres database is definitely running.

Do you have a firewall installed? Could it possibly be configured to block outgoing access to PGAdminIII? That might cause this sort of result.

Yes, it definitely must be running considering that my own C# code can connect to the PT3 database and query data programmatically. And obv PT3 is working quite well also and getting data from the database.

I don't have any other firewall software (I trust mostly to the SPI fw built-in to my Buffalo router box) installed besides the Vista built-in one. I did try to run pgAdmin with the Vista firewall disabled as I suspected that it might be one reason, but that didn't help, still couldn't connect to the database.

[kraada]

I'm not sure, but you might consider looking for help on the PGAdmin support site as they're probably better equipped to figure out what's going on.