Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Unable to send msg with error: A previously existing connection with the same peer was found after DNS lookup. Expand / Collapse
Author
Message
Posted Wednesday, November 9, 2011 8:03 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, September 15, 2014 2:16 PM
Points: 151, Visits: 436
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!
Post #1203231
Posted Thursday, November 10, 2011 11:49 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, September 15, 2014 2:16 PM
Points: 151, Visits: 436
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,

Post #1203766
Posted Friday, November 25, 2011 11:09 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, September 15, 2014 2:16 PM
Points: 151, Visits: 436
Restarting the SQL Server service on the initiator side resolved the issue.
Thanks so much everyone for the suggestion!!
Post #1212090
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse