Revision #92

You are currently reviewing an older revision of this page.
Go to current version


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 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. New!
    • 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. New!

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:

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".

BizTalk Runtime Issues

The following are the known errors/issues associated to BizTalk Runtime:
  • This remoting proxy has no channel sink wich means either the server has no registered server channels that are listening, or this application has no suitable client channel to talk to the server. The instance may have been completed or terminated already.
  • An unhandled exception (‘<System.StackOverflowException>’) occurred in BTSNTSvc.exe [2756]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.
  • “MIME/SMIME encoder” Send Port: “…” URI: “…” Reason: Unable to initialize. Please ensure that exsmime.dll has been registered in the system.
  • There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Source: “XML assembler” Send Port: “portname” URI: “uri” Reason: This Assembler cannot retrieve a document specification using this type: namespace#rootnode …
  • The maximum number of convoy set properties has been exceeded. A convoy set can only contain up to 3 properties.
    • Now, you may very well ask, what is a convoy set? And yes, it is a bit confusing that the error message uses a term that is actually internal to BizTalk and not something your average BizTalk developer cares about. But a convoy set is simply a correlation set that is used in a convoy.
  • Inner exception: Received unexpected message type does not match expected type http://Namespace#RootNode. Exception type: UnexpectedMessageTypeException
  • The published message could not be routed because no subscribers were found.
  • Arithmetic overflow error converting expression to data type int.[SQLSTATE 22003] (Error 8115) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
    • This issue is due to threshold of Sendhost has crossed the Int value. If I quickly check at the threshold of the SendHost I could find that it already reached Int value. If you look at the Store procedures which has supported for the above job, It cleared said the data type used for nID as INT in stored procedure. But actually in table it declared as BigInt..
  • Retrieving the COM class factory for component with CLSID {254B4003-2AA7-4C82-BB2E-18BA7F22DCD2} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
  • Receive pipeline rejected incoming message due to the following RNIF exception: UNP.SCON.VALERR : A failure occurred while validating the service content.
    • It turns out that the RNDisassembler does in-fact attempt to validate the message contained within the Service Content against a deployed schema just like the standard XmlDisassembler. The message that our trading partner was sending did not validate and hence the RosettaNet Accelerator threw this error message; once we had corrected the schema and redeployed, the error went away.
  • Could not load file or assembly ‘file://Microsoft.Solutions.BTAHL7.HL72fDasm.dll’ or one of its dependencies. An attempt was made to load a program with an incorrect format.
  • Scheduling BAM Packages: "Set global connection string variables. Object reference not set to an instance of an object.(0×00000000)".
  • Exhausted the network retry attempts. Error code 5649. 
  • “Cannot open database ‘…’ requested by the login. The login failed” or “The EXECUTE permission was denied on the object ‘…’, database ‘…’, schema ‘dbo’”. 
  • “The Messaging Engine failed to add a receive location "..." with URL "sap://CLIENT=010;LANG=EN;@a/SAPSERVER/00?..." to the adapter "WCF-SAP". Reason: "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_SYSTEM_FAILURE. SapErrorMessage=Open file 'C:\SAPINI\saprfc.ini' failed: 'No such file or directory'.  AdapterErrorMessage=Error accepting incoming connection. RfcAccept returned RFC_HANDLE_NULL.”
    • The RFC library will read the saprfc.ini file to find out the connection type and all RFC-specific parameters needed to connect to an SAP system, or to register an RFC server program at an SAP gateway and wait for RFC calls from any SAP system.
  • 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 yor password on a regular basis, and its easy to forget to reconfigure BAM with the new passord.
  • xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service
    Exception type: TypeInitializationException
    The following is a stack trace that identifies the location where the exception occured
    Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0×80131401)
    • After some research I found out that the Loading this assembly would produce a different grant set from other instances part normally represents a failure with 32bit vs 64bit. I then checked the host-instance, and to my surprise the default value for the host-instance was 32bit only, even though the server was 64bit. So I created a new host-instance that was 64bit, changed the orchestration to use this host instance, and with that the issue was resolved.
  • There was a failure executing the receive pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=, Culture=neutral, PublicKeyToken1bf3856ad364e35" Source: "EDI disassembler" Receive Port: "..." URI: "...\*.*" Reason: No Disassemble stage components can recognize the data. New!

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:

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)
  • 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 Asministrator.
  • 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 definately 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" New!


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. 

ESB Toolkit 2.1 – List of Known Issues and Solutions New!

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.

See also BizTalk Server Resources on the TechNet Wiki