Introduction

This article is intended to be a knowledge base of all Errors and Warnings, Causes and Solutions documented in all stages/components of BizTalk: different stages of development, deployment, adapters, runtime, setup and configuration…

Visual Studio Orchestration Design Issues

The following are the known errors/issues associated to Visual Studio Orchestration Design:

Visual Studio Schema Design Issues

The following are the known errors/issues associated to Visual Studio Schema Design:

Visual Studio Mapper Design Issues

The following are the known errors/issues associated to Visual Studio Schema Design:
  • XSL transform error: (0,0) : Resolving of External URI’s was prohibited.
  • Cannot load source/destination schema: “schema_name”. Either the file/type does not exist, or if a project dependency exists, the dependent project is not built.
  • Value Cannot be Null. Parameter name: extension
  • The Messaging Engine failed while executing the inbound map for the message coming from source URL:"C:\*.csv" with the Message Type "<some message type>". Details:"An error occurred when parsing the incoming document: "'.', hexadecimal value 0x00, is an invalid character. Line 1, position 275.".
  • Error 23 Exception Caught: Mapper Compiler: Functoid not found: guid ({5DE500CC-45BC-454B-A23D-24449899042C}) with functoid id (6124).
    • It is usually associated with custom functoid, so you have to copy your functoid assembly to "%BTS%\Developer Tools\Mapping Extensions" folder, where %BTS% is the installation folder of BizTalk, to be able to use it in visual studio and then you have to GAC it to be able to use it during the run time.
  • BizTalk Server 2010: The Messaging Engine failed while executing the inbound map for the message coming from source URL:”...” with the Message Type “...”. Details:”Cannot find the script or external object that implements prefix ‘ScriptNS0′.
  • BizTalk Server 2013 Unit testing: "Transformation Failure".
    • or "The type initializer for 'Microsoft.BizTalk.ScalableTransformation.BTSXslTransform' threw an exception."
    • or "The type initializer for 'Microsoft.BizTalk.CommonSettings.CBizTalkSettingsLookup' threw an exception."
    • or "Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))"
    • Eventually I found a solution to this.  I added a test settings file to my solution and referenced this in the TEST menu so it was the active test settings.  When I did this running the test with the BizTalk Unit Testing feature and running the test using C# to execute the map both worked fine.  I didn't need to modify any settings in the test settings file, I just left them as the defaults.
  • "Exception Caught: Cannot use a prefix with an empty namespace" New!

BizTalk Visual Studio Common Issues

The following are the known common errors/issues associated to Visual Studio:
  • "Cannot generate serialization assembly {AssemblyName}.XmlSerializers.dll because it already exists. Use /force to force an overwrite of the existing assembly."
  • "Cryptographic failure while signing assembly 'assembly name here' — 'Access is denied.'"
  • “Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.BizTalk.Component.Interop.IComponentTypeInfo'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CF0480A5-F484-415b-AEC6-0AB44855758B}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))”
    • PipelineObjects.dll is a pipeline tool provided with BizTalk SDK to perform BizTalk Unit testing. The first thing that we do when using this utility is to create an instance of pipelinefactory and create pipeline using the below code. However from .net 4.0 onwards there has been a change in how .net calls the com component and now on, .net supports calling of com components using an entry in config file.
  • “Could not load file or assembly ‘file:///C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components\BREPipelineFrameworkComponent.dll’ or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded”. New!

BizTalk Debugging Issues

The following are the known errors/issues associated to Debugging BizTalk Solutions:
  • Tracking database doesn't have any records about the selected service instance yet.
    • I received this error when trying to debug an orchestration using the Orchestration Debugger option and it would just show the above message. Things I did were:
      • Enable global tracking, because that was turned off. 
      • Check all the tracking properties in the orchestration. 
      • Start the process keeping the orchestration in the enlisted state only (That would force suspend the orchestration)
      • Once it was suspended I resumed in debug mode.
      • Then it went into the running state with a status of "In Breakpoint(Active)"
      • Then right click the instance and click orchestration debugger and it worked.
    • More reading can be done here: Troubleshooting Orchestrations
  • Pipeline file name is already specified - Error 80131600.
  • Importing Binding Files: Failed to create 'WCF-Custom' Transport Component.  New!
    • This error occurred during the importation of one of the binding files remotely. The solution: The Windows Communication Foundation Adapter runtime should also be installed on the local machine (in our case TFS Build Server).

BizTalk Deploy Issues

The following are the known errors/issues associated to Deploying BizTalk Solutions:

BizTalk Adapters Issues

The following are the known errors/issues associated to BizTalk Adapters:
  • WCF: Exception: System.ServiceModel.ServiceActivationException: The service ‘/MyService/Service.svc��� cannot be activated due to an exception during compilation. The exception message is: That assembly does not allow partially trusted callers.. —> System.Security.SecurityException: That assembly does not allow partially trusted callers.
  • A message received by adapter "FILE" on receive location "Receive Location3" with URI "C:\...\In\*.xml" is suspended. Error details: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
  • The HTTP send adapter cannot complete the transmission within the specified time
  • "The operation has timed out", "Request timed out."
  • HTTP/SOAP:The underlying connection was closed: An unexpected error occurred on a receive.
  • FTP: Unable to receive the file
  • The one-way operation returned a non-null message with Action=”...".
    • A WSDL file with a true one-way operation results in a WCF client that expects an IsOneWay=true interaction pattern.  However, BizTalk doesn’t support true one-way interactions.  It supports operations that return no data (e.g. “void”) only.  So, by putting a hand-built WSDL that demanded an asynchronous service on a BizTalk receive location that cannot support it, we end up with a mismatch.
  • WCF-Oracle Transport Properties. Error loading properties. (System.MissingMethodException) Method not found: ‘System.Configuration.ConfigurationElement Microsoft.BizTalk.Adapter.Wcf.Converters.BindingFactory.CreateBindingConfigurationElement(System.String, System.String)’.
  • "E-PSFT0029: JVM was not started" or "Unable to find JAVA_HOME"
  • The adapter "WCF-Custom" raised an error message. Details "System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
  • The adapter failed to transmit message going to send port “WcfSendPort_SqlAdapterBinding_TypedProcedures_MyDB” with URL “mssql://MYSRVSQ01//MyDB?”. It will be retransmitted after the retry interval specified for this Send Port. Details:”Microsoft.ServiceModel.Channels.Common.MetadataException: Object [dbo].[uspInsertRecords] of type StoredProcedure does not exist
    • The above message can be quite confusing especially when the stored procedure does exist in your database. The above basically means the BT host account does not have execute permissions on the stored procedure being called. You need to restart the BT host instance after setting permissions.
  • The adapter failed to transmit message going to send port “WcfSendPort_SqlAdapterBinding_TypedProcedures_MyDB” with URL “mssql://MYSRVSQ01//MyDB?”. It will be retransmitted after the retry interval specified for this Send Port. Details:”System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object ‘uspInsertRecords’, database ‘MyDB’, schema ‘dbo’
    • If you are using a WCF SQL adapter in your solution, it is imperative to set permissions on the stored procedures you call from within BizTalk.
  • The adapter failed to transmit message going to send port “System.ServiceModel.ProtocolException: The content type text/xml of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly."
  • Microsoft.ServiceModel.Channels.Common.ConnectionException:Details: ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_LOON_FAILURE. SapErrorMessage=User account not in validity date. AdapterErrorMessage=.----> Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_LOON_FAILURE. SapErrorMessage=User account not in validity date.
  • Error details: The FILE send adapter cannot open file < > for writing. Details: Access is denied.
  • "A message received by the adaptor "<<Adapter type>>" on the received location "<<Receive Location Name>>" with the uri "<<Location path>>" is suspended. Operation was not executed because of previous failures".
    • You may have some more warnings/errors in the event log along with this error which may give some idea about the issue. Microsoft's suggestion: Check for other previous events in the event log. If the problem persists, please run trace and contact Support along with the Trace Dump
  • Failed to create ‘WCF-SQL’ Transport Component Microsoft.BizTalk.ExplorerOM.BtsException: Failed to create ‘WCF-SQL’ Transport Component
    at Microsoft.BizTalk.ExplorerOM.BtsCatalogExplorer.SaveChangesWithTransaction(Object transactionObj)
    at Microsoft.BizTalk.ExplorerOM.BtsCatalogExplorer.SaveChanges()
    • The main cause for this issue is due to the dependency on one of the run-time dll’s  (Microsoft.BizTalk.Adapter.WCF.Runtime.dll) that gets installed only when you install all the components of BizTalk Server. Since in our case we only installed BizTalk Admin components, that dll was missing in the server and hence the error.
  • Known Issues with the File Adapter
  • The Messaging Engine failed to add a receive location “XXX XXXX Relay Service Location” with URL “https://zzzzzzzz.servicebus.windows.net/httprelay/zzzzzservice” to the adapter “WCF-BasicHttpRelay”. Reason: “System.ServiceModel.CommunicationException: Unable to reach scabiztalkintegration.servicebus.windows.net via TCP (9351, 9352) or HTTP (80, 443)
  • Event Source: System.ServiceModel 3.0.0.0
    Description: WebHost failed to process a request. Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/20508338 Exception: System.ServiceModel.ServiceActivationException: The service '/service.svc' cannot be activated due to an exception during compilation.  The exception message is: Receive location for address "/service.svc" not found. (The BizTalk receive location may be disabled.). ---> Microsoft.BizTalk.Adapter.Wcf.AdapterException: Receive location for address "/service.svc" not found. (The BizTalk receive location may be disabled.)
  • System.Net.WebException: The operation has timed out New!
  • Windows cannot access \\path
    Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.
    Error code: 0×80004005 New!
    • The problem is not related to BizTalk layer, but to Windows Server 2012-based or Windows 8-based computer that fail to connect to a third-party file server that supports the SMBv2 file protocol. To allow the ports configured on multiple BizTalk hosts to works fine, you have to disable SMBv2 and SMBv3 protocol forcing the communications on SMBv1.
  • The Messaging Engine failed to add a receive location "name" with URL "URL" to the adapter "WCF-Custom". Reason: "System.PlatformNotSupportedException: Operation is not supported on this platform.
    at System.Net.HttpListener..ctor()
    at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
    at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
    at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
    at System.ServiceModel.Channels.HttpChannelListener.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)". New!
  • Source: BizTalk Server
    A response message sent to adapter "MLLP" on receive port "..." with URI "localhost:21000" is suspended.
    Error details: There was a failure executing the response(send) pipeline: "BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=1.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "BTAHL7 2.X Assembler" Receive Port: "..." URI: "localhost:21000" Reason: Message had parse errors, can not be serialized. New!
    • At the first sight, you may think that the message I am sending is wrongly formed and is not a correct HL7 message. I did several checks on my message and it looked good. After doing a bit of research and troubleshooting, I came to know that the problem was with the party configuration that I had in the “BTAHL7 Configuration Explorer”.
  • System.Transactions.TransactionException: The operation is not valid for the state of the transaction. --->
    System.TimeoutException: Transaction Timeout  
    --- End of inner exception stack trace ---  
    at System.Transactions.TransactionState.EnlistVolatile(InternalTransaction tx, IEnlistmentNotification enlistmentNotification, EnlistmentOptions enlistmentOptions, Transaction atomicTransaction)  
    at System.Transactions.Transaction.EnlistVolatile(IEnlistmentNotification enlistmentNotification, EnlistmentOptions enlistmentOptions)  
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.TransmitTxnBatch..ctor(IBTTransportProxy transportProxy, ControlledTermination control, Transaction transaction)  
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkDeleteTxn.Execute(BizTalkExecutionContext executionContext). New!
    • After some research I found that the connection is broken if the operation takes more time than that specified in the SendTimeout of the WCF-SAP send port properties..
  • A message sent to adapter "WCF-SQL" on send port "SendPortName" with URI "mssql://SQL-SERVER-1:50105//DbName?FailoverPartner=SQL-SERVER-2" is suspended.
    Error details: Microsoft.ServiceModel.Channels.Common.ConnectionException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.
    Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.Data.SqlClient.SqlException: A
    network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.
    Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception: Logon failure: unknown user name or bad password New!

