Fix: The ConfigMgr 2007 database grows excessively large and DPs do not honor the "Number of retries" and "Delay before retrying (minutes)" retry settings

Fix: The ConfigMgr 2007 database grows excessively large and DPs do not honor the "Number of retries" and "Delay before retrying (minutes)" retry settings

  • Comments 4
  • Likes

Toolbox3You may notice that an unusually large number of System Center Configuration Manager 2007 status messages are generated causing significant growth in database size.  Further investigation also shows a large number of these entries repeating over and over again in the distmgr.log:

Compressed files for package xxx hasn't arrived from site xxx

Note: These messages can occur on a normally functioning site.  It is only a cause for concern when an excessively large number are repeatedly seen.

This can be caused by the issue documented in the following Knowledge Base articles:

SP1 version:  KB978875 - The Distribution Manager does not honor the "Number of retries" and "Delay before retrying (minutes)" retry settings on SCCM 2007 SP1 site servers

SP2 and later version:  KB978021 - The Distribution Manager that is in System Center Configuration Manager 2007 SP2 does not honor the "Number of retries" and "Delay before retrying (minutes)" retry settings

To resolve this issue apply the appropriate hotfix referenced above.

Troubleshooting and verification:

You can use this script to determine that the status specific tables are largest in the ConfigMgr database:

http://www.sqlteam.com/article/finding-the-biggest-tables-in-a-database

Then you can use these queries to determine the components generating the most status messages.  In this specific scenario you'll find that it is Distribution Manager.

select Component, count(*) from vStatusMessages group by Component order by count(*) desc
select MessageID, count(*) from vStatusMessages group by MessageID order by count(*) desc

ref: http://blogs.technet.com/b/configurationmgr/archive/2009/01/27/troubleshooting-database-growth-issues-in-configuration-manager-2007.aspx

You should find that the SMS_DISTRIBUTION_MANAGER thread has been generating status message ID's 2342, 2300 and 2301 or similar every 5 seconds, repeatedly.

So what's the takeaway from all this? 

If you have System Center Configuration Manager 2007 SP1 or later and are doing software distribution then you need this hotfix!

Clint Koenig | Senior Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • To your point of:

    If you have System Center Configuration Manager 2007 SP1 or later and are doing software distribution then you need this hotfix!

    Even if the DP role isn't installed on the site server?  This goes against what the KB article says when it states, "The distribution point role is installed on a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) site server. "  I don't have the DP role installed on my site server.  The DPs in my environment are only DPs (and some are PXE service points), but none of them are Site Servers.  Am I missing something?

  • Good Sharing Hornbeck !

    isnt it imporant that you or MS folks respond to valid questions aked on these blogs, defeating the whole purpose of blogging. Since when you started thinking that after blog my responsibility is over ? Question is so valid and important to attend, dont you think so ?

    If you guys think PSS is only customers go, blogging itself defeats its own purpose

  • Its a shame that engineers do not get their name posted on the tech-article as this was my issue and MS had never seen it before,  But the pain that I had to go thru in getting them to understand and create the Hot fix..  

  • I don't know if someone will answer my questions but if DP is no longer exists (decommissioned a few months ago) and I have a similar situation, where should I apply the hotfix? the new DP that is trying to send the package? do I have to install the hotfix on every DPs from parent sites to all secondary sites?

    Thanks,