Tuesday, January 10, 2012

Event ID 6872, error with incoming e-mail drop folder

As you work to clean up your farm, one step is to review your Health errors and Windows Event logs.

ISSUE --

As you are going through your logs you start seeing errors stating that the incoming e-mail drop folder is not configured. Your environment is setup as.

  • Environment: SharePoint 2010 SP1 June 2011 CU.
  • You have implemented incoming email following this technet article.
  • You have e-mails making it to your libraries.

You know you have followed the appropriate steps, permissions and it makes it to the correct location. No additional errors are being seen in the ULS logs, or at least none that I could find.

Why are this error still showing up?

We are receiving the following error when processing incoming email.

clip_image001

Full error message:

User: domain\sp_farmadmin
Computer: SPAPP1.domain.com
Description:
The incoming e-mail drop folder is not configured. If automatic settings are being used, confirm that the SMTP service is running.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
<EventID>6872</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>4</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2012-01-10T12:11:38.492769800Z" />
<EventRecordID>35421</EventRecordID>
<Correlation ActivityID="{3FD14B9B-4065-40CE-A347-7184796AC7EF}" />
<Execution ProcessID="64276" ThreadID="65616" />
<Channel>Application</Channel>
<Computer>SPAPP1.xtra.com</Computer>
<Security UserID="S-1-5-21-2133076291-787694070-318601546-124014" />
</System>
<EventData>
<Data Name="string0">The incoming e-mail drop folder is not configured. If automatic settings are being used, confirm that the SMTP service is running.</Data>
</EventData>
</Event>

I looked at the the following and verified that these all were done. Check.

Nothing was changing, we still get these errors.

RESOLUTION --

After further research on TechNet Forums I found this similar issue.

Taking this new information we deployed the October CU to our Test farm and this Event no longer appears in our Event logs. We are now scheduling this to go into production, cross your fingers.

  • To download the October 2011 CU, go here:

Thanks for the community and hope this helps you!

0 comments: