MonitorPro System Update Check List

A check list outlining the general steps required when updating MonitorPro including; MP Desktop, MP Web, MP Service and databases.

The following is based on a full MonitorPro system update, for Desktop only systems simply skip the MP Web elements. This is not intended as full installation guide, for detailed instructions please refer to the appropriate sections in the knowledge base.

Prerequisites

General 

  • Latest update files downloaded from https://ehsdata.com/support/
  • Suitable rollback/disaster recovery plan in place, as a minimum backups of the databases should be taken prior to update, a copy of the MP Web website root folder, and previous version installers for MP Desktop and Service. 
  • Ensure suitable access to the entire environment MonitorPro is installed on to deploy updates correctly. 

Application Server

  • Ensure .NET Framework 4.8 is installed.

Web Server

  • Ensure .NET Framework 4.8 is installed.
  • Ensure .NET Framework 8.0 Hosting Bundle
  • Ensure URL Rewrite Module is installed.

Check List

Step

Complete?

Stop MonitorPro Service on application server and MonitorPro Web on the web server.

 

In SQL Server Management Studio login to the database with an account which has DBO access to the MonitorPro databases (Data and Gateway). Execute the DataDB_Update.sql against the MonitorPro data database(s). Ensure it completes without errors. 

Note: When updating to version 19 you will need to set the culture for the database, this is done once and stored in the database going forward and can not be changed. 

 

Execute the GatewayDB_Update.sql against the MP5WebGateway and ensure it completes without errors. 

 

If databases have updated successfully proceed to updating app and web servers, otherwise contact support@ehsdata.com with the reported SQL errors. 

 

On the application server ensure MonitorPro Desktop is closed and no associated MonitorPro tasks are running (check in task manager for Monitor.exe or processes starting MP5). 

 

Run the MP Desktop Update Setup.exe and follow the on screen prompts to completion. If you're updating to version 19.0, MP Desktop will need to be uninstalled prior to running the version 19.0 installer.

 

Launch MP Desktop and ensure it connects to the database without issue. If it hasn't been updated correctly it will provide a version mismatch warning. 

 

Run the MonitorProServiceSetup.exe and follow the on screen prompts to completion. 

 

Start the MP Service, this should connect to the databases using the previous configuration. If it's unable to start or connect to the databases check the account running the service under Windows Services. 

 

Update the MonitorPro Desktop client on end users machines. As mentioned above if updating to version 19 any earlier version will need to be uninstalled. 

 

Ensure copy of the MP Web folder is taken, as mentioned above, you will require details from the old web.config. 

 

Delete contents of the MP Web folder except for the reports folder. 

 

Unzip contents of the MPWeb_Version.zip and copy contents of EHS.MPWeb-version folder into the now empty MP Web folder above, minus reports. 

 

Open the AppSettings.json in notepad and the AppSettings.json in the copy taken before. If you're updating from version 18 or earlier you'll need to open the web.config in the copy.

 

Find the section "connectionStrings" and update the server=SERVERNAME with the server name from the copy. You may also need to update the Database=MP5WebGateway field if the database has been renamed. 

 

Depending on the authentication model you'll need to do either, set the Trusted_Connection to True if using Windows authentication to the connect to the databases, or set the username and password for SQL authentication. 

 

If additional appSettings have been configured in the old web.config these will also need copying over as required. Save and close the config. 

 

In IIS expand the MP Web website, find the Reporting folder, right click and convert application with the default settings.

 

Restart the website in IIS and ensure it's accessible and running.