1. This message occurs if the database to be upgraded is not running. Make sure that the database is running. The upgrade process builds a list of all databases from the ini that can be successfully connected to. If the database is not running, the upgrade will not detect the database and the message will occur.
2. This can also occur is there is an issue with the database that causes the upgrader to not be able to see it. To determine if the upgrader identified an issue with the database, review the following logs that the upgrader creates. They are located in npo\found\fims:
3. If you have reviewed the logs above and see no issues as to why the database was skipped, then to resolve this issue, do the following:
Note: Be sure that the FIMSNT ini file has the correct paths to the database in the database section of the ini file.
1. Open cmd.exe. being sure to run as an administrator
2. Type in the following and run all as separate commands:
%dlc%\bin\probkup n:\found\dbfiles\found n:\found\dbfiles\found-20180601.bkp (this bkp file name is just an example name, you can name it what you like)
cd /d n:\found\fims
%DLC%\bin\prowin32.exe -p tools\FimsInstallCompile.p -assemblies ..\assemblies -ini ..\configfiles\FIMSNT.INI -s 2560 -inp 32000 -param nodbbackup
Note that the new files that were installed during the 1st portion of the upgrade which is the FIMS application upgrade will still be there, so there is no need to re-run the upgrade from the beginning for this issue. These commands are finishing the 2nd part of the upgrade, which is to upgrade the database itself.