Acknowledgement Won't Send: An Error Occurred While Receiving Data: '121(The Semaphore Timeout Period Has Expired.)'.

Any idea of what this means?

My acknowledgement messages are getting stuck in sys.transmission_queue. In profiler, the message generated by the target server (the one sending the ack) is:

This message could not be delivered because it is a duplicate.

The result of the function GET_TRANSMISSION_STATUS is

An error occurred while receiving data: '121(The semaphore timeout period has expired.)'.

Each time I send a new mesage I get one record in sys.conversation_endpoints and two in sys.transmission_queue. The two records in the transmission_queue are the same except one has a NULL for the message body and is_end_of_dialog=1

If I try to clean out the queues they re-populate (I guess becasue the initiator keeps re-trying the message?)

I have double checked my routes back to the initiator and they seem correct (see below). In fact, a second server is using an identical route and it is working OK.

The only thing tricky on this machine is added a second message queue for a differnet kind of message, and it is replying to a different service broker instance. In other words, on server A, database "Production" sends a message to server B, database "Destination" and Server A, database "Schedule" also sends a message to server B, database "Destination".

In the respective return routes I have double checked the guid for the broker_instance.

The broker_instance value in each return route is right out of server A's sys.databses view:

name service_broker_guid

-------------------------------------------------------------------------------------------------
Production 3BE812A8-5212-45D2-8664-521F83689585

Schedule 86113D85-A594-4EAB-8460-3E459EE8F055


The return routes look like this:


CREATE ROUTE [SendReplyProduction] AUTHORIZATION [mssqlssb]

WITH SERVICE_NAME = N'//mycompany.com/SSB/Services/ProductionChangeService' ,

BROKER_INSTANCE = N'3BE812A8-5212-45D2-8664-521F83689585' ,

ADDRESS = N'TCP://Server_A:4022'

The above route should send the reply to the "Production" database on Server A


CREATE ROUTE [SendReplySchedule] AUTHORIZATION [mssqlssb]

WITH SERVICE_NAME = N'//mycompany.com/SSB/Services/ScheduleChangeService' ,

BROKER_INSTANCE = N'86113D85-A594-4EAB-8460-3E459EE8F055' ,

ADDRESS = N'TCP://Server_A:4022'

The above route should send the reply to the "Schedule" database on Server A


Is this the correct way to do it? And can anyone tell me why I get the semaphore error?

For what it is worth, I am using Transport security only with windows authentication (both machines on the same domain and no certificates)

Thanks for any help!
John