This post is used to list the known issues reported in the last version of BizTalk Health Monitor (currently the v2) and when possible workarounds.
You can let in this post your comments if you want to report new issues.
We will update periodically BHM to fix them and bring also new features.
Known issues:
When a user account is specified to schedule a BHM collect, the creation of the task returns the following error: "A specified logon session does not exist. It may already have been terminated".
The policy "Do not allow storage of passwords and credentials for network authentication" is maybe enabled preventing to create a task under a specific user account.
If it is a local policy and if you can disable it, follow these steps :
- Open the 'Local Security Policies' MMC
- Expand 'Local Policies' and select 'Security Options'
- Disable that property - the system must reboot for the change to take effect
BHM on a localized OS is hanging and crashing when creating a new monitoring profile.
The root cause was identified and fixed. We will release soon a post V2 update fixing that problem.
Users who want a temporary fix can contact JP (jpierauc@microsoft.com).
When we create a monitoring profile targeting a BizTalk group not accessible by the logged-on user, the console is crashing.
During the creation of a profile, BHM connects to the Mgmt db of the targeted group to retrieve the list of BizTalk servers of that group - this list will be used in the performance nodes.
This connection attempt made under the interactive logged-on user account is failing because this user does not have rights on the Mgmt Db, and this error is not well catched.
We will release soon a post V2 update allowing to specify the user account in the new profile dialogbox and managing better connection errors.
You should be able workaround that issue by editing manually an XML profile file following the steps below :
- Duplicate an existing profile using the new "duplicate profile" menu item
- open a CMD window under elevated admin priviledge
- in this cmd change the folder to "c:\programdata\Microsoft\BizTalk Health Monitor"
- open in notepad the XML file corresponding to this duplicated profile
- modify in this xml file the value of MGMTDBSERVER and MGMTDBNAME properties to specify the location of the new Mgmt db you want to target
- modify the value of the "DEFAULTBTS" property entering the name of one BizTalk server of that new targeted group
- modify the value of the "ALLBTS" property entering this same BizTalk server or the complete list of all your BTS of the new targeted group, ex : Value="BTSRV1:True:True:True, BTSRV2:False:False:True"
- save the xml file
- Open BHM console : you should see then the new profile listed
- Display the Settings dialogbox of the new profile and specify the user to run the collect as