Scenario 1: Permission issues

 

Description:

 

While the Database migration is in progress, If the Read/Write permissions to the case directories are not appropriately set, you may encounter this issue.

 

 

To continue the migration, the user must revert to PG 11 and then set the permissions manually. To do so, follow the below steps:

 

  1. Close the DBConfig file.
  2. Open the Control Panel.
  3. Uninstall the following:
  • FTK Suite
  • PG11
  • PG14

 

Control Panel:

 

 


 

Case directory:

 

 


 

SP3 Patch in the registry editor:

 

 

  • Delete all items under:

 

Program Files\AccessData  and ProgramData\AccessData\Products

 

Note: Ensure that the PG11 data directory and case folders (the location where evidence are stored while processing) are untouched.

 

 

 

4.  Re-install FTK 7.5 in ‘Advanced’ mode.


Note: While installing the PostgreSQL 11 data directory must be pointed to the Old PG11 Directory. (The user might remember the old PG DB password and FTK Application login password).

 

 

 

  • The ‘Data Folder Exists’ pop up is displayed.

 

Graphical user interface, text, application, email Description automatically generated

 

  5. Click ‘Yes’ to proceed with the installation.

  6. Upon successful installation, log in to the FTK.

 

Note: Upon logging in, by default, the PG11 Database authentication is popped up and the corresponding PG11 evidences are listed.

 

 7.  Continue the 7.6 and SP3 patch installation process.

 8.  Upon installing the SP3 Patch, set the permissions manually by following the below steps,

 

Providing the User with Read access to the Data folders:

 

  1. Navigate to the PostgreSQL 11.2 data folder.
  2. Right click the folder.
  3. Open the ‘Properties’.
  4. Click ‘Security’.
  5. Click ‘Advanced’.
  6. Change the user (refer the below screenshot).


   7.  Enable the check boxes.

   8.  Click ‘Apply’.

   9.  Click ‘Ok’.


 10.  Click ‘Edit’.


Graphical user interface, text, application, email Description automatically generated

        11.  Click ‘Add user’.

 

 


         12.  Add user with ‘Read’ access.

         13.  Click ‘Apply’.

         14.  Click ‘Ok’.

 

Note: Ensure that the user has ‘Read’ access.

     

        15.  Navigate to the PostgreSQL 14.0 data folder.

        16.  Follow all the steps that were performed for PostgreSQL11.2 data folder.

        17.  Continue with the migration process.

 

 

 

Scenario 2: No disk space error

 

Description: The migration fails if the available disk space is low.

 

To continue the migration, the user needs to revert to PG 11 and then has to increase the disk space before restarting the Migration process.

 

  1. Close the DBConfig.
  2. Open the Control Panel.
  3. Uninstall the following things:
  4. Uninstall the following:
  • FTK Suite
  • PG11
  • PG14

 

Control Panel:

 

 

Case directory:

 

 

SP3 Patch in the registry editor

 

 

  • Delete all items under:

 

Program Files\AccessData  and ProgramData\AccessData\Products

 

Note: Ensure that the PG 11 Data directory and the case folders (the location where evidence are stored while processing) are untouched.

 

 

 

4. Re-install FTK 7.5. in ‘Advanced’ mode.

 

Note: While installing the PostgreSQL 11 data directory has to be pointed to the Old PG11 Directory. (The user might remember the old PG DB password and FTK Application login password).

 

 

 

  • The ‘Data Folder Exists’ pop up is displayed.

 

Graphical user interface, text, application, email Description automatically generated

5. Click ‘Yes’ to proceed with the installation.

6. Upon successful installation, login the FTK.

 

Note: Upon logging in, by default, the PG11 Database authentication is popped up and the corresponding PG11 evidences are listed.

 

7. Continue the 7.6 and SP3 patch installation process

8. Upon successful installation continue with the migration process.

 

  

Scenario 3: Error / Interrupted while Migration / Schema update

 

Description:

 

Migration failure due to socket connectivity, system restart, Power failures, etc.,

 

Migration failure:

 

 

Schema version not updated after migration:

 

 

Erron might occur while Schema is updating:

 

 

 

  1. Close the DBConfig.
  2. Open the Control Panel.
  3. Uninstall the following things:
  4. Uninstall the following:
  • FTK Suite
  • PG11
  • PG14

 

Control Panel:

 

 

Case directory:

 

SP3 Patch in the registry editor:

 

 


 

  • Delete all items under:

 

Program Files\AccessData  and ProgramData\AccessData\Products

 

Note: Ensure that the PG11 data directory and case folders (the location where evidence are stored while processing) are untouched.

 


5. Re-install FTK 7.5 in ‘Advanced’ mode.

 

Note: While installing the PostgreSQL 11 data directory has to be pointed to the Old PG11 Directory. (The user might remember the old PG DB password and FTK Application login password).

 

 


 

 


 

  • The ‘Data Folder Exists’ pop up is displayed.

 

 

6. Click ‘Yes’ to proceed with the installation.

7. Upon successful installation, login the FTK.

 

Note: Upon logging in, by default, the PG11 Database authentication is popped up and the corresponding PG11 evidences are listed.

 

8.  Continue the 7.6 and patch installation process