BizTalk Server: List of Errors and Warnings, Causes, and Solutions

BizTalk Server: List of Errors and Warnings, Causes, and Solutions


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′. New!
  • BizTalk Server 2013 Unit testing: "Transformation Failure". New!
    • 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:

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." New!
  • 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. New!
  • Error details: The FILE send adapter cannot open file < > for writing. Details: Access is denied. New!
  • "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() New!
    • 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 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. New!

BizTalk Runtime Issues

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

Business Activity Monitoring (BAM) Issues

The following are the known errors/issues associated with Business Activity Monitoring (BAM):

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 New!
  • Error encountered: Could not install BAM Tools while installing BizTalk Server 2013 RTM New!
  • 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 New!
    • 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." New!
    • 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" New!
  • BAM Portal configuration: "Attempted to read or write protected memory" New!
  • "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)" New!
  • "Missing MSVCP100.dll" 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:

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

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" New!
  • 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 occasion. The other option is to change the timeout property in the registry.
  •  Orchestration will not open in the Orchestration Designer

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] New!
  • 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. New!
  • Exception has been thrown by the target of an invocation. Source: Microsoft.Practices.ESB.Resolver.ResolverMgr. New!
  • 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. 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

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.

Regarding the ESB Toolkit: also check BizTalk Server ESB: Survival Guide

Leave a Comment
  • Please add 5 and 4 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Ed Price - MSFT edited Revision 244. Comment: Comma in title (consistency, per guidelines)

  • Paul Endras edited Revision 242. Comment: Deleted obsolet chars.

  • Sandro Pereira edited Revision 239. Comment: Fix link to open in a new window

  • Maheshkumar S Tiwari edited Revision 230. Comment: added error"Logon failure: The user has not been granted the requested logon type at this computer" and its  solution  

  • Sandro Pereira edited Revision 229. Comment: Change Title

  • Lex Hegt edited Revision 228. Comment: Added link to the ESB Survival Guide

  • Sandro Pereira edited Revision 224. Comment: fixed typos

  • Sandro Pereira edited Revision 221. Comment: New error: Failed to get data. If available, errors returned from the provider are listed below

  • Sandro Pereira edited Revision 220. Comment: New error: Failed to create ‘WCF-SQL’ Transport Component

  • Sandro Pereira edited Revision 217. Comment: New problem: BAM Portal Display Problems

Page 1 of 12 (112 items) 12345»
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Sandro Pereira edited Revision 1. Comment: add Visual Studio Schema Design Issues

  • Sandro Pereira edited Revision 2. Comment: Add more content

  • Sandro Pereira edited Revision 3. Comment: new content

  • Good article, it's very helpful

  • Rohit.Sharma edited Revision 5. Comment: Added few more

  • Rohit.Sharma edited Revision 6. Comment: Added few more errors

  • Great Post :)

  • Again a great post, keep it up.

  • Steef-Jan Wiggers edited Revision 7. Comment: Formatting

  • Steef-Jan Wiggers edited Revision 9. Comment: Formatting

  • Sandro Pereira edited Revision 10. Comment: Try to fix TOC

  • Sandro Pereira edited Revision 11. Comment: Try to fix TOC

  • Sandro Pereira edited Revision 12. Comment: Add Introdution

  • Thank you all. Feel free to add/change content to this topic making it always up to date.

  • Great article!

Page 1 of 10 (140 items) 12345»