Wednesday, July 31, 2013

SharePoint 2010 Event ID 6801 FIMSynchronizationService

Our User Profile Synchronization service has been running without issues for quite a while, but in the last few days we started to seeing event id 6801 errors in the application event log:

Event ID 6801 FIMSynchronizationService

Looking at the configuration of the service itself, there didn't appear to be any problems. The sync would run, but it would generate errors for every user it processed. It turns out the problem is with the proxy for the user profile service application. The proxy basically associates the User Profile Service Application to the Web application through membership in the a service application connection group. In most environments, this is the default group.

User Profile Service Application Proxy

The solution is to simply re-create the proxy using the following steps:

1. Delete the existing User Profile Service Application proxy using the following script. The name may be different in your farm, but you can verify by running Get-SPServiceApplication.

Note: If you've messed around with the service application associations and don't remember if you're still using the default group, go to Central Admin - Application Management - Service Applications and click on Configure service application associations. In the default config, it should look like this:

Service Application Associations

$proxy = Get-SPServiceApplicationProxy | where {$_.typename -eq "User Profile Service Application Proxy"}

Remove-SPServiceApplicationProxy -Identity $proxy -confirm:$false
2. Create a new User Profile Service Application Proxy using the following script and associate it with the default group:
$upa = Get-SPServiceApplication -Name "User Profile Service Application"
New-SPProfileServiceApplicationProxy -Name "User Profile Service Application Proxy" -ServiceApplication $upa -DefaultProxyGroup
3. Do an iisreset from the command prompt, then run a profile sync and check the errors are no longer being generated.

For other User Profile Synchronization issues we've looked at see:

Thursday, July 25, 2013

SharePoint 2010 Service Pack 2 Now Available!

Microsoft just released the latest service pack for the SharePoint 2010 family of products. You can download the bits from the Update center for Office, Office servers, and related products. You might want to start now since it's over 400MB!

As usual we recommend waiting a couple of weeks before applying it to a production environment since there have been issues in the past caused by CU's or updates. If you use the Profile Synchronization features of SharePoint, you'll know what we mean.

The service pack includes all updates to May 2013 as well as all CU's up to April 2013. According the the SharePoint Team Blog the service pack "addresses security, stability, and performance and provides better compatibility with Windows 8, Internet Explorer 10, Office 2013, and SharePoint 2013. In addition to the new functionality Service Pack 2 provides, as with all Service Packs, it includes a number of fixes designed to improve your experience". You can also subscribe to the following blog if you want to be made aware of updates concerning SP2 going forward.

So far there are very few known issues, but you still can't install SharePoint 2010 on Windows Server 2012 which we were hoping would be supported. We suspect this will be addressed by Microsoft shortly.

As always, be sure to follow upgrade directions to maintain availability and reduce the number of headaches you have:

Below is are some of the other issues addressed.

If requireExactUrl is not set for openweb calls, the PublishingWeb constructor may spawn variation pages  into incorrect locations while attempting re-creation of failed label during create hierarchies.
Incremental content deployment fails, giving the following error: FatalError: The given key was not present in the dictionary
Spell Checker doesn't work properly with Internet Explorer 10.
Rich text editor spell checker may work incorrectly on 64 bit machines.
Customers encounter issues sending e-mail from workflows when the From address uses a non-Unicode character set.
Updated VBE7.dll to fix safe array corruption for x64 hosts when calling UDF methods using safe array arguments directly from the host. 
SQL exceptions will appear in the log when running update statistics timer.
Improved performance of the AllUserData table.
Getting a feed against a discussion board fails if feed contains more than zero items.
SharePoint 2010 client object model now has compatibility for accessing Sharepoint 2013 servers.
Windows 8 users with Internet Explorer 10 receive an error when trying to open a document from SharePoint 2010 directly in the Office client.
Call GetChanges won’t return changes in certain cases where the change log has been edited and no parameters are set.
STSAdm MigrateUser fails when SQL server is not in domain.
Attempting to delete a child web from site settings causes the page to fail. 
There is no exposed method to recalculate the second stage recycle bin size.
April 2011 Calendar View does not display correctly with Amman System Time zone
Users can create a scenario where a site loses permissions.
After deleting a web that contains historical document versions in the RecycleBin, rows are abandoned in the database.  These rows bloat the size of the database, causing difficulty with database management operations such as backup/restore, complicating upgrade and other scenarios.
After creating alerts on a document library with unique permissions and moving the contents using SPFolder.MoveTo method, the permissions seem to be lost and even the farm administrator is not able to delete these alerts.