Re: BUG #2271: no privilege to install

> The following bug has been logged online:
>=20
> Bug reference:      2271
> Logged by:          Peter laursen
> Email address:      deepeter@snaps.dk
> PostgreSQL version: 8.1.3.1

There is no such version of PostgreSQL.


> Operating system:   Win XP SP2 Home - Dansih
> Description:        no privilege to install
> Details:=20
>=20
> I installed 8.1.1.1 successfully some months ago.  An update=20
> to 8.1.3.1 fails.  Server program installs (Files copy,=20
> registry values are written) but service does not install due=20
> to privilege issue.

There is no 8.1.3.1 version. I assume you mean 8.1.3.

This is a known issue,that we don't know why it happens. The solution is
documented in the FAQ
(http://www.postgresql.org/docs/faqs.FAQ_windows.html#3.7) question 3.7.


> However my user account is an ADMINISTRATOR account.  But as=20
> ADMINISTRATOR in WinXP HOME is another implementation than in=20
> WinXP PROFESSIONAL, I suspect that the installer does not=20
> realize that difference!  And I had no problems with 8.1.1.1=20
> of the kind and also not MySQL, Apache and other programs=20
> installing services

No, there is no difference between an administreator in XP Home and XP
Pro. There's a difference in the UI, but the installer doesn't care
about the UI.

MySQL and Apache by default run as local system, which is very dangerous
should a security issue appear in either product or their plugins.
PostgreSQL protects you agains this, which causes a bit of extra issues
in some cases.

I don't beleive this one is related to that, though. It's a case of
Windows Installer getting confused.


> With XP Home I have no option to grant more privileges,=20
> except than logging on as user 'ADMINISTRATOR' from fail-safe=20
> mode.  However running MSI-installer from failsafe mode is=20
> not possible/allowed. :-(

Yes, it does. You can use the commandline tools available to add a user
to the administrators goup, for example. MS just took away the UI.

Though again, I don't think this is related.



> I 'worked around' the problem by running the UPGRADE.BAT=20
> until MSGBOX with privilege issue occurred.  Instead of=20
> cancelling the install I then killed MSI from Task Manager.=20=20

I wouldn't trust that method, you may have a partially upgraded system.
I suggest applying the solution from the FAQ.


//Magnus