PDA

View Full Version : A connection to postgresql could not be made...



bbq
01-16-2010, 04:47 PM
"A connection to postgresql could not be made, would you like to have holdem manager attempt to start the service?"

I would like that very much, thank you, but when i click yes it just says:

"Sorry, Holdem manager was unable to start the service"

This problem actually started like half a month ago, but I've been to lazy to try and do anything about it other than uninstalling/reinstalling both postgresql and holdem manager. It has been working fine for ages, but then suddenly around late december it goes into cardiac arrest. Obviously that didn't work.

I've tried searching this forum for an answer, but I saw so many different suggestions that my head almost exploded.

So is there a known and preferably easy fix to this? Or is my best bet to just hit my computer repeatedly with a shovel until it sees the error of its ways?

fozzy71
01-16-2010, 10:18 PM
This is usually a firewall or windows update issue.

First try to reboot.

If no help, try this:

Start > Programs > PostgreSQL > 8.x > Stop Service

Start > Programs > PostgreSQL > 8.x > Start Service

If that doesnt help delete the \postgresql\8.x\data\postmaster.pid file, if you see it.

Add exceptions to the windows firewall, even if it is off. If you have a 3rd party firewall, do the equivalent or uninstall it temporarily - http://www.holdemmanager.net/faq/afmviewfaq.aspx?faqid=171

Please try following all of these FAQs, step by step:

1) http://www.holdemmanager.net/faq/afmviewfaq.aspx?faqid=34
2) reinstall the same version of postgresql, using the same \data folder - http://www.holdemmanager.net/faq/afmviewfaq.aspx?faqid=177
3) http://www.holdemmanager.net/forum/showthread.php?t=8261

If that doesn't help you will probably have to reinstall PostgreSQL completely and reimport your hands using these instructions - http://forums.holdemmanager.com/showthread.php?t=20755

bbq
01-17-2010, 04:28 PM
That did it. Thanks!

Pieter86
01-18-2010, 10:59 AM
Had the same problem, eventually step #3 did the trick (make sure u restart your pc, didnt work without restarting..)
so ty to the creator of that litle guide:)