Problems installing Biztalk2020 CU1

Copper Contributor

Just yesterday we tried to upgrade our new BTS2020 dev environment to CU1. Installation went through without problems, but after the installation Biztalk Admin Tool mmc-plugin fails to load with error below. Same happens if the MMC is opened separately and they trying to add the Biztalk Server add-in.

 

The problem started when installing CU1 with VS plugin, all changes were removed and it was fixed. Reinstalling the CU1 only made it happen again and removing it fixed the situation again. Has anyone else faced anything like this?

 

We are also receiving this error when trying to start Biztalk hosts. :

Error code: 0x80131534
Error source: Microsoft.BizTalk.CommonSettings
Error description: The type initializer for 'Microsoft.BizTalk.CommonSettings.CBizTalkSettingsLookup' threw an exception.

Also this problem is fixed as soon as CU1 is removed.

 

We were trying to install this to fix a problem with BTS2020 jobs, one fails with the error message Invalid column name 'uidServiceInstanceId', where it seemed it could be a collation issue in our database - something similar was fixed in Biztalk 2016 CU7-upgrade.

 

Error text for MMC:

 

Faulting application name: mmc.exe, version: 10.0.17763.1282, time stamp: 0x9eae7180
Faulting module name: KERNELBASE.dll, version: 10.0.17763.1369, time stamp: 0xb99aaceb
Exception code: 0xe0434352
Fault offset: 0x00122452
Faulting process id: 0x14cc
Faulting application start time: 0x01d69275d6dd21c4
Faulting application path: C:\Windows\SysWOW64\mmc.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 41426be9-6006-4a1b-8e75-52cae7d62349

Faulting package full name:
Faulting package-relative application ID:  

8 Replies

Hi @JariMy Thanks for reporting this. We need some details to debug this issue:

1. Is this single machine environment, where BizTalk, VS and SQL are all on same machine?

2. What BizTalk features are installed? What features are configured? Please attach screenshot of the features from Add Remove Program -> Modify.

3. In what sequence CU1 installation and VS extension update was performed?

@JariMy 

 

Looks like some assemblies were not properly upgraded by CU1 installation on your server. Please consider submit a support ticket to Microsoft for assistance on this. Basically we will need to look into the following two kinds of data to troubleshoot such issue:

 

1. The CU1 setup log.

2. Generate a dump of the crashed mmc with command like the following:

 

procdump -ma -e 1 -f "TypeInitializationException" <PID of mmc.exe found in task manager>

 

Procdump

https://docs.microsoft.com/en-us/sysinternals/downloads/procdump

 

@ParikshitGupta 

 

Thank you for your response!

 

  1. SQL is in separate AlwaysOnSQL cluster, BizTalk & VS in the same box

2) screen captures attached

3)

CU1 + ESB + VS, then all removed in reverse order. After that tested installing just CU1 and same issue. MMC and BizTalk hosts crash

Host crash

Log Name:      Application

Source:        BizTalk Server

Date:          24.9.2020 16.23.38

Event ID:      5410

Task Category: BizTalk Server

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <removed>

Description:

A failure occurred when executing a Windows service request.

 

 Service request: Start

 

 BizTalk host name: <removed>_Receive_DMZ

Windows service name: BTSSvc$<removed>_Receive_DMZ

 

 Additional error information:

Error code: 0x80131534

Error source: Microsoft.BizTalk.CommonSettings

Error description: The type initializer for 'Microsoft.BizTalk.CommonSettings.CBizTalkSettingsLookup' threw an exception.

 

MMC crash

Log Name:      Application

Source:        .NET Runtime

Date:          24.9.2020 16.29.56

Event ID:      1026

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <removed>

Description:

Application: mmc.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentNullException

   at Microsoft.BizTalk.Utilities.ARMClient.WebProxyWithSystemCredential..ctor(IWebProxy webProxy, NetworkCredentialCache networkCredentialCache)

   at Microsoft.BizTalk.Utilities.ARMClient.ProxyCache..ctor()

   at Microsoft.BizTalk.Utilities.ARMClient.ProxyCache..cctor()

 

Exception Info: System.TypeInitializationException

   at Microsoft.BizTalk.Administration.SnapIn.BtsSnapIn..ctor()

 

