SMS_Distribution_Manager Component spammed with 2300 & 2301 messages

I had a strange problem with my secondary site the other day that I thought I'd share the fix for.

For some reason the SMS_Distribution_Manager component status message log was showing message ID's 2300 & 2301 every minute for a task sequence located on my Central site.

04/08/2010 21:06:16 SystemName SMS_Distribution_Manager 2301 SMS Distribution Manager successfully processed package "Corporate Image 32-Bit - Generic" (package ID = SC1001BA).
04/08/2010 21:06:16 SystemName SMS_Distribution_Manager 2300 SMS Distribution Manager is beginning to process package "Corporate Image 32-Bit - Generic" (package ID = SC1001BA).
04/08/2010 21:05:11 SystemName SMS_Distribution_Manager 2301 SMS Distribution Manager successfully processed package "Corporate Image 32-Bit - Generic" (package ID = SC1001BA).
04/08/2010 21:05:11 SystemName SMS_Distribution_Manager 2300 SMS Distribution Manager is beginning to process package "Corporate Image 32-Bit - Generic" (package ID = SC1001BA).
04/08/2010 21:04:06 SystemName SMS_Distribution_Manager 2301 SMS Distribution Manager successfully processed package "Corporate Image 32-Bit - Generic" (package ID = SC1001BA).
04/08/2010 21:04:06 SystemName SMS_Distribution_Manager 2300 SMS Distribution Manager is beginning to process package "Corporate Image 32-Bit - Generic" (package ID = SC1001BA).

Checking the Distmgr.log you can see the tasksequence re-trying every minute, but what's more interesting is that it explains it can't because a referenced package wasn't available.

Failed to insert SMS Program ID 49479 because the referenced program SC1001ED-* is not present in the PkgPrograms table. Will try later.

This turned out to be a driver package that wasn't distriuted to the secondary site.
OK, not a problem I thought, lets add it.

Hmm... that's not right.
Failed to insert SMS Package SC1001ED because SDM Type Content C727B3AC-0B5B-49D7-AA28-C8C6F3907E3A is not present in the CI_Contents table. Will try later.

Looking around, Jannes Alink had a similar problem last month:
http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/1bd6908c-3395-4a39-a174-747b741927d4

I ran preinst.exe /syncchild and since it had so much to replicate through I left it to it.

Checking this morning however and the last (and final) retry of distributing the task sequence was at 23:54 the previous night, only 6 hours after doing a syncchild!

Problem solved.