I believe there is a problem withour FSP. It is not reporting anything in Reports regarding success or failure for the client installs. And In the folder SMS\MP\OUTBOXES\statemsg.box on the FSP there are a growing number of files building up. Ive been looking through the log files and in mpfdm.log on the fsp Im getting this over and over. **ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/6/2008 3:38:56 PM2764 (0x0ACC) Any ideas?

Hi, Looks like that the MP is unable to connect to the site system. Check for errors regarding your MP. If you extended the AD schema check to see if the site server computeraccount has full control on the system management container in AD. MP requirement is that IIS is installed with BITS and Webdav is allowed.

Thanks for the reply but there doesnt appear to be any problem with the MP. The AD schema has been extended and the site server has full control on the system management container in AD. Thiswas an upgrade from a SMS 2003 site.

The AD schema extension has nothing to do with this FSP problem. Check fspmgr.log for errors. I guess that the upgrade to ConfigMgr did not complete successfully. Check sitecomp.log if all components were upgraded (reinstalled) without any errors. Also have a look at the site system status.

I uninstalled then re-installed the FSP to see if that would help it did not. sitecomp.log doesnt show any errors and reports that the FSP installed successfully. The system status doesnt appear to be reporting anything related to the FSP. It looks like clients are reporting to the FSP as I see *.smx files in the SMS\MP\OUTBOXES\statemsg.box The fspmgr.log doesnt have any errors this is all thats in the log: SMS_EXECUTIVE started SMS_FALLBACK_STATUS_POINT as thread ID 3756 (0xEAC).SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:05 PM3820 (0x0EEC)CFSPManager::Initialize() : CreateThread succeeded.SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:05 PM3756 (0x0EAC)SMS_FALLBACK_STATUS_POINT successfully STARTED.SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:05 PM3756 (0x0EAC)CFSPManager::TransferFiles - No files need to be copied from the staging location.SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:05 PM2248 (0x08C8)********************************************************************************SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:05 PM3756 (0x0EAC)Updated throttling values based on registry changes.SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:13 PM2248 (0x08C8)CFSPManager::TransferFiles - No files need to be copied from the staging location.SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:13 PM2248 (0x08C8)Updated throttling values based on registry changes.SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:13 PM2248 (0x08C8)CFSPManager::TransferFiles - No files need to be copied from the staging location.SMS_FALLBACK_STATUS_POINT8/8/2008 1:18:13 PM2248 (0x08C8)Successfully copied 23 out of 23 file(s).SMS_FALLBACK_STATUS_POINT8/8/2008 2:18:13 PM2248 (0x08C8) mpfdm.log is where Im seeing the errors. It looks like the FSP and the site system are not talking. SMS_EXECUTIVE started SMS_MP_FILE_DISPATCH_MANAGER as thread ID 3664 (0xE50).SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3820 (0x0EEC)MP File Dispatch Manager initializing...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)Site Code = FRXSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)Site Server =SCCMSERVERSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)Local SMS install directory = E:\SMSSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)MP Host Server =SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)On Site Server = FalseSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)Polling interval = 300 secs.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)*******************************************************SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)Initiating Remote Site FDM processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)The site server has not responded yet, default to push-mode.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)FDM performance polling thread starting.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2488 (0x09B8)Remote site is in push-mode.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)Assistant thread count = 1.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3664 (0x0E50)Worker thread [Discovery Data Manager (Trusted)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1856 (0x0740)Worker thread [Discovery Data Manager (Registration)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM4008 (0x0FA8)Worker thread [Software Inventory Processor (Site Trusted)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1776 (0x06F0)Worker thread [Data Loader (Trusted)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2940 (0x0B7C)Worker thread [Site Server Inventory Collection] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3680 (0x0E60)Worker thread [Status Manager] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3624 (0x0E28)Worker thread [Software Metering Processor Usage (Site)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3060 (0x0BF4)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1776 (0x06F0)Worker thread [Client Configuration Record (Incoming)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3616 (0x0E20)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2940 (0x0B7C)Assistant push thread for [Status Manager] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2148 (0x0864)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3680 (0x0E60)Worker thread [Distribution Manager (Incoming)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1284 (0x0504)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3060 (0x0BF4)Created source directory E:\SMS\MP\OUTBOXES\hinv.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2940 (0x0B7C)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1284 (0x0504)Worker thread [State System (Incoming)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2988 (0x0BAC)Created source directory E:\SMS\MP\OUTBOXES\swm.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3060 (0x0BF4)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2988 (0x0BAC)Created source directory E:\SMS\MP\OUTBOXES\distmgr.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1284 (0x0504)Created source directory E:\SMS\MP\OUTBOXES\statemsg.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2988 (0x0BAC)Assistant push thread for [State System (Incoming)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2620 (0x0A3C)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3680 (0x0E60)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3060 (0x0BF4)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2940 (0x0B7C)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM2988 (0x0BAC)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1284 (0x0504)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM4008 (0x0FA8)Created source directory E:\SMS\MP\OUTBOXES\rdr.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM4008 (0x0FA8)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM4008 (0x0FA8)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3624 (0x0E28)Created source directory E:\SMS\MP\OUTBOXES\sinv.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1776 (0x06F0)Created source directory E:\SMS\MP\OUTBOXES\stat.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3624 (0x0E28)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1776 (0x06F0)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3624 (0x0E28)Worker thread [Distribution Manager (Incoming)] starting execution.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3572 (0x0DF4)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3572 (0x0DF4)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3572 (0x0DF4)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3616 (0x0E20)Created source directory E:\SMS\MP\OUTBOXES\ccr.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3616 (0x0E20)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM3616 (0x0E20)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1856 (0x0740)Created source directory E:\SMS\MP\OUTBOXES\ddr.boxSMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:18:13 PM1856 (0x0740)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:20:43 PM3572 (0x0DF4)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:20:43 PM3616 (0x0E20)**ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:20:43 PM1856 (0x0740)Worker thread [Site Server Inventory Collection] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM3680 (0x0E60)Worker thread [Discovery Data Manager (Registration)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM4008 (0x0FA8)Worker thread [Distribution Manager (Incoming)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM1284 (0x0504)Worker thread [Software Metering Processor Usage (Site)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM3060 (0x0BF4)Worker thread [Status Manager] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM3624 (0x0E28)Worker thread [Distribution Manager (Incoming)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM3572 (0x0DF4)Worker thread [Software Inventory Processor (Site Trusted)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM1776 (0x06F0)Worker thread [Data Loader (Trusted)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM2940 (0x0B7C)Worker thread [Client Configuration Record (Incoming)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM3616 (0x0E20)Worker thread [State System (Incoming)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM2988 (0x0BAC)Worker thread [Discovery Data Manager (Trusted)] cannot update environment so skiping outbox processing.SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:21:13 PM1856 (0x0740)Updating environment...SMS_MP_FILE_DISPATCH_MANAGER8/8/2008 1:22:13 PM3680 (0x0E60) Does the FSP send data to the Site Server or does the Site Server pull information from the FSP? I do have the server accounts in the Local Administrator groups on both servers. Appreciate any help.

TheFSP receives state messages from SCCM client computers and thensent these back to the site.

Problem solved. The problem was caused by the FSP not being able to read SMS registry keys on the site server that was being blocked by some policies.

willbar, A little late in the day, but hopefully someone will come across this... what policies are you speaking of here? I'm having the same issue and am having trouble finding the solution. Thanks

...even later in the day... same issue here and no concrete info on how to resolve. The SMX files building up in the FSPFolder are running into the millions, and taking up Gigs of space. I've upgraded to SP2, and have disabled software and hardware inventory as the BADMIFS folder was also filling up - I'm having errors with the SMS_INVENTORY_DATA_LOADER (2703) SMS_MP_CONTROL_MANAGER (5447) SMS_SOFTWARE_INVENTORY_PROCESSOR (3701) components. Any insight anyone? FSP is enabled and I dont really see any problems with the FSP component itself. Cheers