Exception Info: System.Reflection.TargetInvocationException

   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)

   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)

   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)

   at System.Activator.CreateInstance(Type type, Boolean nonPublic)

   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)

   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)

   at System.Activator.CreateInstance(String assemblyString, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)

   at System.Activator.CreateInstance(String assemblyName, String typeName)

   at System.AppDomain.CreateInstance(String assemblyName, String typeName)

   at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)

   at Microsoft.ManagementConsole.Internal.SnapInClient.CreateSnapIn(String assemblyName, String typeName)

   at Microsoft.ManagementConsole.Internal.ClassLibraryServices.Microsoft.ManagementConsole.Internal.IClassLibraryServices.CreateSnapIn(String assemblyName, String typeName)

   at Microsoft.ManagementConsole.Executive.SnapInInitializationOperation.OnStart()

   at Microsoft.ManagementConsole.Executive.Operation.Start()

   at Microsoft.ManagementConsole.Executive.RunningOperationsTable.EnqueueOperation(Operation operation)

   at Microsoft.ManagementConsole.Executive.StandAloneComponentData..ctor(SnapInRegistrationInfo info, Int32 bookkeepingId)

   at Microsoft.ManagementConsole.Advanced.FrameworkSnapInFactory.Microsoft.ManagementConsole.Advanced.ISnapInFactory.CreateSnapIn(Int32 bookkeepingId, String snapInKey, Object& snapIn)

 

Exception Info: System.Reflection.TargetInvocationException

   at Microsoft.ManagementConsole.Executive.MmcThreadMessageWindow.OnThreadException(Exception e)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.Run()

   at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.Microsoft.ManagementConsole.Internal.ISnapInMessagePumpProxy.Run()

   at Microsoft.ManagementConsole.Internal.ISnapInMessagePumpProxy.Run()

   at Microsoft.ManagementConsole.Executive.SnapInThread.OnThreadStart()

   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)

   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

   at System.Threading.ThreadHelper.ThreadStart()

--------------------------

Log Name:      Application

Source:        Application Error

Date:          24.9.2020 16.29.56

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <removed>

Description:

Faulting application name: mmc.exe, version: 10.0.17763.1282, time stamp: 0x9eae7180

Faulting module name: KERNELBASE.dll, version: 10.0.17763.1369, time stamp: 0xb99aaceb

Exception code: 0xe0434352

Fault offset: 0x00122452

Faulting process id: 0x24a0

Faulting application start time: 0x01d69276c9b23a7f

Faulting application path: C:\Windows\SysWOW64\mmc.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: f5c221fa-a110-4b99-a234-d2d54d1055f8

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2020-09-24T13:29:56.409582200Z" />

    <EventRecordID>7199</EventRecordID>

    <Channel>Application</Channel>

    <Computer><removed></Computer>

    <Security />

  </System>

  <EventData>

    <Data>mmc.exe</Data>

    <Data>10.0.17763.1282</Data>

    <Data>9eae7180</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>10.0.17763.1369</Data>

    <Data>b99aaceb</Data>

    <Data>e0434352</Data>

    <Data>00122452</Data>

    <Data>24a0</Data>

    <Data>01d69276c9b23a7f</Data>

    <Data>C:\Windows\SysWOW64\mmc.exe</Data>

    <Data>C:\Windows\System32\KERNELBASE.dll</Data>

    <Data>f5c221fa-a110-4b99-a234-d2d54d1055f8</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Thank you for this!
We'll start working with this as well.

Thanks @JariMy for the details. We could not reproduce it. We rule out any generic CU1 installation issue. Reach out to support with CU setup logs for further analysis. Please post file version of these files in BizTalk installation folder and GAC on your machine after CU1 installation(expecting it to be 3.13.759.0 in both GAC and installation directory):

Microsoft.BizTalk.Utilities.ARMClient.dll

Microsoft.BizTalk.CommonSettings.dll

Microsoft.XLANGs.BaseTypes.dll

@ParikshitGupta Hello, I have the same problem and I can confirm that these assemblies have the same version (3.13.759.0) both in GAC and in the installation folder.

 

Best regards, Igor

@IgorMilavec  We ended up opening a support ticket and we were able to solve the situation. The people in this thread helped as and tried to narrow it down but they weren't able to reproduce it.

 

In our case default proxy was disabled (<defaultProxy enabled="false" ..) in machine configuration files. For the CU there was a change on how the default proxy is utilized in the WCF ports. 

We removed the section from the machine.config files (both bit-versions) and were able to install the CU1 and after that MMC and BTS Hosts started working. 

After further tests there seems to be two possible working configurations for this:

a. defaultProxy is enabled at machine.config(s)

b. defaultProxy is not enabled at machine.config but are enabled at the BTSNTSvc.exe.config (both bit versions) and mmc.exe.config  files. 

 

I have no idea if this helps in your case, but that's the end result of ours. I must say the handling of the support ticket was superb from the MS team. 

 

Best of luck!

Hi @JariMy ,

 

thank you for the information. In our case the default proxy was disabled in the BTSNTSvc.exe.config. After removing the configuration setting I was able to start BizTalk service.

 

Thank you and best regards, Igor