יום חמישי 28 יולי 2005 13:06
When I send message from Server1 to Server2,I found the error "This message could not be delivered because it is duplicate" in SQLProfiler on Target, why message can be duplicate ? who can help me?
My environment is :
Instance1 on Server1,Instance2 and Instance3 on Server2,Instance1 and Instance2 is a sqlserver2005 cluster,message is sent from Instance1 to Instance3.
יום חמישי 28 יולי 2005 22:30That means that the source is resending the message because it didn't receive the acknowledgement from the target. The second time the target gets the message it looks in the conversation endpoint and finds it already has that message. The most common cause for that is the route from the target machine back to the initiator machine is missing or wrong. A firewall on the initiator can also block the returning acknowlegements.
יום שישי 29 יולי 2005 17:45Thx,it is really helpful for my problem.
BTW,Because I have encountered many problem when I built up service broker. where can I find all error detail of service broker ?
שבת 30 יולי 2005 17:11AFAIK, there is no real good source for error info. Try Roger's book, there may be some info there. Whet problems are you encountering? BTW, some of your best friends when trying to solve SSB problems are the sys.transmission_queue queue and the SQL Server Profiler.
יום שלישי 08 דצמבר 2009 10:25Could please let me know what did you do as I am facing the same issue.
יום שלישי 08 דצמבר 2009 17:16מנחה דיוןPlease describe your issue. The situation described by the original poster is not a real issue. From time to time (especially after establishing new network connection) the initiator will re-send a message before it receives an acknowledgment. In such cases the target will have to drop the message as a duplicate. This is normal, and as long as the message traffic continues to flow, you shouldn't worry about it.
יום חמישי 25 נובמבר 2010 15:42Thank you! Could you give more explanation on it?
יום שלישי 06 מרץ 2012 13:37
I just ran into this issue (again, for about the 5th time). Everytime I see this it's a routing problem from my target back to my initator. The one key thing is that if you're using the MIRROR_ADDRESS = within your CREATE ROUTE and the database is NOT mirrored, you need to remove the MIRROR_ADDRESS (drop and recreate the route, you cannot simply ALTER to remove the MIRROR_ADDRESS).