suhleafs
09-09-2010, 04:09 PM
I am honestly getting sick of this error that keeps coming up. I'm running Windows XP.
I have tried the following suggestions:
http://forums.holdemmanager.com/manager-bugs/35937-failed-establish-connection-127-0-0-1-again-after-reinstalling-windows-7-a.html
http://forums.holdemmanager.com/manager-general/8261-still-cant-connect-posgresql-try.html
http://forums.holdemmanager.com/manager-general/16726-postgres-will-not-start.html
FAQ - Hold'em Manager Poker Tracking Software :: Reinstall PostgreSQL Preserving Old Database (http://faq.holdemmanager.com/questions/71/Reinstall+PostgreSQL+Preserving+Old+Database)
I have tried every suggestion in here: http://forums.holdemmanager.com/manager-general/16726-postgres-will-not-start.html
I have reformatted my computer and this still keeps coming up. I am absolutely sick of un/reinstalling HEM/Postgres every few days, then reimporting ALL my hands. I thought this would have been fixed with reformatting, but the problems still continued. When will this be fixed? It looks like it is a large enough issue that it needs to be worked on by your development team.
Does anyone have any suggestions?
I have tried the following suggestions:
http://forums.holdemmanager.com/manager-bugs/35937-failed-establish-connection-127-0-0-1-again-after-reinstalling-windows-7-a.html
http://forums.holdemmanager.com/manager-general/8261-still-cant-connect-posgresql-try.html
http://forums.holdemmanager.com/manager-general/16726-postgres-will-not-start.html
FAQ - Hold'em Manager Poker Tracking Software :: Reinstall PostgreSQL Preserving Old Database (http://faq.holdemmanager.com/questions/71/Reinstall+PostgreSQL+Preserving+Old+Database)
I have tried every suggestion in here: http://forums.holdemmanager.com/manager-general/16726-postgres-will-not-start.html
I have reformatted my computer and this still keeps coming up. I am absolutely sick of un/reinstalling HEM/Postgres every few days, then reimporting ALL my hands. I thought this would have been fixed with reformatting, but the problems still continued. When will this be fixed? It looks like it is a large enough issue that it needs to be worked on by your development team.
Does anyone have any suggestions?