Service Broker "The target service name could not be found.."

  • Hi I wonder if anyone can help...

    I've restored a broker db backup onto a single instance, 2014 environment. I've re-enabled broker, set the correct db authorization & set new broker ID with immediate rollback.

    I've changed the route to reflect the new broker guid and in my conversation start proc I've amended the selected service target broker reference to reflect the change in broker guid

    But still Im getting the following message in sys.transmission_queue and the messages are stuck there

    "The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied."

    what am I missing ?! (a brain maybe but aside from that.......)

  • Hard to troubleshoot without accessing your instances and drilling down step by step, but here is my wild guess. Did you change/create routes on both instances to point to the correct server addresses? If you use multi-hop routes, are they fully configured for the new architecture? Are all endpoints configured correctly?

    Consider setting up a new test service between the instances; if you can get that to work, compare all settings until you spot the difference.

    Read all posts Remus Rusanu has ever written on Service Broker.


    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog: https://sqlserverfast.com/blog/
    SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/

  • thank you Hugo I will give that a go 🙂

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply