Menu
▾
▴
#3 Incomplete PostgreSQL install in Win 7 (64-bit)
DPSP installer v1.0.2 - Windows 7 Ultimate (64-bit)
This is a known issue but I'm logging it to make sure we have a record of it.
The DPSP installer appears to install all components, including PostgreSQL successfully. However, when I attempt to run DPR I get the error: "Error connecting to database". When I check Postgres databases via PgAdmin, I can see that the QF, PF and DR databases were not created during the install process.
I'm not sure if this may be related but I am also unable to get PostgreSQL to properly install on one of my Windows XP (sp2 32-bit) virtual machines. I can install Postgres OK on one of my other XP virtual machines, however it is not a clean install of XP, so the reasons for the difference are not clear. The non-clean install has Xena and OpenOffice.org 3.1 already installed. I have tried adding these to my clean XP install and running the DPSP installer again but it doesn't make a difference.
The only other clear difference between the two is that my clean install of XP has the local disk label of E:\ not C:\. Perhaps the installer is explicitly naming the C:\drive when creating the QF, PF and DR databases? I can't check this as Windows will not let me change the drive letter of the boot volume.
The above behaviour is also observed in a fresh install of Windows Vista (64-bit). When I check Postgres databases via PgAdmin, I can see that the QF, PF and DR databases were not created during the install process.
This has just come up again and looks to be a serious issue. In effect, the installer doesn't work at all on Windows 7 because the three databases are not created.
Based on AC's earlier observations, a possible cause might be the expected versus actual location of the create_xx.sql files during the setup process. On Win7 they are in:
Computer > OS (C:) > Program Files (x86) > National Archives of Australia > Digital Preservation Recorder
If the installer has a hard-coded assumption concerning the location of these files, it would explain the failure.
The current version of the installer (v2.0.1) will setup the databases in most cases. A change was made in v2.0.0 to use a vb script that looks for registry keys to find the locations of the sql files and of psql.exe. The installer will not install the databases if DPSP has already been installed. It will not replace existing databases if they are present. The script should be updated in a future release to work when DPSP is already installed and to give the user the option to overwrite databases already present. It should also be included in the installation directory so that it can be run after installation.
Lowering the priority as this is less of an issue with the current changes.