Обсуждение: Re: postgressqlnot support inwindows 2000

> ------- Original Message -------
> From: Magnus Hagander <magnus@hagander.net>
> To: siva prakash <sivaa_eng@yahoo.co.in>, "'PostgreSQL'" <pgsql-general@postgresql.org>
> Sent: 30/06/07, 13:33:04
> Subject: Re: [GENERAL] postgressqlnot support inwindows 2000
>
> siva prakash wrote:
> > if i run the setup choose language then go to next button it shows error
> > *"Failed to create process: 2!*
>
> Please don't remove the mailinglist from the CC list, so others can
> learn from the answers.
>
> The error you get indicates that your windows installation is broken. At
> that point it tries to execute "msiexec" which is a part of windows
> installer and a core piece of windows that's not working. You need to
> make sure that it works properly before you can install PostgreSQL.

Unless I'm misreading it errors when the Next Button is clicked on the language dialog, which means msiexec has already
runonce. 

Siva; did you extract both msi files from the zip file before running the installer?

Regards, Dave

Dave Page wrote:
>
>> siva prakash wrote:
>>> if i run the setup choose language then go to next button it shows error
>>> *"Failed to create process: 2!*
>> Please don't remove the mailinglist from the CC list, so others can
>> learn from the answers.
>>
>> The error you get indicates that your windows installation is broken. At
>> that point it tries to execute "msiexec" which is a part of windows
>> installer and a core piece of windows that's not working. You need to
>> make sure that it works properly before you can install PostgreSQL.
>
> Unless I'm misreading it errors when the Next Button is clicked on the language dialog, which means msiexec has
alreadyrun once. 

Yes, but it was not necessarily launched as "msiexec". If the file was
just double-clicked on, the path to msiexec will be fetched from the
registry and not the system PATH. That's the only explanation I can find.


> Siva; did you extract both msi files from the zip file before running the installer?

That gives a different error message - it starts msiexec and then
msiexec is the one that complains. This error indicates that it can't
even find msiexec.exe to run.

//Magnus

Magnus Hagander wrote:
> Yes, but it was not necessarily launched as "msiexec". If the file was
> just double-clicked on, the path to msiexec will be fetched from the
> registry and not the system PATH. That's the only explanation I can find.

Not being installed on Windows 2000 is possible iirc - but breaking the
path and/or renaming the .exe (and then updating the registry to match)
seems like some really contrived breakage!!

>> Siva; did you extract both msi files from the zip file before running the installer?
>
> That gives a different error message - it starts msiexec and then
> msiexec is the one that complains. This error indicates that it can't
> even find msiexec.exe to run.

So it does. I'm sure I've seen that one before though; can't remember
where...

/D