Port 5432 Database Problem
Posted: Fri Jun 06, 2008 11:00 pm
In pokertracker one day (the June 1, 2008 verson), when i started it up, i got this error that said, "Unable to login to database (PT3 DB). Reason: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" and accepting TCP/IP connections on port 5432?"
So, like suggested by various people, I uninstalled postgresql, did the delete thing in command prompt, and reinstalled it all over again. Then I manually imported all my hand histories from a zip file that I keep just incase of sh*t happening like this, and then 30 minutes later, everything was all good. I started playing at the tables, doing my thing, multi-tabling, and then about 30 minutes later my pokertracker shuts down randomly, and i get some force shutdown error. I go okay, I'll just go restart the program, but when I open up Pokertracker once again, I get the same error, "Unable to login to database (PT3 DB). Reason: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" and accepting TCP/IP connections on port 5432?"
This time, I uninstall everything, Pokertracker 3, postgresql, delete all my data, do the delete user in command prompt thing, and I go download an older version of Pokertracker (the May 16th, 2008 verson), then install everything, including postresql and my hand histories. (I also had to reregister the program with my code). Okay, everything is all good once again, so I go play on pokerstars, and everything works nice. I play for about 8 hours and get in a good session.
The next day, I start up Pokertracker 3, and there and behold, I get the error, "Unable to login to database (PT3 DB). Reason: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" and accepting TCP/IP connections on port 5432?" once again..
Somebody please help me, I am getting really irritated, and in all honesty, I'm going to keep this bumped to the top in the troubleshooting and postresql forums until this problem is fixed. And I don't think this is being selfish as there are many other people experiencing the same problem, all who have also payed good money for this software. I hope I do not have to uninstall and reinstall everything every single day.. (I already spent like 5 hours yesterday troubleshooting this problem).
So, like suggested by various people, I uninstalled postgresql, did the delete thing in command prompt, and reinstalled it all over again. Then I manually imported all my hand histories from a zip file that I keep just incase of sh*t happening like this, and then 30 minutes later, everything was all good. I started playing at the tables, doing my thing, multi-tabling, and then about 30 minutes later my pokertracker shuts down randomly, and i get some force shutdown error. I go okay, I'll just go restart the program, but when I open up Pokertracker once again, I get the same error, "Unable to login to database (PT3 DB). Reason: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" and accepting TCP/IP connections on port 5432?"
This time, I uninstall everything, Pokertracker 3, postgresql, delete all my data, do the delete user in command prompt thing, and I go download an older version of Pokertracker (the May 16th, 2008 verson), then install everything, including postresql and my hand histories. (I also had to reregister the program with my code). Okay, everything is all good once again, so I go play on pokerstars, and everything works nice. I play for about 8 hours and get in a good session.
The next day, I start up Pokertracker 3, and there and behold, I get the error, "Unable to login to database (PT3 DB). Reason: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" and accepting TCP/IP connections on port 5432?" once again..
Somebody please help me, I am getting really irritated, and in all honesty, I'm going to keep this bumped to the top in the troubleshooting and postresql forums until this problem is fixed. And I don't think this is being selfish as there are many other people experiencing the same problem, all who have also payed good money for this software. I hope I do not have to uninstall and reinstall everything every single day.. (I already spent like 5 hours yesterday troubleshooting this problem).