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:

• Errors exist for one or more children.
  • Typically this problem is usually associated with problems in Orchestration Designer “refactoring” or “graphical interpretation” and in a certain way it isn’t a “valid error”, ie, it doesn’t describe the real problem. Usually this error is followed with a red indicator on the shape; however this was not my case, I had no indicator, but had the same error.
    • For more information see BizTalk Orchestration error: "Errors exist for one or more children"
• ‘varName‘: if shared data is updated in a parallel then all references in every task must be in a synchronized or atomic scope
  • For more information see: BizTalk Orchestration Error Message – Using Parallel Action – if shared data is updated in a parallel then all references in every task must be in a synchronized or atomic scope
• Assembly generation failed — Referenced assembly ‘…’ does not have a strong name
  • This problem occurs when a type from an unsigned referenced assembly is used within an orchestration. 
    • BizTalk building solution problem – Assembly generation failed — Referenced assembly ‘…’ does not have a strong name
• ‘EmailPort’: property ‘Microsoft.XLANGs.BaseTypes.Address’ is read-only for non-dynamic ports
  • The port bind is not specified as Dynamic.
    • BizTalk Orchestration Error Message – property ‘Microsoft.XLANGs.BaseTypes.Address’ is read-only for non-dynamic ports
• ‘System.String’ must be Xml serializable to be a message part type
  • Despite what the error says - there's no further information in the event log as it suggests
    • Strange Visual Studio behaviour
• Use of Unconstructed Message ‘MessageName’
  • Check if you have a reference to the message before its initialize
    • Multi-Part message – “use of unconstructed message ” – Error message when you try to build a BizTalk project
• An atomic scope may not contain a receive with a correlation filtration initialized in the same scope
  • The error occurs because you have a Receive shape inside an atomic scope and this Receive shape follows a correlation set that is initialized within the same scope. This is not allowed, as explained here: http://msdn.microsoft.com/en-us/library/aa560115%28BTS.10%29.aspx.
    • Atomic scope may not contain Receive that follows correlation set initialized inside scope
• The transport proxy method MoveToNextTransport() failed for adapter WCF-Custom: Reason: "Messaging engine has no record of delivering the message to the adapter. This could happen if MoveToNextTransport() is called multiple times for the same message by the adapter or if it is called for a message which was never delivered to the adapter by the messaging engine". Contact the adapter vendor.
  • Biztalk Dynamic Request Response Port –Consume WCF Service - Error MoveToNextTransport()
• A message sent to adapter "SMTP" on send port "port-name" with URI "mailto:*mail@domain.com" is suspended. Error details: Unknown Error Description
  • If you are using Dynamic SMTP port and you use the SMTP.EmailBodyText property, you must set up the SMTP.EmailBodyTextCharset property.
    • BizTalk: Dynamic SMTP Port: Unknown Error Description
• Symbol '@@@@' is already defined; the first definition is in assembly @@@.dll
  • The error occurs when trying to rebuild an orchestration assembly in Visual Studio.Net 2010 in BizTalk 2010 environment. This behaviour was seen already in BizTalk 2004 and a straight forward workaround exists which explains clearly what has to be done, to circumvent the situation.
    • Solving BizTalk "error X2044"
• The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security.
  • This problem occurs because the user account that you used to log on does not have sufficient permissions.
    • The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security.
• cannot resolve imported 'service'.
  • So basically, the problem is: When compiling a BizTalk project, you get the "'projectname.orchestrationname': cannot resolve imported 'service'" error. This occurs when you are compiling a project that has an orchestration inside it, that calls another orchestration in another project that again calls an orchestration in a third project..
    • cannot resolve imported 'service'
• Identifier ‘RetryCount’ does not exist in ‘myprojectnamespace’; are you missing an assembly.
  • This problem occurs because we used a special keyword in the namespace used by BizTalk: “BTS” and when we try to compile the project the compiler is trying to get the property RetryCount from the namespace of the BizTalk project: ‘CompanyName.Project.Module.BTS‘ instead of namespace BTS associated with Microsoft.BizTalk.GlobalPropertySchemas assembly.
    • Identifier ‘RetryCount’ does not exist in ‘myprojectnamespace’; are you missing an assembly
• Illegal 'activate' predicate: an 'activate' predicate rvalue must be a string, character, boolean or numeric literal.
  • This problem may occurs when you try to set a filter on the initial receive shape without “double quotes”.
    • Illegal 'activate' predecate
• you must specify at least one already-initialized correlation set for a non-activation receive that is on a non-selfcorrelating port
  • This error can occur if your orchestration has no activating Receive shapes (Activate = true) or has no activating Receive shapes and is not called directly by another orchestration.
    • Project build results in the error "you must specify at least one already-initialized correlation set for a non-activation receive that is on a non-selfcorrelating port"
• A correlation may be initialized only once
  • This error occurs if you are trying to initialize a correlation set in a loop.
    • How to initialize correlation set multiple times

Visual Studio Schema Design Issues

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

• Unexpected XML declaration. The XML declaration must be the first node in the document, and no white space characters are allowed to appear before it. Line x, position y.
  • This problem may occurs if you have a single whitespace character on the first line of your schema before the start of the xml declaration or a single whitespace character on the first line of your XML file before the start of the xml declaration.
    • BizTalk Schemas – Unexpected XML declaration. The XML declaration must be the first node in the document, and no white space characters are allowed to appear before it
• Build failed. Compiler for file type ‘*.xsd’ failed. Value cannot be null. Parameter name: pUnk
  • The error occurs if there is any *.xsd file added to the project.
    • BizTalk Compilation problem – Compiler for file type ‘*.xsd’ failed. Value cannot be null. Parameter name: pUnk error
• Unrecognized data in remaining stream.
  • You can get this error while validating the flat-file instance in visual studio if you have specified wrong value for Tag Identifier.
    • error BEC2004: Unrecognized data in remaining stream.
• This node can occur potentially multiple times in the instance document. Only nodes which are guaranteed to be unique can be promoted.
  • Unfortunately, elements that can occur more than once can not be promoted.
    • Promoting reoccuring elements
• error BEC2004: Non Segment level  : [71] Transaction Set or Group Control Number Mismatch. New!
  • Message Reference Number in UNH segment must be equal to the existing in the UNT segment. Therefore change one of them to become equal and the problem will be solved.
    • Error when trying to validate EDI message against the schema: [71] Transaction Set or Group Control Number Mismatch
• EC2004: Non Segment level  : [29] Invalid count specified at interchange, group or message level. New!
  • This error is a notification that the number of groups, messages, or segments does not match the number given in the UNZ, UNE, UNT, or UST segment; or that the length of an object or the length of encrypted data is not equal to the length stated in the UNO, UNP, USD, or USU segment, i.e., the control count does not match number of instances received..
    • Error when trying to validate EDI message against the schema: [29] Invalid count specified at interchange, group or message level
• Schema item missing from Visual Studio BizTalk Project items. New!
  • Well, unfortunately, I don’t know exactly why this problem occurred, but I believe that some dependence has become corrupted. To fix this issue, or similar problems, you need to repair Visual Studio 2010.
    • Schema item missing from Visual Studio BizTalk Project items

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.
  • This issue can occur if the XSLT file that is defined in the Custom XSL Path Grid Properties uses the <xsl:import> element or the <xsl:include> element to import or to include an external XSLT file.
    • BizTalk XSLT Reuse (xsl:include and xsl:import): Resolving of external URIs was prohibited error
• 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.
  • For some reason the BizTalk designer loses the schema reference and it is a little hard trying to “trick” the designer into remembering the schema’s location.
    • BizTalk Mapper – Cannot load source/destination schema
• Value Cannot be Null. Parameter name: extension
  • If you use external assembly in the scripting fucntiod MAP create an Extension Object file to keep the Details of the dll being referenced in the scripting functoid..
    • BizTalk Map Error: 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.".
  • Turns out that the file contains nulls (hex 0x00) in some of the fields, in some of the records.
    • Inbound map fails due to nulls in incoming file
