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

SERVICE_BROKER_TRANSMISSION_WORKTABLE Error Expand / Collapse
Author
Message
Posted Tuesday, November 3, 2009 7:30 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, August 15, 2014 1:39 PM
Points: 26, Visits: 321
Hi Everyone,

We have a nightly job which stops and starts one of our SQL Server 2008 instances. The job failed last night and when I look in the sql server log the following error/message kept appearing around the time the job was trying to stop sql server:

Timeout occurred while waiting for latch: class 'SERVICE_BROKER_TRANSMISSION_WORKTABLE', id 0000000003D51620, type 4, Task 0x0000000005E68988 : 0, waittime 1500, flags 0x1a, owning task 0x0000000007904BC8. Continuing to wait.


Any ideas as to what might be happening? As far as I know we don't use service broker functionality...however we do have it enabled in most of the databases in this instance. Any help would be appreciated.

Thanks
Post #812919
Posted Wednesday, November 4, 2009 6:05 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Thursday, June 5, 2014 10:54 AM
Points: 9,902, Visits: 9,480
Do you use DB Mirroring or DM Mail on that instance?

-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #813943
Posted Thursday, November 5, 2009 5:46 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, August 15, 2014 1:39 PM
Points: 26, Visits: 321
No..we aren't using either of them. Database Mail is not enabled on the instance. I'm thinking that I should probably just disable the broker in all the databases...but I'm still baffled as to how this error occured even though we don't use the broker for anything.
Post #814164
Posted Wednesday, August 14, 2013 10:13 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 11:16 AM
Points: 14, Visits: 324
I had the same problem but I am using SQL Server 2008 R2 SP1 with a service broker, but there is no information on internet about this problem.

Did you solve it?
Post #1484392
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse