Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Service Broker / February 2007

Tip: Looking for answers? Try searching our database.

Service Broker messages stuck in sys.transmission_queue

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Terry - 27 Feb 2007 23:04 GMT
Hello,
I'm testing service broker on two machines in the same domain. I'm using
windows authentication. When I begin a dialog on serverA the message is
immediately put into the sys.transmission_queue with a blank
transmission_status, and is_conversation_error = 0. Also, I specified the
broker instance in the route, but the to_broker_instance field for the
message in sys.transmission_queue on ServerA is blank.

Any help would be appreciated. i've gone through several examples and
cannot get this message delivered to the queue on ServerB.

-T
Bob Beauchemin - 28 Feb 2007 01:05 GMT
Replied on microsoft.public.sqlserver.programming...

Bob Beauchemin
SQLskills

> Hello,
> I'm testing service broker on two machines in the same domain. I'm using
[quoted text clipped - 8 lines]
>
> -T
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.