EndDialog messages are stuck in the TARGET(remote) transmission queue. The transmission\_status is blank on each entry.

The Initiator is actually receiving the EndDialog message and ending the dialog on it's side.

I know that for sure because I have put a PRINT on the INITIATOR service reply queue procedure. The log shows that those procedure are getting executed as a result of the INITIATOR receiving an EndDialog message.

Everything works except that in the TARGET, conversation endpoint entries remain in DO state and the EndDialog message also remains in the TARGET transmission queue.

It looks like the TARGET is not getting an ACK from the INITIATOR for the enddialog message.

On the TARGET the BROKER:CONVERSATION trace shows STARTED\_INBOUND, CONVERSING, DISCONNECTED\_OUTBOUND states.

Follow configuration:

TARGET: Windows Server 2003 R2 Standard 64 edition SP2, SQL Server 2008 SP2, Standard Edition 64-bit, database in compatibility mode 100

INITIATOR: Windows XP SP2, SQL Server 2005 express SP2, Database in compatibility mode 80.

Do you have any advice on how to solve this issue?