none
BizTalk 2016 CU5 – 64 bit host instances refuse to start RRS feed

  • Question

  • Summary

    We’ve encountered a strange issue, after what looked like connectivity connection error to the BizTalk databases which caused some of the host instances to restart, some of the 64 bit hosts did not restart and trying to start manually them failed instantly. Restarting a 64 bit host that appeared to be running state resulted in it failing as well. After a server reboot, all of the 64 bit hosts failed to start but the 32 bit ones were fine.

    Does anyone have any clues as to what the issue could be and how to resolve it? Please read what we checked / tried first though.

    Error

    Failed to start the BizTalk Host instance. Check the event log on the server “* ” for more details.
    Internal error: “The service did not respond to the start or control request in a timely fashion.” (WinMgmt)

    What we checked / tried

    Checked that no patches had been applied (not since March) and nothing new had been installed. The only odd things was that BizTalk was showing has having been installed on that day in Add / Remove programs.

    Tried creating a new 64 bit host and host instance (same error on start).

    Checked that BTSNTSvc64.exe.config & BTSNTSvc.exe.config had not been changed or corrupted

    Check that both the 64 and 32 machine config had not changed.

    Rebooted the server

    Restarted MSDTC on the SQL Server.

    DTCP Ping showed no connection issues

    Detailed Error

    Text from the above error

    Starting instance of host ********* on server ******** failed.

    ------------------------------
    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=HostInstance_UnmapServerHostInstanceFailed

    ===================================

    Failed to start the BizTalk Host instance. Check the event log on the server "*******" for more details.

    Internal error: "The service did not respond to the start or control request in a timely fashion." (WinMgmt)

    ------------------------------
    Program Location:

       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
       at Microsoft.BizTalk.SnapIn.Framework.WmiProvider.Invoke(ManagementObject instance, String command)
       at Microsoft.BizTalk.Administration.SnapIn.Nodes.HostInstanceNode.OnStart(Object sender, EventArgs e)

    Tuesday, August 27, 2019 3:43 AM

Answers

  • The Escalation Microsoft Engineer used the following tools to attempt to diagnose the issue

    In Process Monitor we could see that it was loading the 32 bit DLLs from the folder C:\Program Files (x86)\Microsoft BizTalk Server 2016\Bins32 but not the 64 bit ones.

    The issue was that the C:\Program Files (x86)\Microsoft BizTalk Server 2016\Bins64 was missing from the System Variable Path. Adding it back in resolved the issue

    Monday, September 2, 2019 8:28 PM

All replies

  • That's a generic WinMgmt error saying it couldn't start the service, without giving you anything substantial to look into!

    Aside from the Windows Event Log, I don't think there is much else you can do to try and get useful information out.  You have a bit of a lead that it is impacting 64-bit instances, but nothing very tangible.  My guess would be something has gone wrong with a 64-bit version of a dependent component, but tracking that down would be time consuming and largely luck based.

    You could using things such as DebugView and ProcessMonitor to try and see if anything useful gets spewed out.  I'd probably cut my losses and mark this one up as a good time to practice your DR plan and rebuild your node! :)


    If this is helpful or answers your question - please mark accordingly.
    Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)
    Read my articles on: BizTalk | .NET

    Wednesday, August 28, 2019 1:00 PM
  • The Escalation Microsoft Engineer used the following tools to attempt to diagnose the issue

    In Process Monitor we could see that it was loading the 32 bit DLLs from the folder C:\Program Files (x86)\Microsoft BizTalk Server 2016\Bins32 but not the 64 bit ones.

    The issue was that the C:\Program Files (x86)\Microsoft BizTalk Server 2016\Bins64 was missing from the System Variable Path. Adding it back in resolved the issue

    Monday, September 2, 2019 8:28 PM