Postgres Pro
Downloads
Home   >   mailing lists

Thread: BUG #2343: Silent installers fails

BUG #2343: Silent installers fails

From
"Anton"
Date:
The following bug has been logged online:

Bug reference:      2343
Logged by:          Anton
Email address:      support@firedigit.com
PostgreSQL version: 8.1.2
Operating system:   Windows XP
Description:        Silent installers fails
Details:

Hi All,

When the installer creates the user account, I get the following error:

Internal Account lookup failure
No mapping between account names and security ID's was done.

Here is the silent installer command:

msiexec /i C:\hsm\source\pgsql\postgresql-8.1-int.msi  /qr INTERNALLAUNCH=1
ADDLOCAL=server,psql,pgadmin SERVICEDOMAIN=%COMPUTERNAME%
SERVICEACCOUNT=fd202016fd SERVICEPASSWORD=fd_pgsql SUPERUSER=root
SUPERPASSWORD=fd_hsm PERMITREMOTE=1 ENCODING=UTF8 CREATESERVICEUSER=1
BASEDIR=C:\hsm\postgres

This is run from an NSIS installer (with ExecWait).
The user account "fd202016fd" specified was created.

Any idea what could cause this and what could be a workaround?

Thanks,
Anton

Re: BUG #2343: Silent installers fails

From
"Magnus Hagander"
Date:
> Bug reference:      2343
> Logged by:          Anton
> Email address:      support@firedigit.com
> PostgreSQL version: 8.1.2
> Operating system:   Windows XP
> Description:        Silent installers fails
> Details:=20
>=20
> Hi All,
>=20
> When the installer creates the user account, I get the=20
> following error:=20
>=20
> Internal Account lookup failure
> No mapping between account names and security ID's was done.
>=20
> Here is the silent installer command:
>=20
> msiexec /i C:\hsm\source\pgsql\postgresql-8.1-int.msi  /qr=20
> INTERNALLAUNCH=3D1 ADDLOCAL=3Dserver,psql,pgadmin=20
> SERVICEDOMAIN=3D%COMPUTERNAME% SERVICEACCOUNT=3Dfd202016fd=20
> SERVICEPASSWORD=3Dfd_pgsql SUPERUSER=3Droot SUPERPASSWORD=3Dfd_hsm=20
> PERMITREMOTE=3D1 ENCODING=3DUTF8 CREATESERVICEUSER=3D1=20
> BASEDIR=3DC:\hsm\postgres
>=20
> This is run from an NSIS installer (with ExecWait).
> The user account "fd202016fd" specified was created.

Does it work if you run it manually?


> Any idea what could cause this and what could be a workaround?

Not really, it shouldn't normally happens. It seems it's created, but
the process that created it can't see it because of some delay
somewhere.

A workaround is to create the account before you launch the installer.

//Magnus

Re: BUG #2343: Silent installers fails

From
Support FireDigit
Date:
it works when run manually, it looks like the combination NSIS
installer and the MSI installer doesn't work very well.
I did what you suggested, I created a user before launching the
installer and the installer failed this time with the following error.

User "some binary signs"4/"some binary signs" could not be found.
replace "some binary signs" with some binary signs.

The user was correctly created with the right permissions and the
silent installer command was:
msiexec /i C:\hsm\source\pgsql\postgresql-8.1-int.msi  /qr
INTERNALLAUNCH=1 ADDLOCAL=server,psql,pgadmin
SERVICEDOMAIN=%COMPUTERNAME% SERVICEACCOUNT=fd202016fd
SERVICEPASSWORD=fd_pgsql SUPERUSER=root SUPERPASSWORD=fd_hsm
PERMITREMOTE=1 ENCODING=UTF8 CREATESERVICEUSER=0
BASEDIR=C:\hsm\postgres
Anton

Magnus Hagander wrote:
<blockquote
 cite="mid6BCB9D8A16AC4241919521715F4D8BCEA351A3@algol.sollentuna.se"
 type="cite">

    Bug reference:      2343
Logged by:          Anton
Email address:      support@firedigit.com
PostgreSQL version: 8.1.2
Operating system:   Windows XP
Description:        Silent installers fails
Details:

Hi All,

When the installer creates the user account, I get the
following error:

Internal Account lookup failure
No mapping between account names and security ID's was done.

Here is the silent installer command:

msiexec /i C:\hsm\source\pgsql\postgresql-8.1-int.msi  /qr
INTERNALLAUNCH=1 ADDLOCAL=server,psql,pgadmin
SERVICEDOMAIN=%COMPUTERNAME% SERVICEACCOUNT=fd202016fd
SERVICEPASSWORD=fd_pgsql SUPERUSER=root SUPERPASSWORD=fd_hsm
PERMITREMOTE=1 ENCODING=UTF8 CREATESERVICEUSER=1
BASEDIR=C:\hsm\postgres

This is run from an NSIS installer (with ExecWait).
The user account "fd202016fd" specified was created.



Does it work if you run it manually?




    Any idea what could cause this and what could be a workaround?



Not really, it shouldn't normally happens. It seems it's created, but
the process that created it can't see it because of some delay
somewhere.

A workaround is to create the account before you launch the installer.

//Magnus

Re: BUG #2343: Silent installers fails

From
"Magnus Hagander"
Date:
> 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