PDA

View Full Version : SQL service wont start on EITHER of my laptops



originaL
09-07-2008, 11:09 PM
I've been running HEM on 2 laptops which share a single data drive (external HD) successfully until today.

I had been data mining hands for 2 days while I was away. I came home, stopped HEM (which the importer still appeared to be working), rebooted my comp and since then have not been able to get the PostgreSQL 8.3 service to start.

I thought my SQL might be acting up on my original comp, so I plugged my external drive into my 2nd laptop and I can't get SQL service to load up on that laptop either. This leads me to believe its somehow related to my external data drive? I am usually pretty good at trouble-shooting, but I'm extremely lost right now.

I go into services and try to restart SQL, nothing. It always says "starting" or "stopping" - never started or stopped.

I don't have any firewall on my Vista PC, but I do have symantec corporate on my 2nd laptop. I doubt its related to firewalls because that's never been a problem before today.

Is there someway through all the data mining that something corrupted all my data files and now the service can't launch?

http://i16.photobucket.com/albums/b5/only1justin/sql.jpg
http://i16.photobucket.com/albums/b5/only1justin/error.jpg

morny
09-08-2008, 11:31 AM
Can you try this: http://208.109.95.123/faq/?f=153

Although that usually fixes the "Starts then Stops" message but i havent seen this one before.

Also try this with HM closed. go to C:\Program Files\PostgreSQL\8.2\data and delete the postmaster.pid file then restart holdem manager

If neither of these works maybe we can arrange a teamviewer.com session if that suits morny@holdemmanager.net btw i doubt the datamining had anything to do with it

originaL
09-08-2008, 11:59 AM
I went ahead and deleted my data directory and re-created it with a backup from last week. I lost some data from the last 5 days, but thats ok.

I'll let you know if it happens again. I did read in the SQL forums that if data becomes corrupted it will cause PostgreSQL to not be able to start.

I'll reply to this thread if I run into the same problem again.

Thanks