Thursday, July 28, 2005 1:06 PM
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.
Thursday, July 28, 2005 10:30 PMThat 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.
Friday, July 29, 2005 5:45 PMThx,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 ?
Saturday, July 30, 2005 5:11 PMAFAIK, 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.
Tuesday, December 08, 2009 10:25 AMCould please let me know what did you do as I am facing the same issue.
Tuesday, December 08, 2009 5:16 PMModeratorPlease 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.
Thursday, November 25, 2010 3:42 PMThank you! Could you give more explanation on it?
Tuesday, March 06, 2012 1:37 PM
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).