• 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.
    • Functoid not found (Functoid ID 6124)
• 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′. New!
  • BizTalk Server 2010/Visual Studio 2010 have a bug (or issue): Visual Studio does not persist the path of Custom Extension XML property in the .BTM file.
    • Workaround 1: BizTalk Mapper Patterns: Calling an external assembly from Custom XSLT in BizTalk Server 2010
    • Workaround 2: BizTalk Mapper: Custom Extension XML property fixed with PowerShell script (BizTalk 2010)

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!
  • While trying to debug custom pipeline component using “Pipeline.exe” utility, I keep getting this error message.
    • Debug BizTalk Custom Pipelines Components using Pipeline.exe utility – Pipeline file name is already specified Error

BizTalk Deploy Issues

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

• Could not enlist orchestration ‘MyAssembley, Version=1.0.0.0, Culture=neutral, PublicKeyToken=776eb620b83c3d30′. Object reference not set to an instance of an object. (Microsoft.BizTalk.SnapIn.Framework)
  • This problem maybe happens because the DLL’s presents in the GAC are not correct, or they are missing.
    • BizTalk Deploy Error: Could not enlist orchestration ‘MyAssembley’. Object reference not set to an instance of an object. (Microsoft.BizTalk.SnapIn.Framework)"
    • Cannot enlist orchestration because assembly not found
• Unable to copy file "…\Pipeline Components\MyPipelineComponent.dll" to "bin\Debug\ MyPipelineComponent.dll". The process cannot access the file "bin\Debug\ MyPipelineComponent.dll" because it is being used by another process
  • This problem may occurs if: Visual Studio has a lock on the file in order to show the pipeline components in the toolbox; Some BizTalk process is running BizTalk host and have a lock on the file; or IIS AppPool has a lock on the file.
    • BizTalk Pipeline component – Unable to copy file "…\Pipeline Components\MyPipelineComponent.dll" to "bin\Debug\ MyPipelineComponent.dll". The process cannot access the file "bin\Debug\ MyPipelineComponent.dll" because it is being used by another process
• Component ‘…’ could not be initialized. Pipeline component ‘…’ could not be resolved (is an assembly reference missing?)
  • BizTalk Pipeline Component problem – Component ‘…’ could not be initialized. Pipeline component ‘…’ could not be resolved (is an assembly reference missing?).
• The specified module could not be found. (Exception from HRESULT: 0x8007007E)
  • Your DLL (component) depend on other DLL’s to get its job done and if you didn’t copy or install those too, you’d indeed get this error message.
    • BizTalk Pipeline Component – The specified module could not be found. (Exception from HRESULT: 0x8007007E) error
• You have selected an invalid pipeline component assembly. Please check security settings for the assembly if you are loading it from an UNC path.
  • Developing Pipelines Components – UNC Path Error
• Unable to process create change request for BizTalk binding "BindingInfo.xml". Import bindings (overwrite) failed. (Microsoft.BizTalk.ResourceManagers)
  • Error importing binding files
• Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
  • When developing BizTalk 2009 solutions using Visual Studio .NET 2008 on Windows Server 2008, you run into issues when deploying from within Visual Studio .NET.
    • Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
• There was a failure executing the receive pipeline… failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache
  • Because this error can happen for several reasons you may have many solutions to this problem. These are some steps that you should take to resolve the issue:
    • There was a failure executing the receive pipeline… failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache
• Failed to update binding information. Could not validate TransportTypeData, Address or Public Address properties for Receive Location <Receive Location Name>. Retrieving the COM class factory for component with CLSID {CFF09884-6582-49C2-A74F-0FD85849281E} failed due to the following error: 8007045a. and Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Could not validate TransportTypeData, Address or Public Address properties for Receive Location <Receive Location Name>. Retrieving the COM class factory for component with CLSID {CFF09884-6582-49C2-A74F-0FD85849281E} failed due to the following error: 8007045a.
  • These errors occur when trying to redeploy over BizTalk applications that use role links with send or receive ports. These deployments from Visual Studio have been attempted with the deployed BizTalk applications in both the enlisted/started and unenlisted/stopped states.
    • Role Link Deployment Issue and Workaround
• Error: The binary code for the script is not found. Please open the script in the designer by clicking Edit Script button and make sure it builds successfully.
  • “the binary code for the script is not found…”
• Exception thrown from: segment -1, progress -1. Inner exception: Could not load type ‘type name’ from assembly ‘assembly name, Version=1.0.0.0, Culture=neutral, PublicKeyToken=…’.Exception type: TypeLoadException.
  • You didn’t install the assembly specified in the error; Your DLL depend on other DLL’s to get its job done and if you didn’t copy or install those too, you’d indeed get this error message; Or you have installed an older version of the assembly.
    • TypeLoadException: Could not load type ‘type name’ from assembly ‘assembly name, Version=1.0.0.0, Culture=neutral, PublicKeyToken=…’
• Schema referenced by Map 'map_name' has been deleted. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group configuration before making any further changes. New!
  • This problem occurs if: A schema referenced by a deployed map has not been deployed.
    • BizTalk 2010 Map Deployment Bug Fix
• Failed to add resource(s). Resource (…) is already in store and is either associated with another application or with another type. New!
  • Inadvertently deployed it to another application, most likely to the default “BizTalk Application 1”;
  • Someone have probably removed the previously existing name in “Application Name” property from the project properties.               
    • Failed to add resource(s). Resource (…) is already in store and is either associated with another application or with another type. 
• There was a failure executing the receive pipeline: "xxxxxxxxx, xxxxxxxx, Version=1.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxx" Source: "Flat file disassembler" Receive Port: "xxxxxxxxx" URI: "C:\BizTalk Folders\xxxxxxxxx\*.csv" Reason: Cannot access a disposed object. Object name: 'DataReader'.. New!
  • The following error was encountered when consuming a flat file through a pipeline that made use of the Flat File Disassembler pipeline componente; This was resolved by settling 'RecoverableInterchangeProcessing' to True in the Receive Pipeline Properties on the Receive Location.                  
    • BizTalk Pipeline - Flat File Disassembler Cannot Access a Disposed Object 'DataReader'

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.
  • BizTalk WCF Adapter – BasicHttpBinding results in Partial Trust Exception
• 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 system cannot find the file specified
• The HTTP send adapter cannot complete the transmission within the specified time
  • This error occurred for Solicit-response send port when the HTTP adapter does not receive the response within the time specified for Request timeout. for details see: Error: "The HTTP send adapter cannot complete the transmission within the specified time"
• "The operation has timed out", "Request timed out."
  • This error is caused when the BizTalk performance get degraded and it start responding slow
    • For details see Error: "The operation has timed out", "Request timed out."
• HTTP/SOAP:The underlying connection was closed: An unexpected error occurred on a receive.
  • You might get this error in case of solicit response send port if AppPool get recycled before receiving the response message
    • Error: " The underlying connection was closed: An unexpected error occurred on a receive."
• FTP: Unable to receive the file
  • This error can be caused by blocking of incoming connection by Firewall
    • For details see: FTP adapter issue: 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.
    • Error with One-Way WSDL Operations and BizTalk Receive Locations
• 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)’.
  
  • SP1 and the Oracle Adapter in BizTalk Adapter Pack 2.0
• "E-PSFT0029: JVM was not started" or "Unable to find JAVA_HOME"
  
  • It's common to get this kind of errors when we try to connect Enterprise Applciatons with BizTalk Adapters
    
    • Error while connecting with BizTalk Server Enterprise Adapter. (PeopleSoft/Siebel/JDE etc)
• 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.
  
  • Getting rid of : WCF-Custom" raised an error message. Details "System.Data.SqlClient.SqlException: Timeout expired

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.
    • BizTalk 2006 FTP Adapter – The receive location… is shutting down. The error threshold was exceeded
