Forefront Identity Manager Synchronization Service fails to start

There are numerous articles covering that issue.

In my case the “Forefront Identity Manager Synchronization Service” (FIMSynchronizationService) failed to start whereas the “Forefront Identity Manager Service” (FIMService) was started.
Both services where configured to automatically start.

This happened right after the installation of Windows (and SharePoint) updates and runnin the PSCONFIG command “PSCONFIG.EXE -cmd upgrade -inplace b2b -wait”.

Restarting the service — or even the SharePoint Service Application (i.e. the UPA) — did not help.

In the Windows EventLog I found the following entry:

Detection of product ‘{90150000–104C-0000–1000–0000000FF1CE}’, feature ‘PeopleILM’, component ‘{CF90B971-D78A-4794–8F90-EB5FB5028DDA}’ failed. The resource ‘C:\Program Files\Microsoft Office Servers\15.0\SQL\DatabaseSettings.sql’ does not exist.

This was not the first time and therefore I knew what to do:

Grant READ permissions to the computer-local NETWORK SERVICE account to the ‘C:\Program Files\Microsoft Office Servers\15.0’ folder.

Preferably using the membership of the local group WSS_WPG.

Please also refer to:

SharePoint 2013: Detection of product ‘{90150000–104C-0000–1000–0000000FF1CE}’, feature ‘PeopleILM’, component ‘{1C12B6E6–898C-4D58–9774-AAAFBDFE273C}’ failed