Unable to connect to database

[elcal06]

I just purchased Pokertracker3 and I am having this message as well. I think that I installed the program correctly and I have tried everything that I have found on this site and it still says the same thing every time I try to start it. Also when I tryed to reload my configuration it said "This application has failed to start because libintl3.dll was not found. Re-installing the application may fix this problem."
Thanks for the help

Calvin Battles

[kraada]

Calvin,

It sounds like your installation of PostgreSQL may be broken.

Please follow the steps of this tutorial to uninstall and reinstall properly, and it should fix this issue for you.

[oracle3001]

I am experiencing very similar problems to the original poster. I had a perfectly normal working system, then about 3 weeks ago I started to have the following problem.

I would start up my system, start up PT3, play a session, no problems. Close PT3. Come back after a break and fire up PT3 again. Problem is that the start up just hangs (and I now know it is because it can't connect to the DB). I try to log in using PgAdmin and I get the same messages that the original poster gets. Now until 3 weeks ago I have never experienced any problems with postgres, since I first installed postgres 8.3. Once the system has got in this state, the only way to fix it is to restart my whole machine. Attempting to restart or stop/start the postgres server results in the command timing out and just logging out and in again results in the postgres server unable to start up.

Ok, so I have sent a couple of support tickets regarding this, and the only advice I got was to reduce the number of connections settings. I tried this, and again suffering the same problem. One time use of PT3, second time start up PT3 fails to start and postgres is unusable.

Right, so I took the decision to uninstall postgres, uninstall PT3, delete all databases and start from scratch. Installed the latest version of postgres, A96 of PT3, and same problem. One time use of PT3 fine, from then on screwed.

Should also add that when using HEM (and other applications that use postgres) I don't encounter this, it works fine, and postgres continues to operate. It is only when I have been using PT3 that I encounter these problems.

For me it happens on exactly like this every single time, that it cant just be a one off "one of those things", it has to be either PT3 screwing up postgres somehow, or the interaction between postgres and PT3 is causing a serious problem. I have noticed quite a few posts over the past week or so, which sound like basically the same problem, but often poorly worded. Bells are ringing at my end that there is some underlying problem, which has been introduced in the last month or so, that is causing a fair number of people to have what sounds like the same problem.

[oracle3001]

Bump.

[kraada]

Oracle,

I've seen your post and I do agree that we've seen a lot more of these issues recently. I'm not entirely sure what's causing them, but I have raised the issue with Derek and it will be looked into.

[oracle3001]

Ok. If I can be of any assistant just let me know.

[kraada]

Thanks, I appreciate the offer.

[APerfect10]

I am the guy that you need to work with to resolve these "issues". I replied to your ticket and suggested lowering the max connections, you replied back that you would tried it later then I never heard anything further. You would be best served to keep the communication open in that ticket so that I can work with you.

While anecdotal posts are good they do not help us get to the root of the issue. We need PostgreSQL log files, setup a remote assistance session, etc.

Did these problems occur before or after you ran HEM? The only reason I ask is that every time I've ever tried to run HEM it has crashed PostgreSQL and caused major problems. I've never had problems with Postgres on my machine other than these times. (I am not trying to point blame, it could very well be a PT3 issue; I am just trying to get to the bottom of the issue)

Best regards,

Derek

[oracle3001]

For starters, I have been away for a few days. On my return I noticed that other people seemed to be having the same problem, so I added my comments there instead. I also commented here that lowering the amount of connections has made no difference. I also sent you a load of log files when this problem has occurred.

With regards HEM, I have had it on my system longer than PT3, and never a problem until as I said about 3 weeks ago (and I haven't upgrade HEM etc in the past month or so). However, I don't use HEM that much, and I have tried removing it and still getting these problems. So any thought that HEM is causing the problem is a definite red herring. The only time I suffer these problems is using PT3, no other application. Furthermore, I explained in my ticket that the only system change / application installation that I can remember is I changed security provider from ZoneAlarm to BitDefender. However, I have BitDefender, same version of postgres, same version of PT3 on my laptop and never had a problem there.

I have now sent you ever log since I did the postgres reinstall to the support ticket. Please note that there will be some errors in there saying certain DB's don't exist, that is due to deleting all the data, but obviously PT3 still trying to access them on first start-up afterwards before I have had to chance to delete links to them and create a new DB.