• "The import failed because the import file is larger than the maximum size allowed on your server. Contact your system administrator".
  • The fix is simple and requires a change to the Web.Config file of the Commerce Server Catalog Web Service.
    • Large File Error when Importing a Catalog into Commerce Server 2007

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.
  • This error may occur because you may have referenced COM+ component inside your project:
    • Error when trying to debug orchestration in HAT: This remoting proxy has no channel sink wich means either the server has no registered server channels that are listening
• 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.
  • It’s very common to use .NET code for orchestration support. A StackOverflowException exception is thrown when the execution stack overflows by having too many nested method calls.
  • Tip: Make sure you do not have an infinite loop or infinite recursion.
    • BizTalk Error Message – An unhandled exception (‘System.StackOverflowException’) occurred in BTSNTSvc.exe
• “MIME/SMIME encoder” Send Port: “…” URI: “…” Reason: Unable to initialize. Please ensure that exsmime.dll has been registered in the system.
  • This is a strange behavior occurs in a custom pipeline that uses MIME/SMIME encoder.
    • There was a failure executing the send pipeline: "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=3.0.1.0, 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 Application made reference to another Application that contained one schema with same namespace#rootnode name
  • The Application as different resources (dll) that contained more than one schema with same namespace#rootnode name
  • Schema defined by namespace#rootnode does not exist (not my case, because it was deployed)
    • There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, ….” – 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.
    • Only three properties in a Correlation Type – or what is the deal?
• Inner exception: Received unexpected message type does not match expected type http://Namespace#RootNode. Exception type: UnexpectedMessageTypeException
  • Message Debatching – Values not being mapped in a Transformation – Null Values in Destination Schema
• The published message could not be routed because no subscribers were found.
  • You can get this error if the subscription has not been created or context properties don’t match the subscription.
    • Error: "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..
    • Biztalk HostInstance ThreshHold -Error nID int datatype
• 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)).
  • When you use BizTalk in 64 bit version, and the Mime/Smime encoder you’ve got this error. To resolve it, just put your pipeline on a 32 bit Host.
    • Mime/SMIME encoder error : Class not registered (Exception from HRESULT: 0×80040154 (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.
    • BTARN ‘Service Content’ Error in the RNDisAssembler Component
• 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.
  • Make sure that your host is running under 32bit mode, if it is running in 64 bit mode, you will get this error.
    • 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.
• Exhausted the network retry attempts. Error code 5649. 
  • This error occurs when you have to many connections towards one location that exceeds the limit of allowed connections.
    • Retry exhausted Error code 5649 in BizTalk
• “Cannot open database ‘…’ requested by the login. The login failed” or “The EXECUTE permission was denied on the object ‘…’, database ‘…’, schema ‘dbo’”. 
  • This problem occurs because the user account that you used to access database or that tries to execute stored procedure does not have sufficient permissions.
    • 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.
    • SAP calling RFC hosted in BizTalk
• 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) New!
  
  • 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.
    • Using 64bit Host Instance
• There was a failure executing the receive pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken1bf3856ad364e35" Source: "EDI disassembler" Receive Port: "..." URI: "...\*.*" Reason: No Disassemble stage components can recognize the data. New!
  
  • This error occurs because the message does not contain the EDIFACT interchange envelope segments (UNB and UNZ). An EDIFACT interchange begins with a UNB. It contains version release information, syntax information, and partner information. An interchange ends with a UNZ.
    • There was a failure executing the receive pipeline: Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive Reason: No Disassemble stage components can recognize the data.

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.
  • One of the possible causes of the problem is that Analysis Services form BAM aggregations was not configured.
    • BizTalk BAM activity Deploy problem – 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))
  • When you use a locale setting other than English (United States) while installing the English version of BizTalk Server, your deployment of the Bam.xls file generates an "fnGetString" or "Old format or invalid type library" error.
    • BizTalk BAM activity Deploy problem – 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)".
  • This error was due to the user under which the SQL Server Agent Service runs not having enough permissions on SQL Server.
    • Scheduling BAM Packages – failure in ‘Set global connection string variables’
