[GENERAL] Re: Cannot start Postgresql 9.3 as a service in Windows 2012 Server with a domain account

2014-06-12 Thread boca2608
After adding the domain user account into the local users group, the postgresql service can be started successfully now. We will do more testing to make sure that all postgresql functions are working. But I want to give my big thanks to Krystian Bigaj, Igor Neyman and Raymond O'Donnell for offeri

[GENERAL] Re: Cannot start Postgresql 9.3 as a service in Windows 2012 Server with a domain account

2014-06-12 Thread boca2608
+s1045698n5807004...@n5.nabble.com] Sent: Thursday, June 12, 2014 10:06 AM To: boca2608 Subject: Re: Cannot start Postgresql 9.3 as a service in Windows 2012 Server with a domain account > -Original Message- > From: [hidden email] [mailto:pgsql-general- > [hidden email]] On Behalf Of

[GENERAL] Re: Cannot start Postgresql 9.3 as a service in Windows 2012 Server with a domain account

2014-06-12 Thread boca2608
Krystian Bigaj replied this in a separate email, which led to some interesting information that I would like to share in this mailing list. He suggested the use of the "Process Monitor" app to log the process events during the startup of the service and look for "ACCESS DENIED" errors. Here is wh

[GENERAL] Re: Cannot start Postgresql 9.3 as a service in Windows 2012 Server with a domain account

2014-06-12 Thread boca2608
Thanks Ray. But unfortunately, there is no log entry in the postgresql log (as in the data/pg_log folder). The log file is empty. I checked the log before and after the error. Thanks, John -- View this message in context: http://postgresql.1045698.n5.nabble.com/Cannot-start-Postgresql-9-3-as

[GENERAL] Cannot start Postgresql 9.3 as a service in Windows 2012 Server with a domain account

2014-06-11 Thread boca2608
First, we have tried many suggestions found in this and other sites. But the problem has not been solved. When trying to start postgresql as a service with a domain account on a windows 2012 server, the service starts and stops immediately. The Windows event log showed a terse error about timeout