BizTalk 2006 Adapters Issues

The following are the known errors/issues associated to BizTalk 2006 Adapters:
  • FTP: The receive location “ErrorMonitor Location” with URL “ftp://IP:21//OUT/log_err_*” is shutting down. Details:”The error threshold was exceeded.
    • First you need to understand the behavior of the BizTalk 2006 (R2) FTP Adapter:
      • The BizTalk Server 2006 FTP adapter uses the FTP client protocol to poll the designated FTP server and retrieves data from the server “as is.” The FTP adapter does not validate any data that it retrieves. The FTP adapter sends the retrieved document to the BizTalk Messaging Engine for processing and then it deletes the original document from the FTP server.
    • Second you need to understand the configure variables for an FTP Receive Location, in particularly this:
      • Error Threshold: Specify the number of errors that BizTalk Server can encounter before the location is disabled. (Default value: 10)
    • Therefore the first thing I checked was the permissions of my user on the folder of the FTP that I’m monitoring… the result was that I had only read privileges and this is what was causing me the problem, because as I said earlier, the behavior of the adapter is: deletes the original document from the FTP server.
  • "The import failed because the import file is larger than the maximum size allowed on your server. Contact your system administrator".
  • The Messaging Engine failed to register the adapter for “SOAP” for the receive location {Location}”. Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.
  • BizTalk Adapter v2.0 for mySAP Business Suite. Description: Error in Check Transaction: Failed to load the runtime. (Exception from HRESULT: 0×80131700).
  • The Messaging Engine could not find the receive location for URI:"/XXX_VirtualDirectory/Service.asmx".\
    Please verify the receive location exists and is enabled. New!
    • If your BizTalk solution is mainly relying on HTTP/SOAP adapter (we are still in BTS 2006 - no WCF yet), you'll soon see weird errors popping up due to BizTalk isolated host instances / IIS Application pool  configuration.  In order to resolve this problem, you need to setup the Isolated Host Instances and the application pools correctly. The rules are simple:
      1- You must create at least one IIS application pool for each isolated host.
      2- A separate IIS application pool is not required if all of your receive locations use the same adapter (HTTP or SOAP) and same ReceiveHandler (ex: BizTalkServerIsolatedHost)
      3- A separate IIS application pool is required if the receive locations use different adapters (HTTP/SOAP) and they run under the same ReceiveHandler (ex: BizTalkServerIsolatedHost)
      4 -A separate IIS application pool is required if the receive locations run under different ReceiveHandler (ex: BizTalkServerIsolatedHost, BizTalkServerIsolatedHost_2)  
  • Creating an instance of the COM component with CLSID {C34AE9CE-8410-4191-8205-900E08603EC2} from the IClassFactory failed due to the following error: 800706b9."
    At the same time on the MQ server we noticed the below error: A COM+ application hangs with an 'Access violation' in amqmtmgr.dll and a dump is produced showing:
    amqmtmgr.dll!_FreeHConn() + 0xd5 bytes
    amqmtmgr.dll!_tmzstMQDISC() + 0x17d bytes.. New!

BizTalk Runtime Issues

The following are the known errors/issues associated to BizTalk Runtime:
  • A batch item failed persistence Item-ID c715fbf1-6eed-4781-8061-85b4088b0efb OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo. The published message could not be routed because no subscribers were found.
  • Application: BTSNTSvc64.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FDED170BC1 (000007FDECE00000) with exit code 80131544.
    • Periodically, your BizTalk host process crashes with the following errors in the eventlogs.  Note the error code is 80131544. There is a change in the .NET 4.5 CLR that results in the BizTalk process crashing during XLANG AppDomain shutdown.  XLANG AppDomain Shutdown is when the .NET AppDomain that contains the Orchestration Engine tears itself down during periods of inactivity or idleness. 
  • Faulting application name: BTSNTSvc64.exe, version: 3.10.229.0, time stamp: 0x50fe567a
    Faulting module name: clr.dll, version: 4.0.30319.19106, time stamp: 0x51a512d4
    Exception code: 0x80131544
    Fault offset: 0x0000000000370bc1
    Faulting process id: 0xca8
    Faulting application start time: 0x01ceb6394f1dd32a
    Faulting application path: C:\Program Files (x86)\Microsoft BizTalk Server 2013\BTSNTSvc64.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    • Periodically, your BizTalk host process crashes with the following errors in the eventlogs.  Note the error code is 80131544. There is a change in the .NET 4.5 CLR that results in the BizTalk process crashing during XLANG AppDomain shutdown.  XLANG AppDomain Shutdown is when the .NET AppDomain that contains the Orchestration Engine tears itself down during periods of inactivity or idleness. 
  • The BizTalk Service BizTalk Group : BTSOrchHost service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
    • Periodically, your BizTalk host process crashes with the following errors in the eventlogs.  Note the error code is 80131544. There is a change in the .NET 4.5 CLR that results in the BizTalk process crashing during XLANG AppDomain shutdown.  XLANG AppDomain Shutdown is when the .NET AppDomain that contains the Orchestration Engine tears itself down during periods of inactivity or idleness. 
  • There was a failure executing the receive pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Source: “XML disassembler” Receive Port: “XmlValidationReceivePort” URI: “C:\Folder\*.xml” Reason: The document failed to validate because of the following error:”The ‘http://XmlValidationTest.CommonNamespace:Schema1′ element is not declared.”.
    • To avoid having to add a new custom pipeline to the solution, even one as simple as containing a standard XmlValidator component. So instead, I opted to use port-based configuration by enabling validation within the XmlDissembler component in the existing XmlReceive pipeline. Of course, this does require specifying the list of specific schemas in the DocumentSpecNames property on the port instance. 
  • Could not load file or assembly 'Microsoft.BizTalk.Interop.SSOClient, Version=7.0.2300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.  The system cannot find the file specified.
  • “An error occurred while attempting to install the BizTalk application: World Wide Web service (W3SVC) on host “localhost” not available.
    The following Windows component may not be installed: Application Server -> Internet Information Services (IIS) -> Common Files.
     Unknown error (0×80005000)
     Unknown error (0×80005000)” New!
    • The problem this time was that IIS 6 Management Compatibility role services was not installed.The Deployment Framework for BizTalk includes support for deploying application pools and virtual directories in IIS.  Virtual directory and application pool deployment is fully active for server deployments.
      Due to IIS 7.0/7.5 includes significant change on the configuration system, on Windows Server 2008 and above, we need to enable IIS 6 Management Compatibility role services: IIS Metabase and IIS 6 configuration compatibility, IIS 6 WMI Compatibility and IIS 6 Scripting Tools to allow System.DirectoryServices code work on modifying IIS configurations on IIS7.x.
  • BizTalk Server Administration Console fails to launch:
    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) New!
    • 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() .
  • Error While Saving. Unable to access required Public Responder and Public Initiator assemblies or orchestrations. Make sure these assemblies and orchestrations are correctly applied New!
    • As the error suggests we were not able to get the Public Responder and Public Initiator assemblies or orchestrations. Ideally with Rosettanet Installation 9 orchestrations should get created. In this case we had only 5. When I looked at the Resources folder, however, the assemblies were present.

