Re: problem with silent installation

I am installing 8.1.4 on a Windows XP SP2 virtual machine (VMWare). It seems
that if I specify BASEDIR=<path> in my command line, and <path> is NOT the
default install path, I get the error "internal account lookup failure"
immediately after the postgres user account is created. If I leave the
BASEDIR statement out of the command line, the install succeeds.

When performing the initial installation, Simple File Sharing was enabled.
My installation was disabling Simple File Sharing, but not until after the
PostgreSQL install was complete. However, if I disable Simple File Sharing
prior to installing PostgreSQL, I can specify a BASEDIR and I do not receive
the error message indicated above.

Thus, it appears the Simple File Sharing setting interferes with the
PostgreSQL installation's ability to set permissions on the \<BASEDIR>
folder.

To disable Simple File Sharing, change the registry setting:

HKLM\SYSTEM\CurrentControlSet\Control\Lsa\forceguest = 0

Or uncheck the "Tools > Folder Options > View > Use simple file sharing"
option from Windows Explorer.

After digging deeper, it seems that the Simple File Sharing setting is not
the key to the problem. It has a lot to do with the SERVICEDOMAIN and
BASEDIR settings.

- If I do not specify BASEDIR or SERVICEDOMAIN, the installation succeeds.

- If I specify BASEDIR but not SERVICEDOMAIN, the installation never
succeeds regardless of the state of the Simple File Sharing setting.

- I have never been able to get the installation to succeed using
SERVICEDOMAIN="%COMPUTERNAME%" - it fails every time with the same "Internal
account lookup failure" error.

- If I specify SERVICEDOMAIN and pass the name of the computer as read from
the Windows Registry (i.e. SERVICEDOMAIN="MYCOMPUTER"), I am also able to
specify BASEDIR regardless of the state of the Simple File Sharing setting
and the installation seems to succeed every time!

After more extensive testing on various operating systems (2K SP4, XP SP2,
Server 2003, and Vista Business), here is information regarding the use of
different "silent mode" switches in combination with the SERVICEDOMAIN and
BASEDIR switches:

Using the command line: (do not specify SERVICEDOMAIN or BASEDIR)
msiexec /i "<path>\postgresql-8.1-int.msi" <UIType> INTERNALLAUNCH=1
SERVICEPASSWORD="<pwd>" CREATESERVICEUSER=1 SUPERPASSWORD="<pwd>"
ENCODING=UTF8 ADDLOCAL=server,psql,pgadmin

where <UIType> =
/qr - install succeeds on 2K/XP/Server 2003/Vista
/qn - install fails on XP/Server 2003 (assumed "Internal account lookup
failure" error)
/qb - install fails on 2K/XP/Server 2003 with "Internal account lookup
failure" error

Using the command line: (specify both SERVICEDOMAIN and BASEDIR)
msiexec /i "<path>\postgresql-8.1-int.msi" <UIType> INTERNALLAUNCH=1
SERVICEDOMAIN="<ComputerName>" SERVICEPASSWORD="<pwd>" CREATESERVICEUSER=1
SUPERPASSWORD="<pwd>" ENCODING=UTF8 ADDLOCAL=server,psql,pgadmin
BASEDIR="C:\PostgreSQL"

where <ComputerName> is setting read from Windows Registry and <UIType> =
/qr - install succeeds on 2K/XP/Vista but fails on Server 2003 with
"Internal account lookup failure" error
/qn - install succeeds on XP but fails on Server 2003 (assumed "Internal
account lookup failure" error)
/qb - install succeeds on 2K/XP but fails on Server 2003 with "Internal
account lookup failure" error

Using the command line: (specify BASEDIR, do not specify SERVICEDOMAIN)
msiexec /i "<path>\postgresql-8.1-int.msi" <UIType> INTERNALLAUNCH=1
SERVICEPASSWORD="<pwd>" CREATESERVICEUSER=1 SUPERPASSWORD="<pwd>"
ENCODING=UTF8 ADDLOCAL=server,psql,pgadmin BASEDIR="C:\PostgreSQL"

where <UIType> =
/qr - install succeeds on 2K/XP/Server 2003/Vista
/qn - install fails on XP/Server 2003 (assumed "Internal account lookup
failure" error)
/qb - install fails on 2K/XP/Server 2003 with "Internal account lookup
failure" error

--
View this message in context: http://www.nabble.com/problem-with-silent-installation-tp15822573p16339519.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.