Symptom: You get the error "Unable to connect to database requested" or a similar error message when starting FTK using the PostgreSQL database.
Cause: The causes can vary, so this will walk you through the usual troubleshooting process for PostgreSQL connection issues.
- Make sure the database drive isn't write-protected. If it is, unblock it and reboot. Also check the drive permissions to make sure you have full access.
- Open the Services snap-in (services.msc) to see if the PostgreSQL service is "started". The service may have one of the following names:
- Make sure that the drives being used are formatted NTFS
- If the PostgreSQL service isn't started, double-click on it, make sure the "Startup type" is set to Automatic, then click "Start".
- If the service won't start, do the following:
- Open "regedit".
- Navigate to "HKLM\SYSTEM\CurrentControlSet\services\postgresql-x**-*.*".
- Check the "ImagePath". It should look similar to the following:
C:/Program Files/AccessData/PostgreSQL/bin/pg_ctl.exe runservice -N "postgresql-x64-9.1" -D "D:/pgdata" -w
(Notes: The first underlined path is the location of PostgreSQL binaries. The second underlined path is the location of PostgreSQL data.)
- If either of the underlined paths are pointing to an incorrect location, double-click "ImagePath" to edit the value, then modify it appropriately.
- Go back to "services.msc".
- Double-click the PostgreSQL service to open the service properties.
- Under the "Log On" tab, make sure it's either set to run under the Local System account (for one-box setups) or another account with Administrator rights (for multi-box setups or DPE).
- Start the service.
- If the PostgreSQL service will still not start, there may be minor corruption, requiring the transaction logs be reset.
- If the PostgreSQL service starts, but FTK doesn't connect or list any cases and/or all options are greyed out, you may need to repair the PostgreSQL junction links.
- If the PostgreSQL starts then stops immediately, reboot the machine and see if it will start.