• 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.
    • BAM Portal - Service Unavailable
• 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.
  • BizTalk BAM Portal 400 Bad Request
• Error 5009 Registration of BAM performance counters failed New!
  • After a small amount of investigation it turn out to be a known issue where the performance counter registry has been damaged.To fix this problem open a command prompt as administrator and run: lodctr /r
    • BizTalk Installation: Error 5009 Registration of BAM performance counters failed

 

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 Known Issues and solutions with Setup and Configuration (Part 2)

• BizTalk Server Application Service (BTSNTSvc.exe) fails to start automatically after a system restart
  • After rebooting the operating system BizTalk Server 2010 services fails to start automatically, despite being configured to do so.
    • BizTalk Server Application Service (BTSNTSvc.exe) fails to start automatically after a system restart
• Microsoft SQL Server Data Transformation Services (DTS) 2008 with SP1 or higher for BAM Archiving is not installed on the local machine. Please install Microsoft SQL Server 2008 Integration Services. (Microsoft.BizTalk.BAM.CfgExtHelper.ToolsHelper)
  • This error makes it sound like you need to install SQL Server Integration Services (SSIS) which is a little misleading.
    • BizTalk 2009: Unable to configure BAMArchive
    • BizTalk 2010 – BAM Tools configuration error: Microsoft SQL Server Data Transformation Services (DTS) 2008 with SP1 or higher for BAM Archiving is not installed on the local machine.
• The service instance will remain suspended until administratively resumed or terminated. If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception. Inner exception: The event log file is full
  • The event viewer is not properly configured and it reached to the maximum limit of the log file. This causes that when we tried to write in EV he throws this type of exception.
    • Inner exception: The event log file is full: The service instance will remain suspended until administratively resumed or terminated
• “Could not open certificate store.” and “The system cannot find the file specified. (System)”
  • For BizTalk Remote Administration, one need to have the Administration tools and Monitoring feature installed on a Non-BizTalk server as in the below screenshot. Once installed, you get the administration console tool to connect to any BizTalk group in the domain and can do the admin stuff.
    • BizTalk Server Remote Administration issue: “Could not open certificate store.” and “The system cannot find the file specified. (System)”
• Could not create SSOSQL. To fix the problem, reinstall SSO or try ‘regasm SSOSQL.dll’ from a Visual Studio command prompt.
  • For some reason the Enterprise Single Sign-On Service stopped working in one of my BizTalk machines.
    • Fixing BizTalk ENTSSO – Could not create SSOSQL. To fix the problem, reinstall SSO or try ‘regasm SSOSQL.dll’ from a Visual Studio command prompt
• An error occurred while processing the last operation. Error code 8004E00F – COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator.
  • MSDTC errors when BizTalk Cluster is destroyed
• Start registering ASP.NET scriptmap (2.0.50727) at W3SVC/2/Root/BAM. Error when validating the IIS path (W3SVC/2/Root/BAM). Error code = 0×80040154
  • The error indicates that IIS is in 64 bit mode, while this application is a 32 bit application and thus not compatible. (Microsoft.BizTalk.Bam.CfgExtHelper.Utility)
    • BAM Portal Configuration Error
• Windows could not start the Enterprise Single Sign-On Service service on Local Computer. Error 0×80131700: 0×80131700
  • To issue started because it unregisterd SSOSQL.dll which is found on C:\Program Files\Common Files\Enterprise Single Sign-On folder. To register it again run regasm on the VS command prompt from your 32-Bit machine.
    • Enterprise SSO service start failure due to installation of VS2010
• This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem
  • You might get this problem if you have made some mistakes while modifying the BTSNTSvc.exe.config or BTSNTSvc64.exe.config file.
    • Error: 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.”
  • You might get this error in while using the WCF adapter in BizTalk server 2010 if specified the wrong framework for App Pool in IIS
    • Error: “The document specification ‘...’ from assembly ‘...’ failed to load.”
