I'm guessing the postgresql got installed on the other machine at some point. In my experience, the upgrade works just fine, just not a new install.
The way the Postgresql install is supposed to work is something like this; the installer is run by an admin account with access to create a new generic user called postgres. It then creates the directory structure and unpacks the files. Then it modifies the permissions of those files to allow for access from the installing admin account. Then an initialization program is run to set up the databse. This initdb executable must be run as a non-admin account, postgres in this case. The problem is it doesn't change context for some reason so the initdb uses the admin account and fails because it will not initialize with an admin account for security reasons. After this step, it is supposed to modify the dirctory permissions again to include access for the postgres account and then install the service and add items to the start menu. Non of this is done because the intitdb fails. The way I got around this problem is to run the initdb executable as the postgres user instead of relying on the execuable to make the context change for me. Here are my instructions. They are based on the default install locations. I was actually installing RSP or HP Insight Remote Support Advanced or whatever they are calling it now. The postgresql.exe that I run is coming from the expanded Remote Support install.
1. postgresql.exe --mode unattended --superpassword Webe$rules8552 --serverport 7950
This will fail with this error
******************************
creating template1 database in C:/Program Files/PostgreSQL/8.3/data/base/1 ... initdb: could not execute command ""C:/Program Files/PostgreSQL/8.3/bin/postgres.exe" --boot -x1 -F ": No error
initdb: removing contents of data directory "C:/Program Files/PostgreSQL/8.3/data"
Failed to initialise the database cluster with initdb
******************************
This is because the initdb tried to run as the admin user...I think.
2. give postgres user execute permissions to c:\windows\system32\cmd.exe
3. give postgres user Read & Execute, List Folder Contents and Read permissions on default postgresql install location root folder...and propagate.
4. give postgres Modify permissions on the data directory default location.
5. create password file called password.txt in the bin folder with the pasword Webe$rules8552 in it.
6. run this command for a command prompt....runas /user:postgres "cmd /K C:\Progra~1\PostgreSQL\8.3\bin\initdb.exe --pwfile C:\Progra~1\PostgreSQL\8.3\bin\password.txt --encoding=UTF-8 -A md5 -U postgres -D C:\Progra~1/PostgreSQL/8.3/data"
Use Webe$rules8552 as the password for the runas command.
This will take care of the initialization for you. Now we need to rerun the install to finish things up.
7. postgresql.exe --mode unattended --superpassword Webe$rules8552 --serverport 7950
8. Delete password file
9. remove access to cmd.exe
This is how I got PostgreSQL installed on Windows 2003 R2 SP2. Admittedly I am installing this at a customer site so I do not know if they have security changes on their base builds that effects this. I am installing a base 2003 R2 SP2 install on my laptop right now to test. Additionally, I got the same results with the latest postgresql install using the DBEnterprise installer. The HP supplied version is 8.3.1, I think. I am also going to need to install this on 2008 R2 so I will be testing that as well. I have not found any support matrix docs for OS versioning for Remote Support Advanced except that it needs to run on a CMS. I also believe that 2003 R2 32-bit and 2008 is supported for a CMS. IF that is the case....this seems to be a big problem.
