Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Unable to send msg with error: A previously existing connection with the same peer was found after...


Unable to send msg with error: A previously existing connection with the same peer was found after DNS lookup.

Author
Message
sql server developer
sql server developer
SSC-Enthusiastic
SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)

Group: General Forum Members
Points: 162 Visits: 472
Hi All,

I'm receiving the following error when trying to send a message in service broker. I found the below error message in the sys.transmission_queue on the initiator side.

"A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State 116."

Any kind of suggestion would be highly appreciated

Thanks in advance!
sql server developer
sql server developer
SSC-Enthusiastic
SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)

Group: General Forum Members
Points: 162 Visits: 472
As an additional info, i found the below information in the profiler

EventClass:
Broker: Message Clasify
The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied.
EventSubClass: 3 - Delayed

But the target service exists and it has been working untill yesterday evening. It has stopped working all of a sudden without any change.

EventClass:
Broker:Message Undeliverable
The message could not be delivered because it could not be classified. Enable broker message classification trace to see the reason for the failure.
EvenSubClass: 1 - Sequenced Message

Thanks,
sql server developer
sql server developer
SSC-Enthusiastic
SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)

Group: General Forum Members
Points: 162 Visits: 472
Restarting the SQL Server service on the initiator side resolved the issue.
Thanks so much everyone for the suggestion!!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search