• WCF Service: Error: “Root element is missing”
  • For details see: Error: “Root element is missing”
• Error Code: 0x8004E004, There is no MTS object context
  • This error occurs when trying to create an adapter handler/ performing some operation in BizTalk admin console
    • BizTalk: Error Code: 0x8004E004, There is no MTS object context
• “Could not open certificate store.” and “The system cannot find the file specified. (System)”
  • This error occurs when connecting remotely via Biztalk Admin Console and navigating through the properties of any send port. On a newly installed computer, the Other People Certificate store is not initialized unless you access it once. During the Group configuration, you can initialize this other people store, and as a result we do not see this error on a computer on which group configuration has been done
    • BizTalk Server Remote Administration issue: “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 configuired with Windows SharePoint Services. Refer to the documentation for instructions on extending a virtual Server (CWssAdaCfg)”
  • Configuring the WSS adapter in BizTalk 2010
• “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
    • BizTalk 2010 BAM Tools Installation Woes
• “SGEN : error : Cannot generate serialization assembly because it already exists. Use /force to force an overwrite of the existing assembly.”
  • Resolving an obscure BizTalk 2010 build issue

 

BizTalk 2010 – List of Others Known Issues and Solutions

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

• BizTalk 2010 – List of Known Issues and solutions (Part 1)
• Common Issues and Resolutions with the BizTalk Server Administration console New!
• BizTalk Orchestration Performance: Thoughts from BizTalk Support New!
• Common EDI errors New!

 

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.

 

 

 

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)
  • Error when expanding ‘Application’ in the BizTalk 2006 Admin Console
  • Failed to Enable constraints in Admin Console
• Could not enlist orchestration <type details here>. Value does not fall within the expected range.
  • Turns out there’s a bug in BizTalk 2006 that prevents orchestrations from enlisting if not all orchestrations in an application are configured to run on the same host.
    • Value does not fall within the expected range, when starting application
• "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
    • Problem Enlisting Send Port
• 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
    • Further MS-DTC Issues – Check the Startup Order of Clustered Services
• "An error has occurred while establishing a connection to the server"
  • This happens if you receive a copy of someone elses project - since the servername is listed in the projectname.btproj.user file that is a part of the project - and you try to deploy it directly from Visual Studio.
    
    • Deployment: 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)"
  • As the error mentions, the fully qualified file name of the artefacts must be less than 260 characters, and the directory name must be less than 248 characters.
    
    • The specified path, file name, or both are too long.
• "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!
  • BizTalk Powershell Provider on Windows Server 2008 R2
• Error 1053: The service did not respond to the start or control request in a timely fashion New!
  
  • 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 ocassion. The other option is to change the timeout property in the registry.

 

Warnings

 

The following are the known Warnings associated to BizTalk:

 

• Cannot resolve the ‘schemaLocation’ attribute
  • It turned out that the BizTalk compiler is quite strict in the way the imports are defined for schemas in other assemblies. 
    • Warning – Cannot resolve the ‘schemaLocation’ attribute

 

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)" New!
  • After some research, I found out this was a problem with the DTC service, which was not enabled on the BizTalk360 machine. 
    • BizTalk360 and DTC
• 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!
  • The main reason for this exception is due to multiple bindings enabled for the the IIS website under which BizTalk360 is installed. 
    • Error: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection

 

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. New!
  • ESB Toolkit 64-bit Issue
• Access denied: Source: Microsoft.Practices.ESB.BizTalkOperations.BizTalkQuery; Method: Void .ctor(); Error Source: System.Management; Error TargetSite: Void ThrowWithExtendedInfo(System.Management.ManagementStatus) New!
  • Cannot open log for source ‘BizTalk ESB Toolkit 2.1′
• Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′. New!
  • ESB.BizTalkOperationsService fails to start 
• 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!

 

---

See also

• BizTalk Server Resources on the TechNet Wiki