Re: BUG #2343: Silent installers fails - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: BUG #2343: Silent installers fails
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA0F8A1@algol.sollentuna.se
Whole thread Raw
In response to BUG #2343: Silent installers fails  ("Anton" <support@firedigit.com>)
List pgsql-bugs
> it works when run manually, it looks like the combination=20
> NSIS installer and the MSI installer doesn't work very well.
> I did what you suggested, I created a user before launching=20
> the installer and the installer failed this time with the=20
> following error.
>=20
> User "some binary signs"4/"some binary signs" could not be found.
> replace "some binary signs" with some binary signs.
>=20
> The user was correctly created with the right permissions and=20
> the silent installer command was:
>=20
> msiexec /i C:\hsm\source\pgsql\postgresql-8.1-int.msi  /qr
> INTERNALLAUNCH=3D1 ADDLOCAL=3Dserver,psql,pgadmin=20
> SERVICEDOMAIN=3D%COMPUTERNAME% SERVICEACCOUNT=3Dfd202016fd=20
> SERVICEPASSWORD=3Dfd_pgsql SUPERUSER=3Droot SUPERPASSWORD=3Dfd_hsm
> PERMITREMOTE=3D1 ENCODING=3DUTF8 CREATESERVICEUSER=3D0=20
> BASEDIR=3DC:\hsm\postgres Anton

My first guess is that NSIS somehow mixes up the commandline. Can you
try sticking the full command in a .bat-file, and have NSIS call the
.bat?

//Magnus

pgsql-bugs by date:

Previous
From: "Anita Lederer"
Date:
Subject: vacuum: invalid memory alloc request size 2684354556
Next
From: Carlos Rivas
Date:
Subject: Error in ecpg