BizTalk SQL Agent Jobs Issues

Read suggested related TechNet Wiki topics:

Business Activity Monitoring (BAM) Issues

The following are the known errors/issues associated with Business Activity Monitoring (BAM):
  • The BAM Star Schema database has not been configured. Run bm.exe setup-databases to configure the database.
  • Using ‘BAMPrimaryImport’ BAM Primary Import database on server ‘…’… ERROR: Failed to open BAM Excel workbook file – ‘C:\Program Files\Microsoft BizTalk Server 2009\Tracking\MyBAMSample.xls’. Old format or invalid type library. (Exception from HRESULT: 0×80028018 (TYPE_E_INVDATAREAD))
  • Scheduling BAM Packages: "Set global connection string variables. Object reference not set to an instance of an object.(0×00000000)".
  • BAM Portal: HTTP Error 503 - The Service is unavailable
    • From time to time I get the 'HTTP Error 503 - The Service is unavailable' when I try to access my BAM portal. Usually I spend a few minutes before I remember how to get past this. It is the account configured to run bam that needs to have its password updated. Most of you should change your password on a regular basis, and its easy to forget to reconfigure BAM with the new password.
  • BAM Portal: The Server encountered a critical failure while trying to access the list of Views. The Business Management Web Service requires attention. Use the navigation bar on the left to access Business Activity Monitoring views. If the problem persists, contact your System Administrator.
  • Error 5009 Registration of BAM performance counters failed
  • BAM Portal: An unspecified error has occured. Use the navigation bar on the left to access Business Activity Monitoring views. If the problem persist, contact you System Administrator.
  • BAM Portal: Microsoft.BizTalk.Bam.Management.BamManagerException: Failed to list permissions for BAM view. —> System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or property cannot be called on Null values.
  • BAM Portal: (BAMPortal.PortalApplication) Void LogAllErrors(System.Exception[]): System.Web.HttpException: Error executing child request for /BAM/Pages/Search.aspx.
  • BM.exe: ERROR: Failed to list permissions for BAM view. Data is Null. This method or property cannot be called on Null values.
  • BM.exe: ERROR: Security management of the BAM view failed. Failed to grant OLAP permission to account domain\user. A connection cannot be made. Ensure that the server is running. No connection could be made because the target machine actively refused it ip:port.
  • BM.exe: ERROR: Security management of the BAM view failed. The specified account is the Database Owner. The Database Owner always has access to the view and cannot be added to or removed from the view.
    • This error may occur when you try to add or remove one account using BM command: "bm.exe add-account -AccountName:domain\user -View:MyView" - As the error indicates, the user in question is database owner and therefore cannot be added to or removed from the view.
  • BAM Add-In Excel Issue : Unspecified Automation Error.
  • BAM Add-In Excel Issue : Object library invalid or contains references to object definitions that could not be found.
  • Bm.exe is not a valid Win32 App.
    • By looked at bm.exe and found the file size was 0, it seems got corrupted somehow . By replacing it with a new bm.exe solved the problem.
  • BAM Portal Activity Search: "This action cannot be performed because one or more database(s) appears corrupted"
  • BizTalk BAM Portal URL authorization failed for the request (Event code 4007).
    • After a few minutes I remembered the basics… if you remember the BizTalk Configuration experience, you use the BizTalk Server configuration tool to specify whether BAM is enabled, and to specify the Web service accounts, the Windows groups that can view portal, and the Web site that will host the portal. To solve this problem you have to configure the users or groups that you want to have access to BAM Portal under the “BizTalk BAM Portal Users” in your Active Directory.
  • Troubleshooting BAM.
    • ERROR: BAM deployment failed. A connection cannot be made. Ensure that the server is running. No connection could be made because the target machine actively refused it <IP address>.
    • When you try to refresh the data in a live data workbook, Microsoft Office Excel might display the following error: XML for Analysis parser: The CurrentCatalog XML/A property was not specified.
    • Error:"Object library invalid or contains references to object definitions that could not be found" with BAM Excel Add-In in Office 2010.
    • BAM portal cannot connect
    • BAM portal does not work if invalid users are granted permissions
    • Cannot export or import a BAM definition to localhost:  The system cannot find the path specified.
    • This workbook has lost its VBA project, ActiveX controls and any other programmability-related features.
    • Failed to get data.  If available, errors returned from the provider are listed below: * The following system error occurred:  No connection could be made because the target machine actively refused it.
    • Failed to get data.  If available, errors returned from the provider are listed below: * Safety settings on this machine prohibit accessing a data source on another domain.
  • BAM Portal Display Problems
    • If you are facing some BAM Portal display problems you may consider to enable Background Intelligent Transfer Service (BITS) IIS Server Extension.
  • Failed to get data. If available, errors returned from the provider are listed below
  • The cube “...” was not processed. Please run the cube DTS to process the cube
  • Deploying View... ERROR: The BAM deployment failed. Encountered error while executing command on SQL Server "MyMachineName". String or binary data would be truncated. The statement has been terminated.
  • Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "SERVER_NAME". ---> System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'bam_Metadata_GetConfigurationXml', database 'BAMPrimaryImport', schema 'dbo'. New!
    • We found that only one role had execute rights: BAM_Management_WS and the BAM Portal App Pool was running under our BizTalk server account which was the only member of the role. We solved the problem by simply adding BizTalk Server Application Users group to the membership for the BAM_Management_WS role.
  • Execute batch error.  Exception information: TDDS failed to batch execution of streams. SQLServer: ServerName, Database: BAMPrimaryImport. Parameter is not valid.
    TDDS failed to execute event. Could not find stored procedure “dbo.bam_ActivityName_PrimaryImport'.
    New!
    • This stored procedure gets created when you deploy a BAM definition files for a BAM activity. There are a lot of artifacts (SPs,Tables) gets created along with this corresponding to the BAM definition we deploy. I went to the BAMPrimaryImport database and noticed that all the artifacts (Tables + SPs) related to this activity were not in place. This means that the BAM definition file for the activity was removed by me using the “BM remove-all -DefinitionFile:EAI_BAM_definition.xml”” command. But I did not remove the corresponding tracking profile from the tracking Profile Editor.
      So although I did not have any BAM definition file deployed for an activity, the tracking profile was still tracking the data. Now as the artifacts related to BAM activity were missing from database, TDDS was not able to move data out of BizTalkMsgBoxDb.
  • Event Source: BAM EventBus Service
    Either another TDDS is processing the  same data or there is an orphaned session in SQL server holding TDDS lock.Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. SQLServer: MyServer\Instance, Database: BizTalkDTADb.
    New!
    • So, the first thing to check here would be to look up all the SPIDs on SQL Server, and find if any of the BizTalk SPIDs are blocked (look in the ‘BlkBy’ column). You can run this on the ‘master’ database to get this information – sp_who2.

