I came across an issue in which we were not able to launch BizTalk Admin console in BizTalk Server 2009.
On launching the Admin console and expanding the groups, we were getting the following error:

NullReferenceException
  at
Microsoft.BizTalk.ExceptionMessageBox.BtsExceptionMessageBox.ReprocessManagementException(Exception exception, Exception newInnerException)
   at
Microsoft.BizTalk.ExceptionMessageBox.BtsExceptionMessageBox.ReprocessSpecificExceptions(Exception exception, Exception newInnerException)
   at
Microsoft.BizTalk.ExceptionMessageBox.BtsExceptionMessageBox.ReprocessExceptionRecursive(Exception exception)
   at
Microsoft.BizTalk.ExceptionMessageBox.BtsExceptionMessageBox.set_Message(Exception value)
   at
Microsoft.BizTalk.ExceptionMessageBox.BtsExceptionMessageBox..ctor(Exception exception, ExceptionMessageBoxButtons buttons, ExceptionMessageBoxSymbol symbol)
   at
Microsoft.BizTalk.SnapIn.Framework.FrameworkNotification.Show(Exception exception, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, Control staMarshaller, IWin32Window parent)
   at
Microsoft.BizTalk.SnapIn.Framework.FrameworkNotification.ShowError(Exception exception, Control staMarshaller, IWin32Window parent)
   at
Microsoft.BizTalk.SnapIn.Framework.FrameworkNotification.ShowError(Exception exception)
   at
Microsoft.BizTalk.Administration.SnapIn.GroupNode.FullRefresh(Object o, ResultsChangedEventArgs e)
   at
Microsoft.BizTalk.Administration.SnapIn.GroupNode.OnExpand(AsyncStatus status) 
   at
Microsoft.ManagementConsole.NodeSyncManager.ProcessRequest(NodeRequestInfo info, IRequestStatus requestStatus)
   at
Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessRequest(Request request) 
   at
Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request)
   at
Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at
Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at
Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
   at
Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest() 
   at 
Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
 

On doing some further research, we found that the error was occurring because the WMI Namespace was not valid:
Inner Error = Invalid namespace
   at
Microsoft.BizTalk.SnapIn.Framework.WmiProvider.get_ServerScope() 

We rebuild BTS WMI Namespace as follows:
mofcomp BTSWMISchema.mof 
BTSWMISchema.mof is located in bins32 folder under BTS install location mofcomp is located at c:\windows\system32\wbem 

It may happen that the following command may not be recognized in that case you can run the following command:
mofcomp "C:\Program Files (x86)\Microsoft BizTalk Server 2009\Bins32\BTSWMISchema.mof

Then we were successfully able to expand the groups. 

I am including the generic BizTalk-WMI troubleshooting steps below :

Try a WMI test from the BizTalk server:
Go to Start >> Run and type in ‘WBEMTEST’ , Hit Enter.
Windows Management Instrumentation Tester screen will open up.
Hit Connect
On the connect screen set the namespace as “root\MicrosoftBiztalkServer” as shown below and hit Connect.

Hit Query now:



Provide the same query which failed as per the event log entry:
SELECT * FROM MSBTS_GroupSetting WHERE Name = 'BizTalk Group'

If the outcome was failure, try the below action plan on the BizTalk Servers:

  • Re-register the BTSWMIProvider.dll file by using the following method:
  • For 64-bit: Click Start, click Run, type the following command, and then click OK:

Regsvr32.exe "C:\Program Files (x86)\Microsoft BizTalk Server 2006\Bin32\BTSWMIProvider.dll"
Please check whether this path is correct on your machine. 

  • Run the MOF command prompt to register the MOF schema. To do this, follow these Steps:
    • Open a command window
    • For 64-bit, go to C:\Program Files (x86)\Microsoft BizTalk Server 2006\Bins32
    • Type the following command at the command prompt:
      mofcomp.exe BTSWMISchema.mof
      mofcomp.exe BTSWMISchema.mfl
  • Restart WMI service 

Hope this helps.. !!

 

Written BY
Rasika Chaudhary

Reviewed BY
Jainath V R

Microsoft GTSC India