ISSUE
\nWhen Attempting to start the User Profile Synchronization service in Central Administration, the service goes into a starting state for a couple of minutes and then stops, usual this happens because of permissions (DB account not local admin etc..), however it would appear that if you slipstream and install SharePoint with SP1 and June 2011 included and then try and start the service it can still fail.<\/p>\n
CAUSE
\nYou find this will happen if your Domain contains Windows Server 2003 Domain Controllers.<\/p>\n
The reason for this is due to a Kerberos ticket not be able to generate for the OWSTIMER Account (this is normally the DB Account) as it doesn\u2019t contain an SPN please see Yvan’s Blog article for more information: http:\/\/blogs.msdn.com\/b\/yvan_duhamel\/archive\/2010\/06\/29\/you-get-a-system-security-securityexception-when-you-try-to-start-the-fim-synchronization.aspx <\/p>\n
RESOLUTION<\/p>\n
Run
\nsetspn \u2013a NONE\/NONE OWSTimerAccount<\/p>\n
OWSTimerAccount = this is normally the FarmDBAccount.<\/p>\n
ERRORS:<\/p>\n
Using ULViewer downloadable from http:\/\/archive.msdn.microsoft.com\/ULSViewer <\/p>\n
You will see the following errors<\/p>\n
User Profile Application: Unable to load satellite assembly for lcid 1033. Using neutral language assembly version. Exception details: System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.Office.Server.Intl.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified. File name: ‘Microsoft.Office.Server.Intl.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=71e9bce111e9429c’ —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.Office.Server.Intl.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified. File name: ‘Microsoft.Office.Server.Intl.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=71e9bce111e9429c’ WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLMSoftwareMicrosoftFusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLMSoftwareMicrosoftFusion!EnableLog].
\nat System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
\nat System.Reflection.Assembly.InternalGetSatelliteAssembly(CultureInfo culture, Version version, Boolean throwOnFileNotFound)
\nat Microsoft.Office.Server.Administration.UserProfileApplication.GetIntlDllFileVersionString(Int32 lcid)<\/p>\n
UserProfileApplication.SynchronizeMIIS: Failed to configure ILM, will attempt during next rerun. Exception: System.Security.SecurityException: There are currently no logon servers available to service the logon request.
\nat System.Security.Principal.WindowsIdentity.KerbS4ULogon(String upn)
\nat System.Security.Principal.WindowsIdentity..ctor(String sUserPrincipalName, String type)
\nat System.Security.Principal.WindowsIdentity..ctor(String sUserPrincipalName)
\nat Microsoft.IdentityManagement.SetupUtils.IlmWSSetup.GetDomainAccountSIDHexString(String domainName, String accountName)
\nat Microsoft.IdentityManagement.SetupUtils.IlmWSSetup.GrantSQLRightsToServiceAccount()
\nat Microsoft.IdentityManagement.SetupUtils.IlmWSSetup.IlmBuildDatabase()
\nat Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureIlmWebService(Boolean existingDatabase)
\nat Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance) The Zone of the assembly that failed was: MyComputer.<\/p>\n
In the Security event log you will see the following at the point of provisioning the Service.<\/p>\n
An account failed to log on.
\nSubject:
\nSecurity ID: DomainFarmDBAccount
\nAccount Name: FarmDBAccount
\nAccount Domain: Domain
\nLogon ID: 0x313b2
\nLogon Type: 3
\nAccount For Which Logon Failed:
\nSecurity ID: NULL SID
\nAccount Name:
\nAccount Domain:
\nFailure Information:
\nFailure Reason: An Error occured during Logon.
\nStatus: 0xc000005e
\nSub Status: 0x0
\nProcess Information:
\nCaller Process ID: 0xa98
\nCaller Process Name: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14BINOWSTIMER.EXE
\nNetwork Information:
\nWorkstation Name: SERVER
\nSource Network Address: –
\nSource Port: –
\nDetailed Authentication Information:
\nLogon Process: C
\nAuthentication Package: Kerberos
\nTransited Services: –
\nPackage Name (NTLM only): –
\nKey Length: 0
\nThis event is generated when a logon request fails. It is generated on the computer where access was attempted.
\nThe Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
\nThe Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
\nThe Process Information fields indicate which account and process on the system requested the logon.
\nThe Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
\nThe authentication information fields provide detailed information about this specific logon request.
\n– Transited services indicate which intermediate services have participated in this logon request.
\n– Package name indicates which sub-protocol was used among the NTLM protocols.
\n– Key length indicates the length of the generated session key. This will be 0 if no session key was requested.<\/p>\n","protected":false},"excerpt":{"rendered":"
ISSUE When Attempting to start the User Profile Synchronization service in Central Administration, the service goes into a starting state for a couple of minutes and then stops, usual this happens because of permissions (DB<\/p>\n","protected":false},"author":11,"featured_media":828,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_newsletter_tier_id":0,"footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[21],"tags":[1861],"class_list":["post-1114","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft","tag-sharepoint-2010"],"jetpack_publicize_connections":[],"yoast_head":"\r\n