Biztalk: The “XLangTask” task failed unexpectedly

Last Monday I started, mainly, a Biztalk contract with a previous client. When I tried to build some of the work I have done before I was getting the following error:

Error 1 The “XLangTask” task failed unexpectedly.
System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {1BBA9F19-D4CC-34AA-918C-44FEF11E8274} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
at Microsoft.VisualStudio.BizTalkProject.Compiler.XLangCompiler.Compile(BizTalkBuildSnapshot buildSnapshot, IEnumerable`1 orchestrationFilesToCompile, String switches, String outputPath, List`1& generatedCodeFiles)
at Microsoft.VisualStudio.BizTalkProject.BuildTasks.XLangTask.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult)

The environment was:
Windows Server 2008 R2
Biztalk 2010 Enterprise Edition
SQL Server 2008 R2
VS2010 Ultimate

I tried few things like cleaning the solution, change the build target ..etc. Nothing worked. Finally, I decided to repair Biztalk:

Control Panel –> UnInstall Programs –> click Microsoft Biztalk Server Enterprise Edition –> Uninstall/Change. Choose Repair option when prompted

And That fixed it

Cumulative update packages for BizTalk Server 2010

List of Cumulative update packages  for BizTalk Server 2010

Cumulative update package 1 for BizTalk Server 2010

Cumulative update package 2 for BizTalk Server 2010

Cumulative update package 3 for BizTalk Server 2010

Cumulative update package 4 for BizTalk Server 2010

Cumulative update package 5 for BizTalk Server 2010

Biztalk Configure WCF-SQL Adapter for Outbound Operation using Typed Stored Procedure

• Follow the steps in section Consume Adapter Service
• Select sqlBinding from the dropdown
• Click the Configure button

  

• In the secure tab, select Windows from the “client credential type” drop down
• In the URI Properties tab, enter the Server name, InstanceName and IntialCatalog. In the following figure the server is “LocalHost”, we are using the default instance, and IntialCatalog the name of the adventureworks2008R2 database

  

• Click Binding Properties

  

• Click Ok
• Click the Connect button
• Select Client (Outbound operations)
• Click Strongly-Typed Procedures from the “Select a category” list
• Select a stored procedure from the “Available categories and operations” list
• Click the Add button. Notice that the stored procedure is now list in the “Added categories and operations”
• You can click the properties button to view the schema that will be generated
• You can add multiple stored procedures if you want to have them all under one schema

  

• Click OK
• Notice in the solution explorer window that two files are add; one is the xsd schema and the other is the binding xml file

  

• IMPORTANT:
  • You can add the schema to the Schmas or any other folder. Make sure you modify the name space
  • You can change the Type Name and File Name

  

  • Open the XSD file by double clicking on it
  • Select the Schema Node

  

  • Make sure that you DO NOT change the target Namespace
  • Make sure you DO NOT modify the elements’ names

  

• Import port binding by following these steps
  • Open Biztalk admin console
  • Expand Biztalk server administration
  • Expand Biztalk groups
  • Expand Applications
  • Right click on the application you want to import the port to
  • Select Import à bindings
  • Select the generated xml file from step 16
  • Select the send ports node

  

  • Double click on the send port

    

  • Click Configure
  • If you only have one operation, Copy the value of the Action element, clear the textbox and past the copied value into the textbox

    

  • Click Ok

Consume Adapter Service in Biztalk Application

• Right click on the Biztalk project
• Click AddàAdd Generated Items

• Click Consume Adapter Service

• Click Add

Configure WCF-SQL Adapter for Inbound Operation with FOR XML Clause

Add Generated Item option in visual studio does NOT generate proper schema when using FOR XML EXPLICIT clause. This post shows how to configure a receive port to consume WCF service. Make sure that your application has been deployed before following the next steps

The following steps are to configure the WCF-SQL adapter to poll data:

• Open Biztalk server administrator console
• Expand your application
• Select Receive ports node

  

• Right click Receive Ports node
• Select NewàOne-way Receive Port

• Name the port
• Click Receive Locations on the left panel
• Click new to add a new Receive Location

  

• Name the new receive location

• Set Type dropdown to WCF-SQL
• Set Receive pipeline to XMLReceive or any other custom pipeline
• Click Configure button. You will get the following dialog

  

• In the General tab, enter the SQL Server Address URI or click Configure. Clicking Configure shows the following dialog

  

• Fill the following properties
  • Server name: for this walkthrough, I am using localhost because the SQL server is on the same machine as the dev box
  • InstanceName: leave blank if the instance name is the default instance
  • InitialCatalog: name of the database that contains the stored procedure
  • InboundId: use the stored procedure name. InboundId is used to make the URI unique. Biztalk requires the URI to be unique in an application. For more info read http://msdn.microsoft.com/en-us/library/dd787908(v=BTS.70).aspx
• Click OK
• Go to the Binding tab and fill the following properties

  

  • XmlStoredProcedureRootNodeName : The adapter will insert a root element to the received schema with this name and the name space of XmlStoredProcedureRootNodeNamespace. Make sure that the name matches the name in the xml document
  • XmlStoredProcedureRootNodeNamespace: The namespace for the RootNode in the previous step to be injected by the adapter. Namespace must match the namespace in the xml document
  • InboundOperationType: Because our stored procedure contains FOR XML EXPLICIT, we must use XmlPolling
  • PolledDataAvailableStatement: The sql statement is executed by adapter to check if data is available for polling
  • PollingIntervalInSeconds: How often, in seconds, do we want to poll data from the database. The lower the number, the more frequent the adapter hits the database and the busier Biztalk application will be in case the data is available
  • PollingStatement: the sql statement to be executed to poll data from the database
  • pollWhileDataFound: Set to false. For more info read http://msdn.microsoft.com/en-us/library/dd788416(v=BTS.70).aspx
  • UseAmbientTransaction: true to enable transactional behaviour
• Configure the other tabs if needed
• Click OK to finish configuring the receive location
• Click OK to finish configuring the receive port
• Now your port is ready for usage

DB2 The user does not have the authority to access the host resource. Check your authentication credentials or contact your system administrator

Deploying the DB2 ports using the deployment framework generated authorization error (shows as warning in the event log) when starting the Biztalk application

The adapter “DB2” raised an error message. Details “The user does not have the authority to access the host resource. Check your authentication credentials or contact your system administrator.”.

To fix that above issue, the DB2 password needs to be typed in the connection string. It seems the deployment framework or exporting the binding doesn’t capture the password.