SqlDependency start() throws a strange exception RRS feed

  • Question

  • Hi guys,

     We have a load balanced environment with two servers. They are sharing the same configuration file, same pool and the same domain. We are starting the SQL Dependency on Application_Start and stop it on Application_End. Is this approach generally valid for starting and stopping the dependency?

    Normally, we have two instances of the Sql Query Notification Services, but at some point one of the Sql Query Notification Service disappears, and the corresponding node stops invalidating it's data and experiencing problems with getting the correct data, which leads to problems and errors.

    If we force the start of the Sql Query Notification Service manually by setting a particular page to do this, we are receiving this error:


    SqlDependency does not support calling Start() with different connection strings having the same server, user, and database in the same app domain.

    The only thing fixing the problem is recycling both our nodes, which is very inconvenient and hard to support. What is more, the Sql Query Notification Service disappears on very random basis, so we cannot understand why it actually disappears.


    Any help is much appreciated,

    Thanks in advance!

    • Moved by Pawel Marciniak Monday, April 19, 2010 6:18 PM (From:SQL Service Broker)
    Monday, April 19, 2010 2:09 PM

All replies

  • This problem looks unsolvable, since 2010 no answers !!!!!!!!!!!!!!!!!

    I am suffering with the same problem since i have used service broker.

    Saturday, June 4, 2011 6:58 AM