BizTalk : An internal failure occurred for unknown reasons
Issue 1:
TITLE: BizTalk Server Administration
——————————
An internal failure occurred for unknown reasons. (WinMgmt)
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2013+R2&ProdVer=3.11.158.0&EvtSrc=BTSAdminMsg&EvtID=9218
——————————
BUTTONS:
OK
——————————
Issue 2:
TITLE: BizTalk Server Administration
——————————
Failed to load Group [DBServer:BizTalkMgmtDb] data providers. (Microsoft.BizTalk.Administration.SnapIn)
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2013+R2&ProdVer=3.11.158.0&EvtSrc=Microsoft.BizTalk.Administration.SnapIn.Properties.Errors&EvtID=FailedLoadingGroupProviders&EvtChain=Microsoft.BizTalk.Administration.SnapIn.Properties.Errors+%2cFailedLoadingGroupProviders%3bBTSAdminMsg+%2c9218
——————————
ADDITIONAL INFORMATION:
Failed to load Group [DBServer:BizTalkMgmtDb] data providers. (Microsoft.BizTalk.Administration.SnapIn)
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2013+R2&ProdVer=3.11.158.0&EvtSrc=Microsoft.BizTalk.Administration.SnapIn.Properties.Errors&EvtID=FailedLoadingGroupProviders&EvtChain=BTSAdminMsg+%2c9218
——————————
An internal failure occurred for unknown reasons. (WinMgmt)
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2013+R2&ProdVer=3.11.158.0&EvtSrc=BTSAdminMsg&EvtID=9218
——————————
BUTTONS:
OK
——————————
Issue 3:
With above errors we are not able to open any host instance from BizTalk admin console.
After some analysis I found this is a bug which comes after security updates that were released by Microsoft on July 10, 2018. And this is coming on all version of BizTalk servers like BizTalk 2010, 2013, 2013 R2 and 2016.
Fix:
This issue is still unclear, and Microsoft is working on how to solve it. For now there are two work around that you can do for resolution.
Workaround 1: Uninstall the installed security update from BizTalk machine.
Here in my case for BizTalk 2013 R2, KB4338600 was the culprit. But if you want to know more about other BizTalk machines KB update list the Please check below useful article by Colin Dijkgraaf,
Workaround 2: Add local Network Service to the Administrators group.
Go to Groups => Administrators => Add local Network Service to the group and restart the Server
I would suggest please follow below MSDN thread where all BizTalk peoples posted there query and solution.
Please stay tune for latest update.