Issue: FIM synchronization services in our one of the SharePoint environment stops or doesn’t start every time our servers are patched and rebooted.
Error: We have many loges reported in event viewer of the servers. Event ID 3, Event ID 6324, Event ID 3760
Log Name: Application
Source: Forefront Identity Manager
Date: 29/06/2014 03:16:04
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server Name.
Description:
The TryGetSetting function in SettingsProvider.dll returned an empty set of supported parameters for property, SQLConnectionString.
Event Xml:
The TryGetSetting function in SettingsProvider.dll returned an empty set of supported parameters for property, SQLConnectionString.
Log Name: Application
Source: FIMSynchronizationService
Date: 29/06/2014 03:18:05
Event ID: 6324
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: Server Name.
Description:
The server encountered an unexpected error and stopped.
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 29/06/2014 03:18:38
Event ID: 3760
Task Category: Database
Level: Critical
Keywords:
User: Farm account.
Computer: Server Name.
Description:
SQL Database ‘DB Name; on SQL Server instance ‘SQL Server Instances Name,14331' not found. Additional error information from SQL Server is included below.
Cannot open database "DB Name" requested by the login. The login failed.
Login failed for user ‘Farm account name’.
Troubleshooting:
There are different approaches towards troubleshooting this issue as reason for its occurrence is unknown.
Resolution:
Different people had suggested different things:
First:
Such as adding service account into three groups on local machine:
FIMSyncOperator, FIMSyncJoiners and FIMSyncBrowse and errors should go.
FIMSyncOperator, FIMSyncJoiners and FIMSyncBrowse and errors should go.
Second:
FIM Sync service should start before FIM service. However it may not be happening. Currently the service is set to Automatic and can be changing it Automatic (Delayed Start).
We could deploy a script which will check for the service every 60 seconds, and if it is not running, sends an email to the administrator
- while ((Get-Service "FIM").status -eq "Running")
- {Start-Sleep -Seconds 60}
- Send-MailMessage -From FIM@ps.local -To admin@ps.local -Body "FIM Stopped" -SmtpServer server1
- Alternatively, you can put a .cmd file in your Recovery Tab of the service, and use the following command: Powershell Send-MailMessage
Third:
In our case we had also found there were several SQL related error and in further investigation we found that server hosting FIM service were rebooted before the SQL server and once the SQL servers were re-booted FIM services always failed to find it reference to connect to SQL.
Rebooting SQL servers after server hosting FIM services had let FIM sync Services in Start state and resolved our issue.
Applies to: SharePoint server 2010, Windows Server 2008, Fore front Identity manager.
No comments:
Post a Comment