BizTalk Server Administration Console cannot connect to WMI provider. Ensure that the WMI service is running. (Microsoft.BizTalk.SnapIn.Framework)

  • Sandro Pereira
  • Sep 14, 2017
  • 4 min read

BizTalk Server Administration Console cannot connect to the WMI provider. The things I found from playing around with all kind of different environments from different clients and my personal ones (Hehe)… and I thought that I had already found all type of real or imaginary BizTalk errors, but once again I BizTalk Server prove me that I was wrong, this issue was new for me – who says that my BizTalk Consultant life is boring? (hehe).

Joking apart, I got the following error while trying to navigate in the BizTalk Server Administration Console in one of my personal environments:

TITLE: BizTalk Server Administration
——————————
Failed to load Group [BTS2016LAB01:BizTalkMgmtDb] data providers. (Microsoft.BizTalk.Administration.SnapIn)

For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2016&ProdVer=3.12.774.0&EvtSrc=Microsoft.BizTalk.Administration.SnapIn.Properties.Errors&EvtID=FailedLoadingGroupProviders&EvtChain=Microsoft.BizTalk.Administration.SnapIn.Properties.Errors+%2cFailedLoadingGroupProviders%3bMicrosoft.BizTalk.SnapIn.Framework.Properties.ErrorMessages+%2cConnectToWMIProviderFailed
——————————
ADDITIONAL INFORMATION:
Failed to load Group [BTS2016LAB01:BizTalkMgmtDb] data providers. (Microsoft.BizTalk.Administration.SnapIn)

For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2016&ProdVer=3.12.774.0&EvtSrc=Microsoft.BizTalk.Administration.SnapIn.Properties.Errors&EvtID=FailedLoadingGroupProviders&EvtChain=Microsoft.BizTalk.SnapIn.Framework.Properties.ErrorMessages+%2cConnectToWMIProviderFailed
——————————
Cannot connect to WMI provider. Ensure that the WMI service is running. (Microsoft.BizTalk.SnapIn.Framework)

For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2016&ProdVer=3.12.774.0&EvtSrc=Microsoft.BizTalk.SnapIn.Framework.Properties.ErrorMessages&EvtID=ConnectToWMIProviderFailed
——————————
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422) (System.Management)
——————————
BUTTONS:
OK
—————————–

BizTalk Server Administration Console cannot connect to WMI provider

📝 One-Minute Brief

BizTalk Server Administration Console relies on the BizTalk WMI Provider and the Windows Management Instrumentation (Winmgmt) service. If Winmgmt is disabled or stopped, the console fails to load the group and shows “Cannot connect to WMI provider.” This guide explains the root cause and the quick fix: enable and start Winmgmt so the console can query the BizTalk environment again.

Cause

The reason the BizTalk Server Administration Console cannot connect to the WMI provider is that the BTS Administration Console relies on the Windows Management Instrumentation (WMI) service, specifically the BizTalk WMI Provider (BTSWMIProvider.dll), to perform queries across the BizTalk Environment (or BizTalk databases).

And for that reason, the Windows Management Instrumentation (Winmgmt) service needs to be enabled and running on the server on which you are running the BizTalk Server Administration Console.

In my case, the problem was that while I was investigating unnecessary services I could disable to optimize BizTalk Server performance, I disabled an important service.

Solution

As I mentioned above, the solution to this problem is to enable and start the Winmgmt service. You can accomplish that by:

  • If the service is Disabled:
    • Press the Windows key to open the Start menu, type Services, and click on the View local services option from the Search window.
    • In the Services window, on the Services (Local) panel, select the Windows Management Instrumentation service, right-click, and select the Properties option.
      • On the Windows Management Instrumentation Properties (Local Computer) window:
      • On the General tab, apply the following configuration.
      • Startup type: Automatic.
      • And then click Start and Apply.
BizTalk Server Administration Console cannot connect to WMI provider: Winmgmt service
  • If the service is enabled, you can simply:
    • Open a command prompt as an administrator by pressing the Windows key to open the Start menu, typing cmd in the Start Search box, right-clicking on Command Prompt, and selecting the Run as administrator option from the context menu.
    • And type the following command: net stat winmgmt
BizTalk Server Administration Console cannot connect to WMI provider: Winmgmt service running

Once the Winmgmt service is running, you will be able to use the BizTalk Server Administration Console without this error/problem happening.

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.

1 thought on “BizTalk Server Administration Console cannot connect to WMI provider. Ensure that the WMI service is running. (Microsoft.BizTalk.SnapIn.Framework)”

  1. Nice try, no cigar. We get that same message after bringing up BTAC BUT only if we select Adapters, and an adapter tab like say FTP [really doesn’t matter which one]. It will allow you to move past the initial error but then invokes WMI error when in the configuration pull down for Hosts and ADD you get that 2nd error.
    As you I have three environments of which they are as about exact clones of each other [we’ve done PS scripts to compare KB updates patches etc.] AND one environment has zero problems, and middle one has this error.
    We’ve de-installed some KB updates and reapplied after boot and same results.
    We KNOW it’s due to some update as fine before the push out.
    As you, we had ‘intermittent’ results…sometimes worked all the way then bingo, errors.

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