Re: [BUGS] no sufficient privileges to start system service
To strat the service on windows, the user (postgres, incase you didn't change during installation) needs to be have administrative privilege and service has to run as that user. You can use Run as in windows to run the particular executable or change the user in services. From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Milen Lazarov Sent: Saturday, May 05, 2012 12:41 AM To: pgsql-bugs@postgresql.org Subject: [BUGS] no sufficient privileges to start system service Hi. i can't complete the installation process as i have persisting problem. it gives me the following error message: Service pgsql 8.3 failed to start. Verify that you have sufficient privileges to start system service. where's the problem? can you help?
Re: [BUGS] no sufficient privileges to start system service
On 05/05/12 2:55 AM, Amit Kapila wrote:
To strat the service on windows, the user (postgres, incase you didn’t
change during installation) needs to be have administrative privilege
and service has to run as that user.
You can use Run as in windows to run the particular executable or
change the user in services.
the SERVICE account ('postgres') needs only 'run as service' privileges.
the user doing the start/stop needs admin privs.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] no sufficient privileges to start system service
On 05/05/12 12:14 PM, Milen Lazarov wrote: sorry, but i don't understand. i am just following the steps. what exactly should i do? well, normally, the windows installer just works. since it didn't, the process has to be troubleshooted, and you've not given us sufficient information to hazard a wild guess as to why. you didn't even say what OS you're running under (we had to guess it was some version of MS Windows because you mentioned 'service'), or anything else. anyways, this isn't a bug in postgres, so it really doesn't belong on the [bugs] list, would better be discussed on pg-general. -- john r pierceN 37, W 122 santa cruz ca mid-left coast -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
