Error Cannot Connect To The Inbox Source
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: mpfdm.log **ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again. System Center 2012 Configuration Manager > Configuration Manager 2012 - Site and Client Deployment Question 0 Sign in to vote Hi I have a management point on a server in an untrusted forest that doesn't send the outbox files to the primary. On the log mpfdm.log it is bombed with **ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again. What could be the problem? Wednesday, March 19, 2014 2:19 PM Reply | Quote Answers 2 Sign in to vote I finally solved it by myself. Because the site server is in an untrusted forest, the option under site server properties, "Require the site server to initiate connections to this system" must be selected. Edited by Baatch Wednesday, March 19, 2014 3:10 PM Marked as answer by Baatch Wednesday, March 19, 2014 3:10 PM Wednesday, March 19, 2014 3:09 PM Reply | Quote All replies 0 Sign in to vote Has it ever worked?John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/ Wednesday, March 19, 2014 2:58 PM Reply | Quote Moderator 2 Sign in to vote I finally solved it by myself. Because the site server is in an untrusted forest, the option under site server properties, "Require the site server to initiate connections to this system" must be selected. Edited by Baatch Wednesday, March 19, 2014 3:10 PM Marked as answer by Baatch Wednesday, March 19, 2014 3:10 PM Wednesday, March 19, 2014 3:09 PM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web
→ Configuration Manager 2012 Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. We use cookies to let you log in, for ads and for analytics. OK User State capture not showing in console Started by jdd12 , May 29 2015 04:23 PM User State Migration Please log in to reply 1 reply to this topic #1 jdd12 jdd12 Newbie Established Members 7 posts Gender:Male Posted 29 May 2015 - 04:23 PM Hi Everyone, Yesterday afternoon I installed the State Migration Point role to a Distribution Point that has existed for about 1.5 years. A https://social.technet.microsoft.com/Forums/en-US/0bd1d706-722b-41b1-80f7-c9194764f48d/mpfdmlog-error-cannot-connect-to-the-inbox-source-sleep-30-seconds-and-try-again?forum=configmanagerdeployment little while after it finished installing, I ran a task sequence to capture the User State on one of my clients. The task sequence ran fine. However, it never shows up in Assets and Compliance > User State Migration in the console. I can see the .MIG file on the SMP and I can see a successful status in the Deployment monitoring. There are no errors for the SMP component https://www.windows-noob.com/forums/topic/12462-user-state-capture-not-showing-in-console/ on that Site System. SMSTS.log, SCANSTATEPROGRESS.log, and SCANSTATE.log on the client don't show any errors either. User is connected by both WiFi and Ethernet, if that matters. I ran the same Task Sequence on a test VM in my office (different SMP) and it worked fine and showed up in the console as an "in-place" migration. Can anyone give me an idea of where to begin looking for the cause of this? Or is it something simple that I have missed? Thanks! Back to top #2 jdd12 jdd12 Newbie Established Members 7 posts Gender:Male Posted 04 June 2015 - 02:13 PM An update for anyone that stumbles across this in the future... I ended up opening a case with Microsoft and they found that it is an existing bug that does not have an ETA on a fix. The state message files were queueing up in theSMS\MP\OUTBOXES\statemsg.box and not sending to the MP. The mpfgdm.log on the SMP had the following errors: **ERROR: Cannot connect to the inbox source, sleep 30 seconds and try again. He had me add the DP computer account to the local admin group on the MP (my Primary Site server) and restart the SMS Executive service. After that every
I had to add the MP's computer account to the local administrator group on the site server. This dispite there being a specific local group for http://www.networksteve.com/enterprise/topic.php/MP_failed_after_upgrade_to_1511/1602/?TopicId=134141&Posts=3 remote MPs. Is this normal? As soon as I added the MP's account to the Local Admins group on the site server, and restarted the SMS Executive service on the MP, the errors in the log cleared up. I could not find any documentation that suggests that the MP's computer account requires local admin on the site server. I suspect it is due to the MP not being error cannot able to read the registry on the Site Server. Is this a bug? Why don't they grant the specific rights the MP account needs to the local groups that SCCM creates rather than requiring local admin rights? Mostly I want to know if others have run into this problem. I am slightly uneasy about just blindly giving the MP's computer account Local Admin rights on the site server. Looking error cannot connect in the mpfdm.log file on the Management Point I saw lots of these sorts of problems... ~Worker thread [State System (Incoming - low priority)] cannot update environment so skiping outbox processing. $$