locked
OutgoingMessagesInQueue is large, replication works RRS feed

  • Question

  • Hi,

    I am pretty well with SCCM, but when it comes to Inbox messages I am newb. Recently I discoverd that number of outgoing messages in queue is 140723 and Conflict Count is 10k+. We are running primary site with 3 secondary sites, and all of them are functioning as they should. Database replication has no issues between sites. Can somebody point me to the right direction, so I can start troubleshooting this large queue count? I would like to upgrade to 1706, but prerequisite check is poping up the warning about Backlogged Inboxes. Are those two things somehow connected?


    • Edited by supaFlaj Friday, November 17, 2017 10:44 AM
    Friday, November 17, 2017 10:43 AM

All replies

  • Hi,

    There are some very good information and hints for your reference.

    How to Fix SCCM ConfigMgr Inbox Backlog Issues

    https://www.anoopcnair.com/sccm-configmgr-2012-how-to-check-for-backlog/


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 20, 2017 8:17 AM
  • Hi, yes, I followed those instructions, but there are no solutions in this article. I discovered that there is dbo.AlertVariableChangeTargetQueue queue that is disabled in System Broker System Queues. What does this Queue stands for?

    I also have 140k+ handles in queue:

    Where else can I look for some logs, so I would get a better picture on how to proceed with troubleshooting?

    Monday, November 20, 2017 12:17 PM
  • Were you able to resolve this. I have the same issue.
    Tuesday, September 11, 2018 12:12 PM
  • Hi, no I'm still experiencing this issue. Just today I tried to update SCCM from 1606 to 1702, but it fails because of this warning. I have one parent site PSM and three child sites CGP, SRB and SRS

    I have ran query on sccm database: select * from DrsConflictInfo and the output is:

    249887 29 ObjectDistributionState Upsert Conflict 2018-09-13 12:00:40.197 The same row was upserted at PSM and CGP. The resolver chose the upsert from PSM as the winner. <row ID="" SourceSiteCode="" DestinationSiteCode="" Type="33554432" /> CGP <row ID="" SourceSiteCode="" DestinationSiteCode="" Type="33554432" Stage="33619968" State="33619971" Code="0" PackageVersion="0" LastUpdateTime="2018-09-13T11:57:58.633"/> <row ID="" SourceSiteCode="" DestinationSiteCode="" Type="33554432" Stage="33619968" State="33619971" Code="0" PackageVersion="0" LastUpdateTime="2018-09-13T11:54:55.960"/> 51529974 51529980

    249886 29 ObjectDistributionState Upsert Conflict 2018-09-13 11:58:41.887 The same row was upserted at PSM and SRB. The resolver chose the upsert from PSM as the winner. <row ID="" SourceSiteCode="" DestinationSiteCode="" Type="33554432" /> SRB <row ID="" SourceSiteCode="" DestinationSiteCode="" Type="33554432" Stage="33619968" State="33619971" Code="0" PackageVersion="0" LastUpdateTime="2018-09-13T11:57:22.377"/> <row ID="" SourceSiteCode="" DestinationSiteCode="" Type="33554432" Stage="33619968" State="33619971" Code="0" PackageVersion="0" LastUpdateTime="2018-09-13T11:54:55.960"/> 51529974 51529980

    Any clues?


    • Edited by supaFlaj Thursday, September 13, 2018 12:32 PM
    Thursday, September 13, 2018 11:44 AM