iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

Copyright © 2025 · iT Synergy·

Could not enlist Send Port ‘ALL.Exceptions’. Exception from HRESULT: 0xC00CE557 (Microsoft.BizTalk.ExplorerOM)
Could not enlist Send Port ‘ALL.Exceptions’. Exception from HRESULT: 0xC00CE557 (Microsoft.BizTalk.ExplorerOM) avatar

By Leave a Comment

Problema

Después de instalar el ESB Toolkit 2.1 y al tratar de iniciar la aplicación Microsoft.Practices.ESB desde la consola de administración de BizTalk Server, no inicia correctamente porque el send port ALL.Exceptions no inicia correctamente.

Could not enlist Send Port ‘ALL.Exceptions’. Exception from HRESULT: 0xC00CE557 (Microsoft.BizTalk.ExplorerOM)

Solución

1. Desde el menu Configure.. de la aplicación Microsoft.Practices.ESB,  quitar la referencia del send port asociado a la orquestación Microsoft.Practices.ESB.Agents.Delivery.

2. Eliminar los send y receive ports que contiene la aplicación Microsoft.Practices.ESB

3. Importar los bindings  Microsoft.Practices.ESB.CORE_Bindings.xml ubicados en la ruta

  • C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit 2.1\Bindings

4. Volver a iniciar la aplicación Microsoft.Practices.ESB

Espero sirva ! 😉

DCOM was unable to communicate with the computer x.x.x.x using any of the configured protocols with BizTalk Server
DCOM was unable to communicate with the computer x.x.x.x using any of the configured protocols with BizTalk Server avatar

By Leave a Comment

Al tratar de ejecutar un procedimiento almacenado desde un receive location, el cual pretende hacer polling sobre un procedimiento almacenado de SQL Server ubicado en otro servidor se generaba el siguiente error en el log de eventos tipo System.

“DCOM was unable to communicate with the computer x.x.x.x using any of the configured protocols”

SOLUCION

Habilitar el Distributed Transaction Coordinator de manera correcta en el servidor de BizTalk.

  1. Clic Start, clic Run, digite dcomcnfg ay nd then click OK to open Component Services.
  1. En la ventana desplegada, expandir Component Services, expandir Computers, expandir My Computer, expandir Distributed Transaction Coordinator, y luego clic en Local DTC.
  1. Clic derecho Local DTC y clic Properties para mostrar su ventana de propiedades.
  2. Clic en el tab de Security.
  3. Asegurarse que queden chequeadas las siguientes cuatro opciones y las demás deben quedar limpias.
    • Network DTC Access
    • Allow Inbound
    • Allow Outbound
    • No Authentication Required

clip_image001

  1. Clic OK para cerrar la ventana. Esto reiniciará el MSDTC service, clic Yes para confirmar.
  2. Clic Start, seleccione Administrative Tools, y luego clic en Windows Firewall with Advanced Security.
  3. En el Windows Firewall with Advanced Security, clic en Inbound Rules.
  1. En el panel de Inbound Rules, clic derecho en Distributed Transaction Coordinator *, y clic en Enable Rule.

clip_image002

  1. Luego clic Outbound Rules, dar clic derecho en las reglas de Distributed Transaction Coordinator * y clic en Enable Rule.

clip_image003

  1. Abrir la ventana de Services en el Control Panel
  2. Reiniciar el servicio COM+ System Application.
  3. Reiniciar el servicio Distributed Transaction Coordinator.
  4. Reiniciar el servicio SQL Server (MSSQLSERVER).

Nota: No olvidar también configurar el DTC en el servidor remoto donde se encuentra el SQL Server.

How to configure a polling statement using Oracle adapter in Biztalk 2010
How to configure a polling statement using Oracle adapter in Biztalk 2010 avatar

By Leave a Comment

We have many different ways to poll the Oracle database such as: Select Statements, functions or store procedures. I am going to write about a specific way of polling Oracle Database: Store Procedures. We have to be very careful writing the parameters properly.

I am going to describe the step we have to follow to import the schemas and binding from the Oracle database.

First of all we have to select the binding we are going to use, and then we have to connect to the Oracle database, for that we have to introduce the username and password as show below it.

Then we have to specified the Data source name where the store procedure is, and in this case specified a polling Id, this field can be fill with anything you want, I mean you can use numbers and/or  letters.

 

 

In this step we can configure the binding properties like that:

  • Polled Data available Statement: Indicates the query which tells us if there are any data to poll.
  • Polling actions: Indicates the URL where the Store procedure is, its name looks something like that:

http://Microsoft.LobServices.OracleDB/2007/03/PP/PackageName/StoreProcedureName

  • Polling statement: It is a XML Code which indicates the store procedure we want to use to get the data we are looking for, and the parameters we have to send to it to get the information. Here is very important that all the fields are in capital letter, if not we are going to get and error.

<StoreProcedureName xmlns=”http://Microsoft.LobServices.OracleDB/2007/03/USER/Package/NamePackage”>

<PARAMETER1>12</ PARAMETER1>

< PARAMETER2>Evento</ PARAMETER2>

</ StoreProcedureName >

 

Remember  the name of the field or parameter is in capital letter, otherwise you get and error when you run the application.

When you have imported the schemas, you have to build and deploy the application in visual studio. Then in Biztalk Server Administration console you have to import the binding which was generated when you import the schemas.