After sorting out a problem with the FIM Service not starting automatically after a reboot and several resultant application event log errors, there was one more thing to clean up: running a user profile sync would spit a couple of MsiInstaller warnings about product detection failing (see below).
Various users in the forums suggested granting the Network Service account read access to the C:\Program Files\Microsoft Office Servers\14.0\Service directory and/or the C:\Program Files\Microsoft Office Servers\14.0\Sql directory; I initially found only the latter was required (this directory currently has Read & execute, List folder contents, and Read) but on reboot, the same warnings were logged again. Granting the same access to \Services had the same result and I've found starting a crawl produces these warnings but they go away with subsequent crawls. Reboot and they're back :-(
This change relates to the following warnings logged as a crawl is initialised:
Log Name: Application
Source: MsiInstaller
Date: 2/09/2010 3:40:24 PM
Event ID: 1004
Task Category: None
Level: Warning
Keywords: Classic
User: NETWORK SERVICE
Computer: dev-sps2010-01.dev.mediawhole.com
Description:
Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed. The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.
Log Name: Application
Source: MsiInstaller
Date: 2/09/2010 3:40:24 PM
Event ID: 1001
Task Category: None
Level: Warning
Keywords: Classic
User: NETWORK SERVICE
Computer: dev-sps2010-01.dev.mediawhole.com
Description:
Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM' failed during request for component '{9AE4D8E0-D3F6-47A8-8FAE-38496FE32FF5}'
Log Name: Application
Source: MsiInstaller
Date: 2/09/2010 3:40:24 PM
Event ID: 1015
Task Category: None
Level: Warning
Keywords: Classic
User: NETWORK SERVICE
Computer: dev-sps2010-01.dev.mediawhole.com
Description:
Failed to connect to server. Error: 0x80070005
Have you managed to find a solid solution to this?
ReplyDeleteI've had it for a while and I've been following some MSDN forum threads, but no one has a solid solution.
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/950902d4-9755-4568-acd6-3edb36fb6676
Hi Craig,
ReplyDeleteNo I haven't yet--just been ignoring them to date. That said, I haven't checked it out again since applying the DTC change Spence Harbar suggests in his follow up article to the Rational Guide: http://www.harbar.net/articles/sp2010ups2.aspx
I doubt the two are related but maybe?? :-)
Also haven't revisited with the August CU--maybe worth a shot? (Although I understand the CU introduces new warnings due to a binary incompatibility--which can apparently be ignored if you go there).
I have the same issue. We installed the August CU to get Profile Sync working, which it did, but this was a side effect.
ReplyDelete@Dan: Out of curiosity, did you end up reprovisioning the UPS after installing the August CU?
ReplyDeleteI'm getting the same errors with a new farm. Installed August CU before creating the farm. Followed Spencer's article on provisioning UPS, as well. Drats!
ReplyDeleteyou can get rid off Event ID 1004 (ILM) Error with granting the Network Service permissions to the
ReplyDelete'C:\Program Files\Microsoft Office Servers\14.0\*' directory.
http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/ff3b7ecc-ae43-4c64-8745-4beb28f92c39
This issue happens with SharePoint 2013 Server too.
ReplyDelete