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.

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.

• http://technet.microsoft.com/en-us/library/ff453924.aspx

Nothing was changing, we still get these errors.

RESOLUTION --

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

• http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/7cf5d5e8-e5e4-48c5-b4ad-b029cacf9815

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!

Using Managed Paths to create root Site Collection(s) – Option 2

In my previous post on Creating Site collections at the root of your Web Application, we did this with the knowledge that you would not be hosting a site at the root (http://extranet.company.com), this provided us with the ability to have clean site addresses with out the breakout need of a managed path like, /sites/ or /personal/ or even /dept/.

But what if we did need to have a site at the root and at “/”. What now?

Well this is where being a SharePoint admin keeps you employed.. lol

1. In the previous post we removed the “Explicit inclusion” from our managed path. This is what breaks the ROOT site collection as SharePoint won’t serve up the root site collection with it set as a “Wildcard inclusion”, but it will server up anything underneath it.  This means we have to go back to our managed paths and delete the “Wildcard inclusion” off of the root and change it back to an “Explicit inclusion”.
2. Remove the “Wildcard inclusion” “/”.
   • 
3. Add the “Explicit inclusion” for “/” back.
   • 
4. Now what do we do? This is where the management becomes more of a concern. We need to identify what new managed paths are that need to be defined for each of our our new site collection.
5. Go create a managed path for the new site collection with an “Explicit inclusion”.  Example I named mine mikerules and miketest2.
   • 
6. Now lets create the new Site Collection.
   1. Go to Application Management
   2. Select Create Site Collection under the Site Collection Section
   3. From the Drop down select the correct Web Application
   4. Provide it a name
   5. Under Web Site Address select the Drop Down and you will now be able to select “/”.
   6. Put in the Name of your new site collection.
   7. 
   8. 
   9. Pick your Template
   10. Select Ok
   11. Complete.
       1. Now you can create sites under the root.
7. If we test both the root and new site collection, we will find that they both now work.  

Now lets use PowerShell to create the new “Explicit inclusion” Managed paths that we are looking to add

1. Open PowerShell (SharePoint 2010 Management Shell).
2. The PowerShell command to create a Managed Path: (Always run as Administrator)
   • New-SPManagedPath
   • Our New Managed Path “MikeRules”.
   • New-SPManagedPath MikeRules –WebApplication https://portal.companyname.com/ –Explicit
   • the – Explicit is what’s necessary to create a site on the root and have it render.
3. Look at you managed paths and you will see your new “MikeRules” Explicit inclusion managed path.

This method will now allow you to have Both the Root the Site Collection Managed path rendering at the same time. Remember that you now have to manage how and who can create these site collections and you need to know what name they will be each time.

Hope this helps.

Using Managed Paths to create Site Collection(s) at the root level of your Web Application – Option 1

Do you always want to use /sites/ or /personal/ to create your site collections? Would you ever wanted to create a site collection off the root of your site such as http://extranet.company.com/PartnerName, only to find you can’t?

Well, If you don’t want your new site collection to be under /sites/ and need the ability to put in under (/).

Can it be done, why yes it can, but.. If you want to go down this road, you will NOT be able to have a site collection that resolves at the main root (http://extranet.company.com). This is a good approach depending on your particular requirements.

Here are steps that you can follow to update your managed paths:

1. First you will see that when trying to add a new site collection you are limited to only the managed paths available.
   • 
2. To add a managed path you can select “Define Managed Paths” from the link in the Create Site Collection screen, but you need to know what you are doing.
3. Or, you can go to Application Management, “Manage web applications”, Select the Web Application of your Choice and then select Managed Paths in the ribbon.
   • 
4. Going to the managed paths page, we see something like this.
   • 
5. By default, SharePoint 2010 adds a (root) “Explicit inclusion” to you managed paths for each Web Application created.
6. First step is to delete this “Explicit inclusion” from your Managed Paths.
   • 
7. Next, Create the new “Wildcard inclusion” / .. (select Add Path)
   • 
8. Now your new Path is available.
   • 
9. Now lets create the new Site Collection.
   1. Go to Application Management
   2. Select Create Site Collection under the Site Collection Section
   3. From the Drop down select the correct Web Application
   4. Provide it a name
   5. Under Web Site Address select the Drop Down and you will now be able to select “/”.
   6. Put in the Name of your new site collection.
   7. 
   8. Pick your Template
   9. Select Ok
   10. Complete.
10. Now you can create sites under the root “/” .
11. But remember, this approach leaves you with no main root site collection but allows you to easily manage site collections at the root “/” without having to have a managed path for each new site collection.
12. See Blog post Option 2 if you need both the root and “/”.

Hope this helps.

Session State Activation Steps

Working with one of our developers, he has a webpart that requires session state. After looking for this command with PowerShell, I found others using “Enable-SPSessionStateService -Defaultprovision”. After running this, we still had issues with adding the webparts to an SharePoint.

The following was our error message. “System.Web.SessionStateModule” or custom session state missing a section in the web config.

Step 1:

• Enable-SPSessionStateService –Defaultprovision
• Note: Do this on each server in the farm.

Step 2:

• Go to your Web Application in INETPUB (C:\inetpub\wwwroot\wss\VirtualDirectories\newsite.company.com80) Web.Config
  Find "enableSessionState" change from false to true.

<pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false" pageParserFilterType="Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" asyncTimeout="7">

• Note: Do this for each Web Application that you want this functionality to be available.

Step 3:

• Next is to ensure that the “remove” and “add” lines exist in the modules section for Session is present.

Search For: <modules runAllManagedModulesForAllRequests="true"> Verify the following exists: (Add if missing) Between <modules..   <remove name="Session" /> <add name="Session" type="System.Web.SessionState.SessionStateModule" preCondition="" /> ../modules> End of..

• Note: Do this for each Web Application that you want this functionality to be available.

Why cant this just be as easy as just running a command.

Event ID 7043 - TaxonomyPicker.aspx

Problem: On SharePoint 2010 you may run into the following error (Has been here since Beta).

Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.

It looks like this in your Application Event Log:

Resolution: You will want to rename "TaxonomyPicker.ascx" to "TaxonomyPicker.ascx_broken" so SharePoint does not try to recompile it each time the AppPool is started.

• EDIT File Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES
• Note: This user control is never used within SharePoint and serves no real purpose.

There have been multiple posts on ways this can be fixed but the above seems to be the only way that it does not come back.

• http://todd-carter.com/post/2010/05/03/Help-Wanted-Taxonomy-Picker.aspx
• http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/c894d98c-24ab-416c-aca9-ae57644deb5e.

Thanks for stopping by.

SharePoint 3rd Party Content Migration Tools

List of 3rd party Migration Tools.

---

XAVOR - http://www.xavor.com

1. SHAREPOINT MIGRATOR (XSPM) - Migrate data from WSS 3.0 to MOSS 2007, WSS 3.0 (Platform A) to WSS 3.0 (Platform B) or MOSS 2007 (Platform A) to MOSS 2007/2010 (Platform B).

---

Quest - http://www.quest.com/

1. Migration Manager for SharePoint - For Migrating SPS 2003 content to SharePoint 2007 Platform
2. File Migrator -For migrating content from file shares to SharePoint 2007 platform
3. Public Folder Migrator - For bulk migrations of Exchange Public Folder content to SharePoint 2003 or 2007 platform
4. Notes Migrator- For migrating Notes, QuickPlace and Domino.Doc application content to SharePoint
5. Office 365 Migration Suit- For migrating SharePoint Content from on-premise environments to the cloud

---

Tzunami - http://www.tzunami.com/

1. TD File Shares Migration -Migrate folder structures and files from any file share (local or network drive) to SharePoint 2007 Platform

2. TD SPS 2003 Migration - For migrating content from SPS 2003 to SharePoint 2007 Platform

3. TD SPS 2001 Migration - For migrating SharePoint 2001 to SharePoint 2007 Platform

4. TD Exchange Migration - For migrating Exchange Public Folders to SharePoing 2007 List and Libraries

5. TD LiveLink Migration - For migrating Livelink content into SharePoint 2007 Platform

6. TD DocuShare Migration - For migrating Xerox DocuShare content into SharePoint 2007 Platform

7. TD Documentum Migration - For migrating EMC Documentum Content into SharePoint 2007 Platform

8. TD eRoom Migration -For migrating migrating EMC eRoom content into SharePoint 2007 products

9. TD Hummingbird Migration - For migrating Hummingbird Document Management content into SharePoint 2007 Platform

10. TD Hyperwave Migration - For migrating Hyperwave content into SharePoint 2007 Platform

11. TD Aqualogic Migration - For migrating migrating AquaLogic Interaction content into SharePoint 2007 Platform

12. TD Lotus Notes Migration - For migrating Lotus Notes databaser and applications into SharePoint 2007 Platform

---

Metavis - http://www.metavistech.com/

1. ECM Migrator

• SharePoint to SharePoint
• eRoom to SharePoint
• Livelink to SharePoint

---

MetaLogix - http://www.metalogix.net/

1. SharePoint Site Migration Manager- For migrating content from SPS 2003 to SharePoint 2007 Platform

2. Web Content Migration Manager for SharePoint - For migrating content from various below listed platforms to SharePoint 2007:

• Microsoft Content Management Server 2002
• Third-party enterprise WCM Systems such as Interwoven, Stellent, Vignette, RedDot, Percussion, and Tridion
• All HTTP-accessible, home-grown, static, and dynamic websites
• Documentum eRoom calendars, databases, file, and files with versions

3. FileShare Migration Manager for SharePoint - For migrating content from below listed platforms to SharePoint 2007,

• Network File Shares
• Personal drives
• All web-based intranet and extranet document repositories
• Enterprise File Sharing and Document Management Systems including: eRoom, Documentum, and Lotus Notes

4. SharePoint Migration Manager for eRoom - For migrating content from Documentum eRoom to SharePoint 2007

---

AvePoint - http://www.avepoint.com/

1. Doc Ave SharePoint Migrator - For migrating content from SPS 2003 to MOSS 2007 platform

2. DocAve Public Folder Migrator - For migrating content from Exchange folders to their mapped SharePoint List and Libraries in SPS 2003 and MOSS 2007 platform

3. DocAve File System Migrator - For transfering the documents from traditional Windows-based file systems or networked file shares to online document libraries in SharePoint 2007

4. DocAve Documentum eRoom Migrator - For transfering the collaborative workspaces and document libraries from EMC Documentum eRoom to SharePoint 2007

5. AvePoint Website Migrator - For migrating the web content into SharePoint 2007 Platform

6. DocAve LiveLink Migrator - For migrating from Open Text LiveLink to Microsoft Office SharePoint Server (MOSS) 2007 and WSS v3.0

---

Kapow Technologies - http://www.kapowtech.com/

1. Content Migration Module - The module acts much as an ETL tool, but performs the entire data extraction and transformation at the web GUI level. Kapow can load content directly into a destination application or into standard XML files for import by standard content importing tools. Therefore, any content can be migrated and synchronized to and between any web based CMS, CRM, Project Management or ERP system. Standard adaptors exist for major Content Management Systems e.g. EMC/Documentum, Interwoven, SDL Tridion, Oracle Stellent, IBM FileNet, FatWire,Vignette, SiteCore,CoreMedia, and Joomla. CRM systems supported include salesforce.com, Siebel and Oracle CRM, NetSuite, etc

---

Vamosa - http://www.vamosa.com/

1. Vamosa Solution for SharePoint 2007 - Migrate content from multiple sites, including all other content management systems and older versions of SharePoint and Microsoft Content Management Server to SharePoint 2007 platform

2. Vamosa Content Migrator - For migrating content from any source system to any target system

---

VitalPath - http://www.vital-path.com/

1. Path Builder- A Vendor-neutral solution communicates at the API level, unifying all aspects of different content management systems provides Repository consolidation services

2. Path Builder for SharePoint - Integrates more than 40 content repositories with SharePoint

---

Proventeq - http://www.proventeq.com/

1. Proventeq - Content Migration Suite - End-to-end solution that can migrate web content, documents and other digital assets from a wide range of sources (structured or otherwise) to a variety of target Enterprise Content Management (ECM) systems

---

Will add more as I come across them, please let me know if you have any that I should add.

SharePoint (Foundation, Project, Server) 2010 SP1 & June CU 2011

Hello all, busy day in SharePoint land today. First the June 2011 CU came out yesterday, then last evening SP1 was released. From all the different Twitter conversation on how best to deploy SP1, between Todd Klindt and Spence Harbar and others, deploying the Foundation SP1/CU prior to the Server SP1/CU was the winner. I have outlined my steps below.

Tonight on my UAT environment I followed the below steps to update my environment so I can start testing out the new functionality.

First install all SP1’s before installing the June 2011 CU’s. From what I gather, all CU’s starting with August 2011 will require SP1, so get it in now.

First download all the bits and save them to a location accessible by your SharePoint server(s). (Links next to each product below, note, I have Office Web Applications 2010 & Project Server 2010 integrated into my farm and that info on the patches is included below, if you are not using OWA or Project Server 2010 just skip that step).

Microsoft Resources: Complete list of all SP1 downloads: http://support.microsoft.com/kb/2532120 Update Center for Microsoft Office, Office Servers, and Related Products (CU’s): http://technet.microsoft.com/en-us/office/ee748587.aspx

Microsoft SharePoint SP1 (Foundation, Server, OWA & Project) (install order)

1. SharePoint Foundation 2010 (KB2460058) http://SP2010FoundationSP1
2. Microsoft SharePoint Server 2010 (KB2460045) http://SP2010ServerSP1
3. Microsoft Office Web Apps 2010 (KB2460073) http://OfficeWebAppSP1
4. Microsoft Project Server 2010 (KB2460047) http://ProjectServer2010SP1

As usual, Run Through PowerShell: Run: PSConfig.exe -cmd upgrade -inplace b2b -wait –force

Patching with SP1 went very smoothly, Farm is up and “Check product and patch installation status” shows “Microsoft SharePoint 2010 Service Pack 1 (SP1) is installed (14.0.6029.1000). Now on to deploying the June 2011 CU’s.

June 2011 CU (install order)

1. SharePoint Foundation 2010, June 2011 CU: http://SP2010FoundationJune2011CU
2. SharePoint Server 2010 June 2011 CU: http://SP2010ServerJune2011CU
3. Project Server 2010 June 2011 CU: http://ProjectServer2010June2011CU

After installing the CU packages, you may be prompted for a reboot of your Server! Please don’t forget to run the PSConfig Wizard anyway, even after reboot so that all updates are applied completely and successful!

As usual, Run Through PowerShell:   PSConfig.exe -cmd upgrade -inplace b2b -wait -force

During the PSConfig, applying the June CU’s showed that Task 3 of 4 completed 100% but Failed to start the “ProfileSyncronizationServiceInstance”.. Message stated to “Start it manually”.. Big gulp here, as Profile service has been so friendly in the past..

So after going to Services on server and selecting start (fill out password again) and selecting ok, I quickly jump to Server Manager and watched the Services.. One at a time the Forefront services stopped and…started back up.. WOW, in a very timely manor the Profile services were back online!

 

Now that my Farm is up, let’s go to CA and “Check product and patch installation status” shows “Hotfix for Microsoft Office Server (KB2536599) is installed (14.0.6105.5000).

In less than 2 hours I am all patched up and ready to go.

Good luck and thanks to all that provide exceptional guidance in the SharePoint community.

Happy patching!