Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

SharePoint 2010: User Profile Synchronization fails with event ID 6801


View products that this article applies to.

Symptoms

You are running profile synchronization (using Forefront Identity Manger) in SharePoint Server 2010. Profile synchronization fails and the following error is logged in the event log of the synchronization server (Event ID 6801):

Log Name:      Application
Source:           FIMSynchronizationService
Event ID:        6801
Task Category: Server
Level:              Error
Keywords:    Classic
Description:
The extensible extension returned an unsupported error.
The stack trace is:

"System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: No User Profile Application available to service the request. Contact your farm administrator.
at Microsoft.Office.Server.UserProfiles.ProfileManagerInstance.GetApplicationProxy()
at Microsoft.Office.Server.UserProfiles.ProfileImportExportService.GetPartitionIds()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.Office.Server.WebServiceDirectProxy.WebMethodInfo.Invoke(Object webServiceInstance, Object[] args)
at Microsoft.Office.Server.WebServiceDirectProxy.Invoke(String methodName, Object[] args)
at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportDirect.GetPartitionIds()
at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportExtension.Microsoft.MetadirectoryServices.IMAExtensibleFileImport.
GenerateImportFile(String fileName, String connectTo, String user, String password, ConfigParameterCollection configParameters, Boolean fFullImport, TypeDescriptionCollection types, String& customData)
Forefront Identity Manager 4.0.2450.11"

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="FIMSynchronizationService" />
<EventID Qualifiers="49152">6801</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="[Date and Time]T20:30:12.000000000Z" />
<EventRecordID>42502</EventRecordID>
<Channel>Application</Channel>
<Computer>ComputerName</Computer>
<Security />
</System>
<EventData>
<Data>System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---&gt; Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: No User Profile Application available to service the request. Contact your farm administrator.
at Microsoft.Office.Server.UserProfiles.ProfileManagerInstance.GetApplicationProxy()
at Microsoft.Office.Server.UserProfiles.ProfileImportExportService.GetPartitionIds()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.Office.Server.WebServiceDirectProxy.WebMethodInfo.Invoke(Object webServiceInstance, Object[] args)
at Microsoft.Office.Server.WebServiceDirectProxy.Invoke(String methodName, Object[] args)
at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportDirect.GetPartitionIds()
at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportExtension.Microsoft.MetadirectoryServices.IMAExtensibleFileImport.
GenerateImportFile(String fileName, String connectTo, String user, String password, ConfigParameterCollection configParameters, Boolean fFullImport, TypeDescriptionCollection types, String& customData)
Forefront Identity Manager 4.0.2450.11</Data>
</EventData>
</Event>

↑ Back to the top


Cause

This problem may occur if the proxy for user profile service application becomes corrupt or gets deleted

↑ Back to the top


Resolution

In order to address this problem, delete and re-create the user profile service application proxy by using the following Powershell commands:

  1. Remove the User Profile Service Application proxy:
    $proxy = Get-SPServiceApplicationProxy | where {$_.typename -eq "User Profile Service Application Proxy"}
    Remove-SPServiceApplicationProxy -Identity $proxy -confirm:$false
  2. Create the User Profile Service Application proxy:
    $upa = Get-SPServiceApplication | where {$_.name -eq "<name here>"}
    New-SPProfileServiceApplicationProxy -Name <proxyName> -Uri $upa.uri.absoluteURI
Associate the new User Profile Service Application Proxy with the existing web applications

When you create a service application in Microsoft SharePoint Server 2010, a service application connection is created. A service application connection is also referred to as an application proxy. A service application connection associates the service application to Web applications via membership in a service application connection group (also referred to as application proxy group).

You can add or remove service application connections to a service application connection group by using Central Administration or by using Windows PowerShell 2.0 cmdlets.
  1. To edit a service connection group by using Central Administration
    • Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
    • On the Central Administration Home page, click Application Management.
    • On the Application Management page, in the Service Applications section, click Configure service application associations.
    • On the Service Application Associations page, select Web Applications from the View drop-down menu.
    • In the list of Web applications, in the Application Proxy Group column, click the name of the service application connection group that you want to change.
    • To add a service connection to the group, select the check box that is next to the service application that you want to add to the connection group. To remove a service application connection from the connection group, clear the check box next to the service application that you want to remove from the connection group. When you have made the changes that you want, click OK.

    Note
    : You can also change custom service application connection groups by clicking Manage Web Applications from the Central Administration Home page, selecting a listed Web application, and then clicking Service Connections on the ribbon. You cannot change the default service applications connection group through this page, however.
  2. To add a service application connection to a service application connection group by using Windows PowerShell
Open the SharePoint Management Shell using Farm administrator credentials and run the following PowerShell command:
Add-SPServiceApplicationProxyGroupMember [-Identity <the service application proxy group>] [-Member <members to add to the service application proxy group>]
For more information on how to add or remove service application connections to a service application connection group, see Add or remove a service application connection to a Web application (SharePoint Server 2010)

↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 2520394
Revision : 3
Created on : 4/18/2018
Published on : 4/19/2018
Exists online : False
Views : 501