Roland Serman’s Blog

Just another WordPress.com weblog

Profile Sync Timeouts

I recently had to open a ticket with Microsoft because of problems getting the Profile Sync service to successfully sync with Active Directory.  In doing so, it was recommended that I modify a few of the timeouts associated with the service.  For the most part, none of these should need to be tweaked unless you have a large AD environment, and need to process large LDAP datasets.

We ended up modifying 3 different parameters:

  • ImportConnAsyncTimeout
  • FIMWebClientTimeOut
  • LdapConnectionTimeout

Don’t quote me on this, but this is my understanding of what each of the three values control:

ImportConnAsynctimeout: This timeout is when you click the Populate button on the editdsserver.aspx page, and SharePoint enumerates the domains/OU’s and then presents them on the page.  the default time out value is 30 seconds.

FIMWebClientTimeOut: After selecting what you plan to sync, and clicking the OK button on the editdsserver.aspx page, SharePoint then goes into the FIM service and create/edits the management agent.  The default timeout for this is ~16.6 minutes, due to large OU structures and the amount of data that is collected.

LdapConnectionTimeout: This is the timeout for the actual Directory Connection, the default for this is 30 seconds.

Below I’ve provided the powershell commands utilized to actually modify the parameters:

ImportConnAsyncTimeout:

$upaAppProxy = Get-SPServiceApplicationProxy | ? {$_.name -like ‘User Profile Service Proxy’}

$upaAppProxy.ImportConnAsyncTimeout = 60 //This value is in seconds

$upaAppProxy.Update()

FIMWebClientTimeOut:

$upaApp = Get-SPServiceApplication | ? {$_.name -like ‘User Profile Service’}

$upaApp. FIMWebClientTimeOut = 300000 //This value is in milliseconds

$upaApp.Update()

LdapConnectionTimeout:

$upaAppProxy = Get-SPServiceApplicationProxy | ? {$_.name -like ‘User Profile Service Proxy’}

$upaAppProxy.LdapConnectionTimeout = 60 //This value is in seconds

$upaAppProxy.Update()

Advertisements

One response to “Profile Sync Timeouts

  1. Samuel May 24, 2011 at 11:49 am

    FIMWebClientTimeOut and LdapConnectionTimeout Properties are not longer visible for the get-serviceapplicationproxy command. How to configure this elsewhere?

    Thanks Samuel

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: