Revision #62

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


Introdution

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 New!
  • 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.". New!
  • Error 23 Exception Caught: Mapper Compiler: Functoid not found: guid ({5DE500CC-45BC-454B-A23D-24449899042C}) with functoid id (6124). New!
    • 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 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". New!

BizTalk Runtime Issues

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

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) New!
  • 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. New!
  • Could not enlist orchestration <type details here>. Value does not fall within the expected range. New!
  • "Could not enlist send port '[Send Port Name]' Exception from HRESULT: 0xC00CE557(Microsoft.BizTalk.ExplorerOM) ". New!
    • 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). New!
    • 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" New!
  • "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)" New!

Warnings

The following are the known Warnings associated to BizTalk:

See also BizTalk Server Resources on the TechNet Wiki