How to upgrade BizTalk Health Monitor from a previous version to the latest one

  • Sandro Pereira
  • Apr 8, 2015
  • 4 min read

BizTalk Health Monitor (BHM) is a BizTalk snap-in that can be added to the existing BizTalk Administration Console or can be run individually, which helps you monitor the health of your BizTalk Server environment. Basically, it’s similar to the “old” BizTalk MsgBoxViewer tool that we used to monitor a BizTalk environment by gathering all information of a BizTalk group and detecting any issues, non-critical or critical warnings, to detect any potential problems in advance.

BHM is now in its third version, released on March 6, 2015, which you can download here.

The goal of this post is not to explain what the BizTalk Health Monitor is, but instead, if you already have a previous version – V1 or V2 – how can you update to the latest one – V3. Do you need to uninstall the previous one?

Note: If you don’t have a previous version of BizTalk Health Monitor installed, then check the post to describe the installation steps required.

📝 One-Minute Brief

Upgrading BizTalk Health Monitor (BHM) is not an automated process via an installer; it requires a manual “swap” of the binary files. This guide walks you through downloading the latest version, replacing the existing files in your installation folder, and re-registering the MMC snap-in to ensure you have the latest performance and health-check rules.

How to upgrade BizTalk Health Monitor to the latest version

Basically, you don’t need to uninstall V2 (or V1) to upgrade to the latest version, you just need to register the snap-in of the new one but there are some considerations that you need to be aware.

  • First, if you have BizTalk Health Monitor integrated with the BizTalk Administration Console you need to close all the BizTalk Administration Console in all sessions, if not you need to close BizTalk Health Monitor in all sessions again, otherwise you cannot replace or delete the existing files.
Error While replacing BHM files

Note: You shouldn’t replace or create a new BHM folder under C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\SDK\Utilities\Support Tools otherwise you will have issues installing BizTalk cumulative updates.

  • After closing all consoles, choose a proper location in your drive, for example:
    • C:\Program Files (x86)\Microsoft BizTalk Server Support Tools\BizTalkHealthMonitor
  • And unzip the version of the BHM zip file to this folder
    • You could also replace the existing files with the new ones; however, I already encountered some issues while registering the new version of the snap-in after doing that.
    • Or you can create a new folder with these new resources.

Note: Once you register the BizTalk Health Monitor Snap-In you cannot delete or change the folder path or BHM will stop working.

  • Open a command prompt as an administrator
  • Navigate to the directory folder where you have the BHM resources
    • For example: C:\Program Files (x86)\Microsoft BizTalk Server Support Tools\BizTalkHealthMonitor.
  • And from the command prompt type:
    • InstallUtil.exe MBVSnapIn.dll
  • And hit enter. This step will register the new version of the Snap-In to be used

Because you already added the BizTalk Health Monitor integrated with the BizTalk Administration Console, you don’t need to do anything more. Just open the BizTalk Administration Console, and the latest version of the BHM will be available.

BizTalk Administration Console BHM V3

Notes:

  • If you replace the existing BHM files with the new ones and then try open the BizTalk Administration Console without registering the new BHM version, you will receive the following error:
    • MMC has detected an error in a snap-in and will unload it.
BHM MMC detected error snap in unload it
  • If you replace the existing BHM files with the new ones and you find some kind of error while trying to register the snap-in, then:
    • Delete all files from the directory and then copy the files to the new BHM version again to the folder.
    • And register the BHM span-in again.

Important Note: If you already replaced some files under C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\SDK\Utilities\Support Tools\BizTalkHealthMonitor or created a new BHM folder under C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\SDK\Utilities\Support Tools, you should:

  • Move the BHM folder to a place outside the C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\SDK\Utilities\Support Tools folder, for example, to the suggested path described above.
  • Register the BHM Snap-In from this directory.
  • And delete all the BHM folders under the Utilities folder.

Otherwise, you will have issues installing BizTalk cumulative updates.

Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son. 

Thanks for Buying me a coffe
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

4 thoughts on “How to upgrade BizTalk Health Monitor from a previous version to the latest one”

  1. Hey Sandro, do you know how to contact the guys from BizTalk Heaslth Monitor? With the last update (4.5) the mail notification does not seem to work anymore and I want to inform them of that (index out of range msg).

    1. I may have, send me an email with the error details and I will forward it to them. But the best way for that to be fixed is to create a bug report.

  2. Hello Sandro,

    Yes i was totally stuck with this and luckily found this highlighted here.

    We recently updaged BHm to V4.5 and email notification seems not working, however the TEST option triggers successfully.

  3. Hi, I am also getting the same error after the update to 4.5 any news on this issue?

    How to know the difference between the 4.3 to 4.5 version where to find it?

Leave a Reply

Your email address will not be published. Required fields are marked *

The Ultimate Cloud
Management Platform for Azure

Supercharge your Azure Cost Saving

Learn More
Turbo360 Widget

Back to Top