Implementations - 1.5.1 to 2.1 u X Upgrade Steps (Manitou)

12/21/2023 11:29 am EST

image.png

Prerequisites:

  • Verify the VC_Redist ran or the Upgrade_XXX.exe.
  • Take a backup of the current Database.
  • Make a copy of the Manitou directory and rename it with the current version.
  • Have operators write down some recent alarms or customer changes that have been made. After the upgrade operators will need to verify that those changes are still present before starting the FEP.
  • Take a screenshot of the FEP Commander to quickly identify which receivers are not coming up if any after the upgrade.
  • Take a screenshot of the license information for the server, as you will have to licence with the 2.1 License Manager.


Upgrade Procedure:

  1. Push out package 3, this will put the upgrade files in the manitou directory.
  2. Push the 2.1 Patch out to the server and appropriate workstations.
  3. Prepare the 2.1 and 1.6.4 DBManager File Swap Folders:
    • Navigate to the Manitou Directory on the Primary Manitou Server.
    • Create a new folder in this directory, naming it similarly to DBM Files 2.1
    • Create another folder in this directory, naming it similary to DBM Files 1.6.4
    • From the Manitou Directory locate the Following Files:
      • DBMANAGER.EXE
      • MANITOU.DATABASEMIGRATIONS.DLL
    • Copy both of these files into the DBM Files 2.1 Folder
    • Extract the 1.6.4-DBM-Swap-Files.zip folder acquired earlier
    • Copy or move these files into the DBM 1.6.4 Folder that was created earlier
  4. Downgrade the DBManager to 1.6.4 version
    • Close any open DBManager applications
    • Open the DBM Files 1.6.4 folder
    • Select the following files:
      • DBMANAGER.EXE
      • MANITOU.DATABASEMIGRATIONS.DLL
    • Copy these files into the %/Program Files (x86)/Bold Technologies/Manitou directory
    • Approve the prompt to Replace Existing Files
  5. Rename the sqlbold.dll file int the Manitou directory newsqlbold.dll
  6. From the backup you took of the Manitou directory copy the sqlbold.dll into the now patched 2.1 directory
  7. Run the Upgrade_151.exe once, verify it completes then move on.
    • The 1.5.2 upgrade will only affect the current month and last month in the database. BObjects will need to be updated via normal upgrade procedures.
  8. Run the Upgrade_152.exe, once it crashes go into SSMS and edit the moptions table:
    • Change line 100 OPTCHAR to 1.5.1 and line 119 to 11 where its = 3
  9. Run the following script to work through all the CLOG tables:
DECLARE @CLOGTable as nvarchar(10);
DECLARE @SQLString as nvarchar(1024);

SET NOCOUNT ON;

DECLARE CLOG_Cursor CURSOR FOR
    SELECT NAME FROM SYSOBJECTS WHERE XTYPE = 'U' AND NAME LIKE 'CLOG%' ORDER BY NAME DESC

OPEN CLOG_Cursor
	FETCH NEXT FROM CLOG_Cursor
		INTO @CLOGTable
	WHILE (@@FETCH_STATUS = 0)
	BEGIN
		PRINT 'Processing Table: ' + @CLOGTable;

		--// Entity SUBTYPE value moved from QUAL5 (VarChar) to QUAL8 (SmallInt)
		SET @SQLString = N'UPDATE ' + @CLOGTable + N' '
			+ N'SET ' + @CLOGTable + N'.QUAL8 = (SELECT MANITOU..CONTACT.SUBTYPE '
			+ N'	FROM MANITOU..CONTACT '
			+ N'	WHERE MANITOU..CONTACT.CONTTYPE = ' + @CLOGTable + N'.QUAL2 AND MANITOU..CONTACT.SERIALNO = ' + @CLOGTable + N'.QUAL3) '
			+ N'WHERE ' + @CLOGTable + N'.EVTYPE = 3 AND ' + @CLOGTable + N'.QUAL = 1 ';
		EXECUTE sp_executesql @SQLString;

		SET @SQLString = N'UPDATE ' + @CLOGTable + N' '
			+ N'SET ' + @CLOGTable + N'.QUAL8 = ' + @CLOGTable + N'.QUAL5 '
			+ N'WHERE ' + @CLOGTable + N'.EVTYPE = 3 AND ' + @CLOGTable + N'.QUAL = 1 AND ' + @CLOGTable + N'.QUAL8 = NULL ';
		EXECUTE sp_executesql @SQLString;

		SET @SQLString = 'UPDATE ' + @CLOGTable + ' '
			+ N'SET ' + @CLOGTable + N'.QUAL5 = NULL '
			+ N'WHERE ' + @CLOGTable + N'.EVTYPE = 3 AND ' + @CLOGTable + N'.QUAL = 1 ';
		EXECUTE sp_executesql @SQLString;
		
		--// Capture CONTID into the agency reference comment CLOG records - used by reports for selection criteria (i.e., Custom Police)
		SET @SQLString = 'UPDATE ' + @CLOGTable + ' '
			+ N'SET ' + @CLOGTable + N'.KEYALM = (SELECT MANITOU..AUTHORITY.CONTID '
			+ N'	FROM MANITOU..AUTHORITY '
			+ N'	WHERE MANITOU..AUTHORITY.SERIALNO = ' + @CLOGTable + N'.QUAL3) '
			+ N'WHERE ' + @CLOGTable + N'.EVTYPE IN (27,28,37) ';
		EXECUTE sp_executesql @SQLString;
		
		FETCH NEXT FROM CLOG_Cursor
			INTO @CLOGTable
	END
