My Distribution Manager component status is getting hammered with these messages, ID's 2300 and 2301.
Message ID 2300: SMS Distribution Manager is beginning to process package "Adobe Shockwave Player" (package ID = MMH0011F).
Message ID 2301: SMS Distribution Manager successfully processed package "Adobe Shockwave Player" (package ID = MMH0011F).
It's doing that for 5 different software packages. And both of these status ID's repeat about every 30 seconds, for each of these 5 packages. I am running SCCM 2007 R2/SP2, and am aware of the hotfix to address the system not honoring the settings for the package distribution retry timer, and have already applied that. That didn't change anything, and even if it did, it wouldn't fix my problem, it would just space the messages out farther. I've looked in the distmgr.log file, and didn't see any errors. Maybe if someone can tell me something specifically to look for, or I can just paste a segment of the log if that will help. Or are there any other logfiles I should be checking? Any help would be much appreciated.
This has happened to me before, and deleting the package and creating a new one has fixed it in the past, but I don't really consider that a fix, just a work around, and would like to find out the proper way to fix this. It shouldn't be happening in the first place, and deleting/recreating the package is akin to ignoring the problem, in my opinion.
On a possibly-related note, my site has 4 distribution points - 2 of which are Branch DP's. I tried deleting all 4 distribution points from these packages, but the Branch DP's will just not get rid of them. I delete them from the list of DP's, and the package status reflects that (the status says I removed the DP from the list, and even tells me it was successful) but then the status log keeps on going, trying to copy the package back, as if someone else is going right behind me re-adding the branch DP's to the list (hitting refresh in the DP list a few minutes later reveals that 1 or both of the Branch DP's have mysteriously returned to the list). I'm fairly certain these two issues are directly related.