List of Known Issues and Solutions with Setup and Configuration

BizTalk Server 2013 – List of Known Issues and Solutions with Setup and Configuration

The following are the known errors/issues associated to BizTalk Setup and Configuration:

  • BizTalk Server 2013 BETA – Window 8 Configuration issues
    • In Windows 8 for a better user experience it’s very important to use a Live ID, to keep everything in sync between your devices. For some reason BizTalk Server 2013 configuration is not happy (or may be product team haven’t tested this configuration in this BETA) with this setup.
  • Error encountered: Missing file ‘MSVCP100.dll’ while installing BizTalk Server 2013 RTM
  • Error encountered: Could not install BAM Tools while installing BizTalk Server 2013 RTM
  • Error encountered while configuring BAM Portal in BizTalk Server 2013 RTM
    Error encountered: Could not install BAM Portal -> error with regards to “BAM Management Web Service User”
    Error thrown: “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.”
    Actual exception: Log indicated ‘Cannot alter the role ‘NSSubscriberAdmin’, because it does not exist or you do not have permission.’ New!
  • Missing itinerary designer after installing BizTalk 2013
    • During the BizTalk 2013 beta the itinerary designer was distributed as a VSIX package. However, in the RTM version it is no longer there. I went into the registry and saw there were entries for the designer, implying it was installed, yet it was not in Visual Studio. Go to a Visual Studio command prompt, and run “devenv.exe /setup”. This “Forces Visual Studio to merge the resource metadata that describes menus, toolbars, and command groups, from all available VSPackages
  • "The program can’t start because MSVCP100.dll is missing from your computer.  Try reinstalling the program to fix the problem", following by "The following platform components failed to install and will need to be manually installed before setup can proceed: Enterprise Single Sign-On Server. Unspecified error."
    • This error occurred while installing an BizTalk Server 2013 on Windows Server 2012 VM’. The error is saying it is missing the C++ Runtime components (probably why I did not see this error when I already had Visual Studios installed).  After trial and error, it seems that it is only missing the 32-bit C++ Runtime.  It seems that this does not get installed with the BizTalk CAB file
  • "Internal Error 2761"
  • BAM Portal configuration: "Attempted to read or write protected memory"
  • "Microsoft SQL Server Data Transformation Services (DTS) 2012 with SP1 or higer for BAM Archiving is not installed on the local machine. Please install Microsoft SQL Server Integration Services. (Sql2012)"
  • "Missing MSVCP100.dll"
  • A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
  • Could not relay results of procedure 'sp_BackupBizTalkFull' from remote server ‘Server Name’.
    [OLE/DB provider returned message: Timeout expired] New!
    • I realized that backing up the databases from the other SQL instance was taking more than 10 mins to finish. And as we all might be aware of the fact that the other SQL instance would allow remote queries for 10 mins only. So even before my remote query can complete, other SQL instance was stopping this query and throwing the above error message. To avoid this situation, I changed the remote query timeout value on the other SQL instance and allowed it to execute remote queries without the time limit.
  • BizTalk ENTSSO Service Fails to start (Windows Server 2003):
    - RPC failure. Please check your network configuration. Error Code: 0x80070057, The parameter is incorrect.
    - String message: RPC raised an exception with a return code RPC_S_INVALIDA_ARG.
    - The MS DTC Connection Manager is unable to register with RPC to use TCP/IP or UDP/IP.  Please ensure that RPC is configured properly.
       Error Specifics:D:\nt\com\complus\dtc\dtc\cm\src\iomgrsrv.cpp:2220, Pid: 1116
       No Callstack, CmdLine: C:\WINDOWS\system32\msdtc.exe New!
    • This looked to be a RPC related error. The error talked about allocating Ports for RPC communication. We opened up the registry and went to the hive which is responsible to specify this port allocation. HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet\
  • ERROR: The BAM deployment failed. The alerts were not deployed. There was a failure while executing nscontrol.exe.
    Error:"Microsoft Notification Services Control Utility 9.0.242.0c Microsoft Corp. All rights reserved.
    Notification Services failed to get the metadata for the specified instance. Instance Name: BAMAlerts
    SqlServerError: Source: .Net SqlClient Data Provider
    Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
    (Microsoft.BizTalk.Configuration.EDIAS2.Utility) New!
  • Source:        ENTSSO
    Failed to retrieve master secrets. Verify that the master secret server name is correct and that it is available.
    Error Code: 0x80002918, No secrets were found in the registry of the master secret server.  Use the configuration tools to generate or restore a master secret.
    And: ERROR: 0xC0002A13 : This function can only be performed by a local administrator. New!
    • After doing some analysis we found out the issue was related to limited availability of the ports. In this scenario only port XXXX was opened between BizTalk Server and SQL Server (on which the SSO Server is present). For such communications it is important that port 135 and the secondary RPC ports needs to be opened. After opening the required port range the issue was resolved.

BizTalk 2010 – List of Known Issues and Solutions with Setup and Configuration

The following are the known errors/issues associated to BizTalk Setup and Configuration:

  • This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem
  • WCF Service: The document specification ‘...’ from assembly ‘...’ failed to load.”
  • WCF Service: Error: “Root element is missing”
  • Error Code: 0x8004E004, There is no MTS object context
  • “Could not open certificate store.” and “The system cannot find the file specified. (System)”
  • “You are attempting to install Windows SharePoint Adapter Web Service on a virtual server that has not been configured with Windows SharePoint Services. Refer to the documentation for instructions on extending a virtual Server (CWssAdaCfg)”
  • “Could not load file or assembly ‘Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91′ or one of its dependencies. The system cannot find the file specified.(Microsoft.BizTalk.Bam.CfgExtHelper.Utility)”
    • The Microsoft.SqlServer.Smo comes with the Microsoft SQL Server 2005 Management Objects Collection and as a prerequisite software I had installed it before installing BizTalk
  • “SGEN : error : Cannot generate serialization assembly because it already exists. Use /force to force an overwrite of the existing assembly.”
  • BAMAlerts – The activation state cache could not be updated.
    • If you have log shipped or detached/attached the BAMAlerts databases, you will have issues starting the notification service on the BizTalk server for BAM alerts. The reason for this, when these databases are restored, the the ‘Cross-Database Ownership Chaining’ option on the BAMAlertsApplication and BAMAlertsNSMain databases is disabled and grayed out.
  • BizTalk Server 2010 - Message Agent Counters do not get updated for Orchestration Host, shows value as 0 for all the counters New!
  • Either or both of the hosts (inproc: BizTalkServerApplication, isolated:BizTalkServerIsolatedHost) created during BizTalk Runtime configuration could not be found. To workaround, please re-create the hosts. New!
  • Error: "BizTalkMgmtDb" on server " SQLSERVERNAME ".
    The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. New!
    • When you take a process monitor trace at the time when this issue occurs, search for “Access Denied” in the result section for the below path of the machine.config file.  You can search for the System.UnauthorizedAccessException exception as well. Once you find these error, giving everyone access to C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\Machine.Config should resolve the issue.
  • The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service is running and DTC network access is allowed on the BizTalk, SQL and SSO Master servers. For more information, see "MSDTC Configuration settings required for BizTalk Server" in the BizTalk Server Help.
    Internal error: "New transaction cannot enlist in the specified transaction coordinator. New!
  • Configuration Framework]Feature: [Group] Failed to configure with error message [Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown.]. New!
  • Failed to setup database objects associated with BizTalk Host "BizTalkServerApplication" on MessageBox database server "RNOKENTUCKY\CIGINS2" / database name "BizTalkMsgBoxDb".
    BizTalk Server cannot access SQL server.  This could be due to one of the following reasons:
    1. Access permissions have been denied to the current user.  Either log on as a user that has been granted permissions to SQL and try again, or grant the current user permission to access SQL Server.
    2. The SQL Server does not exist or an invalid database name has been specified.  Check the name entered for the SQL Server and database to make sure they are correct as provided during SQL Server installation.
    3. The SQL Server exists, but is not currently running.  Use the Windows Service Control Manager or SQL Enterprise Manager to start SQL Server, and try again.
    4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
    Internal error from OLEDB provider: "Cannot open database "BizTalkMsgBoxDb" requested by the login. The login failed." New!

List of Known Issues and Solutions with Setup and Configuration for All Versions