CLOSE CLOG_Cursor
DEALLOCATE CLOG_Cursor

PRINT 'Done.'

SET NOCOUNT OFF;


  1. Run the Upgrade_153.exe twice.
    • Run the upgrade with "Skip previous CLOGs" checked
    • Run the CLOG upgrade
  2. Run the Upgrade_160.exe once, verify completion
  3. Run the Upgrade_161.exe twice
    • Run the upgrade only
    • Run the history upgrade.
  4. In the Manitou Directory rename the following files:
    • Rename SQLbold.dll to oldSQLbold.dll
    • Rename newSQLbold.dll to sqlbold.dll
  5. Launch the 1.6.4 DBManager application via the shortcut on the desktop
  6. Open the appropriate Configuration File for the DBManager already created on the server, or create one if necessary.
  7. Select the Database Updates tab on the left
  8. Select the appropriate Database from the drop-down menu
  9. Verify the Database Update Type is 1.6.4.x version
  10. Select Apply to run the Database Update
  11. When the update is complete the Apply button will re-appear
  12. Select the Health Check tab on the left
  13. Select the appropriate Database from the drop-down menu
  14. Click the Magnifying glass in the Schema File field.
  15. Select the 1.6.4 Manitou_Schema file that is located in %/Program Files (x86)/Bold Technologies/Manitou/DBM Files 1.6.4/
  16. Select Check Database to perform the Health Check
  17. After all entries have populated, select all entries
  18. Filter by remove table and un-check all Remove Table entries
  19. Filter by remove index and un-check all Remove Index entries
  20. Remove filtering to again show All items
  21. Select Apply Changes to complete the approved functions
  22. Wait for the health check to complete
  23. Select Check Database and verify the only entries remaining are the Remove Entries that were excluded earlier
  24. If any non-removal entries are present, select and apply them
  25. Close the DBManager Application
  26. Open the DBM Files 2.1 folder
  27. Select the following files:
    • DBMANAGER.EXE
    • MANITOU.DATABASEMIGRATIONS.DLL
  28. Copy these files into the %/Program Files (x86)/Bold Technologies/Manitou directory
    • Approve the prompt to Replace Existing Files
  29. Launch the 2.1 DBManager application via the shortcut on the desktop
  30. Open the same configuration file used earlier with the 1.6.4. DBManager
  31. Select the Database Updates tab on the left
  32. Select the appropriate Database from the drop-down menu
  33. Verify the Database Update Type is 2.1.x version
  34. Select Apply to run the Database Update
  35. When the update is complete the Apply button will re-appear
  36. Select the Health Check tab on the left
  37. Select the appropriate Database from the drop-down menu
  38. Click the Magnifying glass in the Schema File field.
  39. Select the current Manitou_Schema file that is located in %/Program Files (x86)/Bold Technologies/Manitou/Distributer/(Current Patch #)/
  40. Select Check Database to perform the Health Check
  41. After all entries have populated, select all entires
  42. Filter by remove table and un-check all Remove Table entries
  43. Filter by remove index and un-check all Remove Index entries
  44. Remove filtering to again show All items
  45. Select Apply Changes to complete the approved functions
  46. Wait for the health check to complete
  47. Select Check Database and verify the only entries remaining are the Removes that were excluded earlier
  48. If any non-removal entries are present, select and apply them
  49. Close the DBManager Application
  50. Open the Services.msc console
  51. Restart the Bold Monitor Service
  52. Install the 2.1LicenseManager Application
  53. Install the 2.1 License Client application
  54. License the customer with the values recorded earlier
  55. Launch the MSM
  56. Start All on the Broker
  57. Instruct Operators to login and verify recently handled alarms and customer changes recorded earlier
  58. If all entries are verified and OK proceed
  59. Start the FEP
  60. Start FEP Commander
  61. Verify all receivers are in the same status as before the upgrade

Post upgrade Tasks and Availability

After an upgrade from these versions it is imperative that Bold Technician remain connected to the system to verify normal function of all services and additional modules. If other modules need upgraded they should be handled after the Manitou Core installation is stable and all other workstations have been updated.


Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.

Copyright © 2024-26 Bold Group All rights reserved.