Problem

You see the following warnings appear in the Application event log of the farm server on which the User Profile Application is running (listed below).  These warnings appear whenever an incremental or full profile synchronization runs. You are able to reproduce these warnings by manually initiating a profile synchronization.
Log Name:      Application
Source:        MsiInstaller
Date:          date/time]
Event ID:      1004
Task Category: None
Level:         Warning
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      [farm server]
Description:
Detection of product '{90150000-104C-0000-1000-0000000FF1CE}', feature 
'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  
The resource 'C:\Program Files\Microsoft Office
Servers\15.0\Service\Microsoft.ResourceManagement.Service.exe' does 
not exist.
Event Xml:
...
and
Log Name:      Application
Source:        MsiInstaller
Date:          [date/time]
Event ID:      1001
Task Category: None
Level:         Warning
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      [farm server]
Description:
Detection of product '{90150000-104C-0000-1000-0000000FF1CE}', feature 
'PeopleILM' failed during request for component 
'{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}'
Event Xml:
...
and
Log Name:      Application
Source:        MsiInstaller
Date:          [date/time]
Event ID:      1015
Task Category: None
Level:         Warning
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      [farm server]
Description:
Failed to connect to server. Error: 0x80070005
Event Xml:
...
Solution of this problem is trivial and involves adding the NETWORK SERVICE account to the local WSS_WPG group.  This group is automatically granted Read permission to the C:\Program Files\Microsoft Office Servers\15.0 folder, which contains the Service subfolder identified in the 1004 event message.

Solution

  1. Log into the farm server hosting the User Profile Application.
  2. Launch the Computer Management applet.
  3. In Computer Management, go Computer Management > System Tools > Local Users and Groups > Groups.
  4. Scroll down to the bottom and then double-click the WSS_WPG group.
  5. Add the NETWORK SERVICE account.
  6. Test by manually launching a new profile synchronization and then again checking the the server's Application event log.

References

Notes

  • I discovered the solution to this problem while troubleshooting a previous related issue that had caused the entire UPA to fail on our development farm.  This time, when I saw similar warnings appear again, this time on the production farm, I suspected that a similar solution would be viable, and it was.