Here’s a great checklist for a BizTalk Adminstrator to install BizTalk:

by Tord Glad Nordahl


BizTalk Admin Console - Could not Create the Snap-In MMC

There might be many reasons for the above error, but here’s one we couldn’t find anywhere else.   We had a licensed copy of Windows 2008/R2, then realized we could save a license and use our MSDN subscription on this developer virtual machine.  So my worker upgrade to the Enterprise Developer edition.  That seemed to mess with BizTalk’s registry settings.  The secret to fix the above error for us was to run the BizTalk install and select the “repair” option.




This happens when you run an old .NET Framework 2.0 version of gacutil.exe against an assembly built with Framework 4.0.
Make sure you find and use the correct and latest version of GacUtil (you can see the disk path below).

NOTE: You can add a post-build event so that a .DLL is automatically GAC’ed each time you do a build:
“C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools&\gacutil” /i “$(TargetPath)”

Additional event log error: “Exception has been thron by the target of an invocation”
Error in BizTalk Admin Console: “Failed to start the BizTalk Host Instance. Check the event log on the server … for more details”.
Internal Error: “Unspecified erorr” (WinMgmt)

I’ve seen these errors before, and it’s always a problem with the config file. But today, I kept looking and looking and had trouble finding the problem.
I was adding <appSettings> and <connectionStrings> to my existing config file, as I had done many times in the past.

The difference this time is that I am on BizTalk 2010. And apparently with BizTalk 2010, these new tags have to go after all the default tags.
In older version of BizTalk, you could insert the new tags at the top, but basically now they have to go at the bottom, after the </xlangs> tag.