none
SSBDT: Dialog timer delete during dispatch with SQL Server 2012 SP3

    Question

  • Hello,

    Since two months I can see many entries with the below sentences in SQL logs.

    2017-04-24 22:01:43.900 spid31s      SSBDT: Dialog timer delete during registration (did: 725D87C0-8AAF-4383-BCFC-725AC025CD1D:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:02:41.290 spid31s      SSBDT: Dialog timer delete during registration (did: 6F5BF516-934A-45E4-B1B1-D60DF3401B4E:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:03:17.650 spid31s      SSBDT: Dialog timer delete during registration (did: F044EE94-7203-4FF5-9BB6-00D21B86E686:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:03:22.350 spid31s      SSBDT: Dialog timer delete during registration (did: 0B92D137-915C-4920-9C69-541F87266D90:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:03:37.980 spid31s      SSBDT: Dialog timer delete during registration (did: 958A51D1-B18F-410F-93B5-358D10C81EF5:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:03:40.310 spid31s      SSBDT: Dialog timer delete during registration (did: 14373439-9330-4E2C-BF2B-6901A3ED42BF:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:07:39.000 spid31s      SSBDT: Dialog timer delete during registration (did: 6E9C57B7-BDD5-42BC-BA9A-A5A3F97DC91A:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:08:02.360 spid31s      SSBDT: Dialog timer delete during registration (did: 98B47642-1373-4EF7-86B0-E320B48611A9:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:08:02.480 spid31s      SSBDT: Dialog timer delete during registration (did: 1D1263CE-151D-4C64-90BA-4293A29D6BD0:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:09:27.750 spid31s      SSBDT: Dialog timer delete during registration (did: C7D98CCF-F67D-450B-870B-0242585E9B07:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:09:36.700 spid31s      SSBDT: Dialog timer delete during registration (did: 0D243BC3-6B83-45A0-AF2B-E4AF24098B9D:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:09:51.270 spid31s      SSBDT: Dialog timer delete during registration (did: 4CCDA7EA-FB1E-44C7-9234-C0D7C8484750:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:10:15.450 spid31s      SSBDT: Dialog timer delete during registration (did: 2A515B80-9AFA-45F2-9ECB-1328BBB63852:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:11:10.770 spid31s      SSBDT: Dialog timer delete during registration (did: 9920B4CC-EF38-4A8C-A3AE-FAADD7D75267:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:11:15.610 spid31s      SSBDT: Dialog timer delete during registration (did: 4ABA0501-7CD2-4F58-9B59-49A7A9799092:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:11:20.960 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FAECCF7-6AC5-4FB2-84DC-4927E839D028:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:13:24.770 spid31s      SSBDT: Dialog timer delete during registration (did: A932AF41-C0D0-4234-899B-5E5A4565F924:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:13:24.910 spid31s      SSBDT: Dialog timer delete during registration (did: 00F178A3-640D-44E4-9C39-A69271B279C9:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:13:42.310 spid31s      SSBDT: Dialog timer delete during dispatch (did: 20D9F06E-BC29-4BA5-9623-E08765B42BC7:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:14:00.290 spid31s      SSBDT: Dialog timer delete during registration (did: AA47FA4F-F793-4D89-BBCB-2E434596476F:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:16:31.660 spid31s      SSBDT: Dialog timer delete during registration (did: DD35C46C-7EF0-410F-B78D-CB38DFBD4DEB:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:17:06.290 spid31s      SSBDT: Dialog timer delete during registration (did: E857E323-ED31-4FEC-9AB9-39115D50CA4E:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:18:47.130 spid31s      SSBDT: Dialog timer delete during registration (did: CEDC4256-B4F2-4844-B2DA-9F49C41DE529:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:19:06.390 spid31s      SSBDT: Dialog timer delete during registration (did: 2ACDA3E2-4449-46A8-8A64-E8DF072FEF2A:Initiator, OpType: CloseDialog OpResult: Null)
    2017-04-24 22:21:30.410 spid31s      SSBDT: Dialog timer delete during dispatch (did: E09596A9-CD56-4597-B428-DE392D542E29:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:22:32.890 spid31s      SSBDT: Dialog timer delete during dispatch (did: EC39EEE2-ACC5-49F4-A375-2CC3EA2C68CD:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:23:01.630 spid31s      SSBDT: Dialog timer delete during dispatch (did: DF7D37D2-C4C6-403B-AD77-EC070EC47F36:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:23:25.520 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FDB1B72-8C0B-49F3-B305-93DC9F52EC72:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:25:22.860 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8E7E1C64-16C7-4BB9-A77C-717B1BDF5859:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:25:45.920 spid31s      SSBDT: Dialog timer delete during dispatch (did: E47E8924-8741-48B0-BB55-2B573247CEE7:Target, OpType: DialogCleanupDispatch OpResult: Null)
    2017-04-24 22:27:17.560 spid31s      SSBDT: Dialog timer delete during dispatch (did: CBE4F1C7-A98D-424E-AD0D-339727F76937:Target, OpType: DialogCleanupDispatch OpResult: Null)

    We are using SQL server 2012 SP3

    Do you know what could be the source of that problem?

    We could not find info....

    Tuesday, May 2, 2017 7:23 AM

All replies

  • Hi ,

    We are currently looking into this issue and will give you an update as soon as possible.

    Thank you for your understanding and support.

    Regards,
    Lin

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, May 3, 2017 6:30 AM
    Moderator
  • Hi,

    From what I’ve heard this message is for debugging purpose only. It doesn’t indicate that there is any problem within your system and could be safely ignored.

    If you have any other questions, please let me know.

    Regards,
    Lin

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, May 4, 2017 7:20 AM
    Moderator
  • That is a horrible response.  The SQL Server log is filling up with data and your response is just ignore it?  This could be a production server that is logging debug information?  They obviously monitor the logs.

    OP:

    My logs started doing the same thing as soon as I executed: DBCC TRACEON (3502, 3605, -1);

    This was done to get CHECKPOINT information into the logs (see: http://sqlmag.com/blog/how-monitor-checkpoints)

    Is it possible that you have those trace flags turned on?

    Wednesday, August 9, 2017 2:05 PM
  • Hi, is there any news about this? Error Log is getting full of trash, which is not good and does not help to look for useful information. There should be a way to prevent this to be tracked in the error log if it is not necessary...
    Thursday, February 8, 2018 2:33 PM
  • I have had several thousands of these in my logs since the early hours this morning following a problem with the instance.  They have appeared prior to issue, but not even close to the volume.  As such, it's hard to review logs for critical errors with these alerts - in my case, they are absolutely not harmless.

    Clive
    www.sqlsvrdba.com

    Thursday, May 3, 2018 5:28 AM
  • We currently have the same issue on our Scom Operations Manager DB. Are there any updates ? 

    Thursday, October 11, 2018 5:07 AM
  • I just came across this error message. I am writing software that uses SqlDependency. When I changed my notification query to include [WITH (NOLOCK)] this started to occur. It created an endless loop of notifications where I would receive the notification, Stop the SqlDependency, Start the SqlDependency and notify again. I removed WITH (NOLOCK) from the notification query and the problem stopped.
    Thursday, October 25, 2018 5:43 PM