Re: BUG #2343: Silent installers fails

From: Support FireDigit <support(at)firedigit(dot)com>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2343: Silent installers fails
Date: 2006-03-21 22:42:19
Message-ID: 4420814B.7060903@firedigit.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
it works when run manually, it looks like the combination NSIS
installer and the MSI installer doesn't work very well.<br>
I did what you suggested, I created a user before launching the
installer and the installer failed this time with the following error.<br>
<br>
User "some binary signs"4/"some binary signs" could not be found.<br>
replace "some binary signs" with some binary signs.<br>
<br>
The user was correctly created with the right permissions and the
silent installer command was:<br>
<pre wrap="">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</pre>
Anton<br>
<br>
Magnus Hagander wrote:
<blockquote
cite="mid6BCB9D8A16AC4241919521715F4D8BCEA351A3(at)algol(dot)sollentuna(dot)se"
type="cite">
<blockquote type="cite">
<pre wrap="">Bug reference: 2343
Logged by: Anton
Email address: <a class="moz-txt-link-abbreviated" href="mailto:support(at)firedigit(dot)com">support(at)firedigit(dot)com</a>
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.
</pre>
</blockquote>
<pre wrap=""><!---->
Does it work if you run it manually?

</pre>
<blockquote type="cite">
<pre wrap="">Any idea what could cause this and what could be a workaround?
</pre>
</blockquote>
<pre wrap=""><!---->
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

</pre>
</blockquote>
</body>
</html>

Attachment Content-Type Size
unknown_filename text/html 2.6 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Marinos Yannikos 2006-03-22 04:57:16 Re: BUG #2334: WHERE IN (SUBSELECT) fails when column is null
Previous Message Rafael Jorge Sierra Goncales 2006-03-21 20:21:55 BUG #2352: Bug with Pl/Python