by keggler » Thu Jun 26, 2008 2:55 pm
You've both probably got a permissions problem that another piece of software has set on a file folder or a registry key that is stopping the postgres service get going.
Get procmon (from sysinternals), restart the install, when it gets to the error, don't dismiss the dialog box, launch procmon, make a note of the postgres process ID (PID) from windows task manager, filter the procmon to this PID, scroll down to the bottom and look for any folders/registry keys this PID is trying to access.
The path and result columns in procmon should give you the clue as to the offending item...
If it turns out to be the path of a completely different app, this is the culprit that's holding the lock that's preventing postgres from starting - that app needs to be disabled, uninstalled or updated so it does not conflict with the postgres service.
susan