The following are the known errors/issues associated to BizTalk Setup and Configuration for all versions:

  • BizTalk Group configuration issues: Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown.
    • When you configure BizTalk Server 2006, BizTalk Server 2006 R2, BizTalk Server 2009, or BizTalk Server 2010, the group configuration fails and you receive this error message
  • The master secret has not been backed up. If you lose the master secret all the information stored in the SSO system will be lost permanently and your systems may fail to work correctly. Please use the SSO admin tools to back up your master secret. New!
  • The SSO service failed to start.  Error Code: 0x800710D9, Unable to read from or write to the database.
    The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate. New!
    • The above error shows that SSO service is trying to communicate to the SQL server over SSL protocol but, the certificate got from the SQL server is not valid. This is obviously due to fact that I did not have SQL server  configured for SSL communication. Then, why does SSO service is trying to communicate with the SQL server over SSL?
      Because we have informed SSO service to do so. There is a registry key under the SSO hive which specifies whether to use SSL protocol to communicate with the SQL server.
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ENTSSO\SQL\SSL
      If this key is set to “Yes”, SSO would try to make SSL communication which was the case on my server. I changed the value to “No” and I was able to start the SSO service without any issues.
  • Source:        BizTalk Server
    Event ID:      6913
    Task Category: BizTalk Server
    Computer:     ABC.Microsoft.com
    Description: An attempt to connect to "BizTalkMgmtDb" SQL Server database on server "ABC" failed.
    Error: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.". New!
    • This is a known behavior and this might happen whenever you restart you Domain Controller(s). This happens because whenever you restart your domain controllers, application (BizTalk) cannot authenticate users until the Domain Controller(s) is not responding on the network.

List of Others Known Issues and Solutions

BizTalk 2010 – List of Others Known Issues and Solutions

The following are the other known errors/issues associated to BizTalk 2010:

List of Others Known Issues and Solutions for All Versions

The following are the other known errors/issues for all BizTalk versions:

  • Failed to enable constraints. One or more rows contain values violating non-null , unique or foreign-key constraints. (System.Data)
  • Could not enlist orchestration <type details here>. Value does not fall within the expected range.
  • "Could not enlist send port '[Send Port Name]' Exception from HRESULT: 0xC00CE557(Microsoft.BizTalk.ExplorerOM) ".
    • After some experimentation I found that it was definitely the filter and I think what was happening was that when I edited the file and saved it through Visual Studio it must be affecting the encoding of the file when it was saved.  When I edited the file through Visual Studio I could not successfully import the bindings to setup the port.  If I configured the template only through Notepad the import of bindings into BizTalk would setup the filter correctly
  • Enlist operation failed: 0x8004d01c(XACT_E_CONNECTION_DOWN). SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager. A severe error occurred on the current command.  The results, if any, should be discarded. (Microsoft SQL Server, Error: 8510).
    • It turns out that when clustered services are brought online, they must be started in a specific order, with the DTC service being started before SQL Server. If they are not brought online in this order, SQL Server fails to register itself and DTC transactions cannot be initiated, even though both the DTC and SQL service’s are running and everything looks correct
  • "An error has occurred while establishing a connection to the server"
  • "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. (Microsoft.BizTalk.ResourceManagers)"
  • "Add-PSSnapin : Cannot load Windows PowerShell snap-in BizTalkFactory.Powershell.Extensions because of the following err or: Could not load file or assembly 'file:///C:\Program Files (x86)\BizTalkFactory PowerShell Provider\BizTalkFactory.P owerShell.Extensions.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently load ed runtime and cannot be loaded. At C:\Users\Administrator\Documents\WindowsPowerShell\profile.ps1:5 char:13 + Add-PSSnapin <<<< BizTalkFactory.Powershell.Extensions + CategoryInfo : InvalidArgument: (BizTalkFactory.Powershell.Extensions:String) [Add-PSSnapin], PSSnapInE xception + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand"
  • Error 1053: The service did not respond to the start or control request in a timely fashion
    • We got this error when Rule Engine Update Service did not start up after a reboot. We had the same problem with HL7 Logging service.
    • The problem was that our machines were up-to-date with windows update but latest Cumulative Pack was not applied.  This was related to BizTalk 2009 environment.
    • Lesson learnt is to always have latest windows update and latest Cumulative Pack applied.
    • One of the server still did not have its Rule Engine Update Service start. The problem was that there is a time-out after 30 seconds. We tried to start again and it worked because it took less than 30 seconds to start on this occasion. The other option is to change the timeout property in the registry.
  •  Orchestration will not open in the Orchestration Designer
  • Could not create SSOCSTX. To fix the problem, reinstall SSO or install SSOCSTX.dll into a COM+ library application.
    Additional Data: 93
    Error Code: 0x8004E00F, COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator New!
  • No BizTalk assembly got loaded to BizTalk Server 2010 process: Could not load file or assembly ‘xxxx' or one of its dependencies New!
    • This was because the config entry <supportedRuntime version="v4.0" /> which directs BizTalk process to point to 4.0 assembly was missing in the btsntsvc.exe.config file. This key is present by default in config file, these default keys should not be removed.. 

BizTalk Server Accelerators

The following section is related to BizTalk Accelerators issues :

BizTalk Accelerator for HL7 (BTAHL7)

The following section is related to BizTalk Accelerator for HL7 issues :

BizTalk Accelerator for RosettaNet (BTARN)

The following section is related to BizTalk Accelerator for RosettaNet issues :

BizTalk Accelerator for SWIFT (A4SWIFT)

The following section is related to BizTalk Accelerator for SWIFT issues :

Other Issues

