How do I Upgrade FIMS to the latest version?

I am running an older version of FIMS and I want to upgrade to the latest version.  This is NOT for clients on Hostnet, it is only for locally installed FIMS clients.
In this article we will walk through step by step what should be done to successfully upgrade your existing version of FIMS to the current version of FIMS (or the version of the upgrade file downloaded from our site).  Note that installing a FIMS patch is different from these steps.  These steps are for upgrading FIMS to a specific version NOT applying a specific patch.

Before You Start:

Things you will need before you begin the FIMS upgrade process:
  1. The FIMS upgrade zip file downloaded onto the FIMS server.  When a new FIMS release is available there will be a post on Blackbaud Community and a link or instructions on how to get the upgrade file.
  2. All FIMS users must be out of FIMS before you start and during the entire upgrade process (generally takes about 1 hour).
  3. You will need to log into the FIMS server (the system (server) that shares the npo folder to the client workstations and has FIMS/Progress installed onto it) as a Windows Administrator rights user.
Upgrading FIMS
  1. Verifying All users are out of FIMS and FIMS files are all closed:
  1. Normally your server running FIMS will have a shortcut on the desktop called “Show All Users” (or something named very similar).  Run the “Show All Users” shortcut and verify that all users are out of FIMS (the DB_Agent and WDOG users are system and can be there).  Any other user must get out of FIMS before proceeding.  You can choose to disconnect them in the show live users utility.  For the ‘Enter choice’, type “1” and then the ‘usr’ number (it’s the first column on the left).  It is best for the users to know to stay out so they don’t just sign back in thou, so I recommend asking them to get out first if possible.
User-added imageUser-added image
  1. If you don’t have this shortcut you can create it by browsing to the file (npo\dlc\bin\_mprshut.exe) and right clicking on it.  Then from the pop-up menu select “Send To” and “Desktop”.  On the desktop shortcut you just created, right click and select properties from menu.  In the “Target” field, add the following text after “_mprshut.exe” – a space and “c:\npo\found\dbfiles\found” (note if the drive or path for the npo folder is different you’ll need to adjust for that).
 User-added image
  1. Run Computer Management (Control Panel > Administrator Tools > Computer Management).  On the left column, expand the “Shared Folders” item and click to select “Open Files”.  Close all files listed within the npo folder (select those files, right click, close open file).
User-added image
  1. Making Back-Ups of the Files and Folders About to be Changed:
  1. Copy the Assemblies folder (\npo\found\Assemblies).  Right click on this folder and select copy from pop-up menu.  Click on Organize and Paste.
User-added imageUser-added imageUser-added image
  1. Copy the FIMS folder (\npo\found\FIMS) using the same process as with the assemblies folder.  Rename it to “fimsbkp-YYYYMMDD”.
  User-added image
  1. Extracting the Upgrade Files and Updating the FIMS application files:
  1. Create a new folder in the npo folder called temp.  Copy the upgrade file that you downloaded from Blackbaud into this temp folder.  Extract the upgrade zip file.  Select the file and right click on it.  From the pop-up menu, click on “Extract All…”.  The default path will be a folder named the same as the file (this is fine) and uncheck the “show extracted files when complete” box.  Click Extract button.
User-added image
  1. Open the new folder that was created.  Now we’re going to move the files within this upgrade folder into the FIMS folder (\npo\found\FIMS).  To move the upgrade files, select all the files and folders within the extracted upgrade folder (Organize > Select All) and cut (Organize > Cut).  Now browse to the FIMS folder (\npo\found\fims).
User-added image
  1. Paste the files and folders (Organize > Paste).  At the Confirm window, check the “Do this for all current items (8 found)” box and click “Yes”.  Another Move File window will pop-up, check the “Do this for the next 5793 conflicts” box and click “Move and Replace”.
User-added imageUser-added image
  1. Select and copy all the files in the npo\found\FIMS\Assemblies folder and paste them into the npo\found\Assemblies folder following the same process as we just did (except this time we are copying (not cutting) the files).
  1. Upgrading the FIMS Database:
  1. Run FIMS but before selecting a database key “alt & F10”.  This will open the Procedure Editor.
User-added imageUser-added image
  1. Type in “RUN system\d-dbpick”. Hit F1.  Select the database and login using your FIMS user.  Hit the space bar.  Note: If you running in a single-user configuration, you may encounter an error saying that you can’t log into the database because it’s in single-user mode. You can ignore this error.  When you click OK, it will not ask for a username or password.  That's expected as well.  Just continue on with the next step.
User-added imageUser-added imageUser-added image
  1. Erase “RUN system\d-dbpick”.  Type in “RUN tools\upfims.p ‘compile’”. Hit F1.
User-added image
  1. You will get a pop-up with a summary of the action about to take place.  The key pieces to verify/check are the database it says you’re upgrading and the current database version it is at and what version it’s going to upgrade to.
User-added image
  1. Click Yes to continue.
  2. At this point the process is all hands free.  The upgrading of the database will first create a backup.  Then it will flash through a series of process.  The compiler section takes normally the longest.
User-added imageUser-added image
  1. A pop-up will show after the compile if there were errors saying to contact support.  Click ok on this if it comes up.  Any errors will be recorded into the fcompile.err file in the FIMS directory (npo\found\FIMS).
  2. If no compile errors occur (or after you click ok to the pop-up message) then it’ll finish and move on to the remaining process left to upgrade the database.  When finished it will display across the bottom of the “Procedure Editor – Run” window - “Procedure complete. Press space bar to continue.” Press spacebar.
User-added image
  1. Erase the “RUN tools\upfims.p ‘compile’”.  Close the Procedure Editor.  If you didn’t clear the run command it will ask if you want to save changes before exiting.  Click no.
  1. Verifying that the FIMS Upgrade was Successful:
  1. Launch FIMS and login.
  2. Click Help > About FIMS.  You should see the correct FIMS version there.
User-added image
  1. Click on from the menu - Tools > System Utilities > System Reports > System Information Report
  2. Check only the top one “System Initial Setup and Other System Info”.  Click ok
User-added image.
  1. Scroll to the bottom of the created report.  The DBVer and the FIMS Version should be the same and they both should be the expected upgraded version (if they are not, do the upgrade again). 
User-added image
  1. FieldMaker Users:
  1. If you have FieldMaker then we need to re-commit changes in Fieldmaker (note if you do not have or use FieldMaker then you may skip this step).  Tools > System Utilities > FieldMaker Configuration, Processes tab and click the “Run Process” button.  A pop-up will appear saying all users must be out of FIMS to do the process.  Click yes to continue.  After the process completes, another pop-up will appear asking to rebuild the SQL views.  Click yes.  When this is complete, FIMS will automatically log back in and go to the main menu.
User-added image
  1. The upgrade is complete.  Close FIMS. 
  1. Upgrading the Test and Learn (also known as Demo) Database:
  1. The demo or test and learn database also needs to be updated.  Run the “copy live to demo” shortcut that is on the desktop.
  1. Clean Up
  1. Delete the “assemblies – copy” folder that was created in step 3 (npo\found\assemblies – copy).  Delete the upgrade file(s) (npo\temp).



Was this article helpful?