The following section is related to other issues that can occur in a BizTalk Environment or ecosystem:

  • Error(s): This operation is not supported for messaging queue in workgroup mode. New!
  • Microsoft.ServiceBus.Messaging.MessagingCommunicationException was unhandled
    HResult=-2146233088
    Message=Error during communication with Service Bus. Check the connection information, then retry.
    Source=Microsoft.ServiceBus
    IsTransient=true
    InnerException: System.ServiceModel.CommunicationObjectFaultedException HResult=-2146233087
    Message=Internal Server Error: The server did not provide a meaningful reply; this might be caused by a premature session shutdown..TrackingId:18787480-6512-4c57-89ea-2618291dd1fb, Timestamp:9/24/2013 2:16:48 PM
    Source=Microsoft.ServiceBus.
    New!
    • It seems that there is a configuration value in the  “Microsoft.ServiceBus.Gateway.exe.config” file (located at “C:\Program Files\Service Bus\1.0”) which is restricting the larger messages to be received in the service bus queue.
  • Error: Attempt to install Message Queuing Server failed with error code 0x80070643.  Fatal error during installation
    The following features were not installed:
    Message Queuing Services
    Message Queuing Server .
    New!
  • An application cannot be created for the Message Queuing IIS extension /LM/W3Svc/Root/MSMQ. Message Queuing will not be able to receive HTTP messages.
    Error Code: 0x080110414.
    New!

Warnings

 The following are the known Warnings associated to BizTalk:

BizTalk 3rd Party Tools Issues

The following are the known Warnings associated to BizTalk 3rd Party Tools:

  • "Unable to enlist in the transaction.
    System.Runtime.InteropServices.COMException (0x8004D00A): Unable to enlist in the transaction.
    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
    at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
    at System.Management.ManagementObject.InvokeMethod(String methodName, Object[] args)
    at A.cf0555bb9c0f6a0aebd67da53b41e6535.cc49ef4e8476b31546c8cfd644bd22a66(String c3ce089d4844970dd178d4bf819010021)
    at Kovai.BizTalk360.BusinessService.Main.BizTalkQueryBusinessService.ExecuteServiceInstanceOperation(ServiceInstances serviceInstances, ServiceInstanceOperation operation)
    at Kovai.BizTalk360.WCFService.BizTalkQueryService.ExecuteServiceInstanceOperation(BizTalkQueryServiceRequest request, ServiceInstances serviceInstances, ServiceInstanceOperation operation)"
    • After some research, I found out this was a problem with the DTC service, which was not enabled on the BizTalk360 machine. 
  • Server Error in '/BizTalk360' Application: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. If your service is being hosted in IIS you can fix the problem by setting 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' to true or specifying 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'. New!

 

ESB Toolkit – List of Known Issues and Solutions

BizTalk Server 2013: ESB Toolkit 2.2 – List of Known Issues and Solutions

The following are the known errors/issues associated with the ESB Toolkit 2.2: 

  • warning MSB3245: Could not resolve this reference. Could not locate the assembly "ESB.BAM.Service.Implementation". Check to make sure the assembly exists on disk.
    warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.ReportViewer.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL".
    warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL".
    Faults\Itineraries.aspx.cs(8,11): error CS0234: The type or namespace name 'BAM' does not exist in the namespace 'ESB' (are you missing an assembly reference?) [C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\ESB.Portal.csproj]
    Faults\MessageViewer.ascx.cs(41,11): error CS0234: The type or namespace name 'BAM' does not exist in the namespace 'ESB' (are you missing an assembly reference?) [C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\ESB.Portal.csproj]
    DAL\DALHelper.cs(21,13): error CS0012: The type 'Microsoft.Practices.ServiceLocation.IServiceLocator' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Practices.ServiceLocation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. [C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.BAM.Service\ESB.BAM.Service\ESB.BAM.Service.Implementation\ESB.BAM.Service.Implementation.csproj]
  • C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\ESBSource\Source\Samples\Exception Handling
    \Install\Scripts>powershell .\ExceptionHandling_Install.ps1 1.\ExceptionHandling_Install.ps1:
    File C:\Program Files (x86)\Microsoft BizTalk ESBToolkit\ESBSource\Source\Samples\ExceptionHandling\Install\Scripts\ExceptionHandling_Install.ps1 cannot be loaded because running scripts is disabled on this system.
  • Exception has been thrown by the target of an invocation. Source: Microsoft.Practices.ESB.Resolver.ResolverMgr.
  • Could not load file or assembly 'Microsoft.BizTalk.Interop.SSOClient, Version=7.0.2300.0, Culture=neutral, PublickKeyToken=31bf3856ad36e35' or one of its dependencies. The system cannot find the file specified.
  • Exception has been thrown by the target of an invocation.
    Source: Microsoft.Practices.ESB.Resolver.ResolverMgr
    Method: System.Collections.Generic.Dictionary`2[System.String,System.String] Resolve(Microsoft.Practices.ESB.Resolver.ResolverInfo, Microsoft.BizTalk.Message.Interop.IBaseMessage, Microsoft.BizTalk.Component.Interop.IPipelineContext)
    Error Source: mscorlib
    Error TargetSite: System.Object InvokeMethod(System.Object, System.Object[], System.Signature, Boolean). New!
  • Configuring ESB toolkit: System.NullReferenceException: Object reference not set to an instance of an object.
    at EsbConfigurationTool.Panels.WebServicesException.get_WebSiteId(). New!

ESB Toolkit 2.1 ��� List of Known Issues and Solutions

The following are the known errors/issues associated with the ESB Toolkit 2.1: 

  • The send adapter for this send port is not supported on64-bit host instances. Please make sure that the send adapter is associated with a 32-bit only handler.
  • Access denied: Source: Microsoft.Practices.ESB.BizTalkOperations.BizTalkQuery; Method: Void .ctor(); Error Source: System.Management; Error TargetSite: Void ThrowWithExtendedInfo(System.Management.ManagementStatus)
  • Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′.
  • Could not load file or assembly 'Microsoft.Practices.ESB.BizTalkOperations, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified
    • Make sure you import/install Microsoft.Practices.ESB.CORE64.msi New!
  •  Create Fault Message enters "endless loop" and cause the CPU to max out and the orchestration to hang indefinitely

See Also

Read suggested related topics: Another important place to find a huge amount of BizTalk related articles is the TechNet Wiki itself. The best entry point is BizTalk Server Resources on the TechNet Wiki.