Event Id 1004 Detection Of Product .Exe Does Not

The Resource Does Not Exist Posted by ieDaddy Jan 30, 2012 Active Directory, SharePoint 4 I recently set up the User Profile Synchronization services on SharePoint 2010 per a great article on Harbar.net: Everything seemed to run fine for several days, and then the synchronization failed to run at all and filled up the Events Log with all sorts of warning messages in regards to the MSIInstaller.

The first issue I looked at was getting the Forefront Identity Manager Service to start following a reboot; the service simply refused to start automatically despite being configured by SharePoint to do so.

Interestingly, both the User Profile Service and the User Profile Synchronization Service items listed in Central Admins Services on Server page listed the services as running.

Starting the FIM Service manually from the Windows Services snap-in succeeded.

My solution was to set both services to start automatically at boot time after a delay by reconfiguring the startup type of BOTH services and Automatic (Delayed Start) in the Windows Services snap-in.

This at least got the services up and running, but the service would stop every time I tried to run the Start Profile Synchronization from the Manage Profile Service: User Profile Service Application screen.

In examining the Event Logs, I saw that there was was one more thing I apparently needed to clean up; Every time I tried to kick off the synchronization job, the logs would fill up with MSIInstaller warnings about product detection failing.

Specific was a series of 1004 and 1001 Event IDs: Event 1004: Detection of product 90140000-104C-0000-1000-0000000FF1CE, feature PeopleILM, component 1AE472A9-E94A-41DC-9E98-F89A2821658F failed.

Event Id 1004 Detection Of Product .Exe Does Not

The resource C:Program FilesMicrosoft Office Servers14.0Toolsmakecert.exe does not exist.

Event 1001: Detection of product 90140000-104C-0000-1000-0000000FF1CE, feature PeopleILM failed during request for component 1681AE41-ADA8-4B70-BC11-98A5A4EDD046 These were repeated for several other component GUIDs.

Now, as we know, the WMI calls are made under the credentials of the Network Service account (If in doubt about what account is trying to access the resource, the User: field is the tip-off).

For some reason during the configuration of the UPS, this account isnt given permissions on the folder indicated in the event ( C:Program FilesMicrosoft Office Servers14.0 ).

As there were multiple calls to various sub-directories under the C:Program FilesMicrosoft Office Servers14.0 folder I gave the Network Service account read and execute permissions on the folder and sub-folders.

After this, I went back into Central Admin Manage Profile Service: User Profile Service Application and clicked on Start Profile Synchronization.

And we once again have Profile Synchronization with Active Directory working as verified by clicking on the Synchronizing status link and confirmed by opening the miisclient.exe on the server.

Share: Previous Final SoCal Code Camp Details Next Office 15 SharePoint 2012 Begins Technical Preview About The Author ieDaddy Computer Geek, SharePoint MadHatter, devOps Champion, Automation Fan, PowerShell Player and sometimes I write Blog Stuff.

Passionate about software delivery, devOps, agile and other things revolving around technology.

This blog is mostly just for me to play around with and keep my hand in web technology and PHP Related Posts SharePoint 2010 Disable Mobile Detection on a SharePoint Website August 15, 2013 The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired December 27, 2007 SharePoint 2010List Templates are not Available on the Site August 1, 2011 Resetting the List Item ID Of A SharePoint List July 27, 2015 4 Comments Microsoft WTF on February 7, 2012 at 10:51 am I wonder why Microsoft doesnt test for this stuff Service accounts running local admin in production is such a bad idea Would be nice to have some sort of fix-it script that would fix all of these obvious security permissions issues.

Loading. Reply Thankful Admin on March 1, 2012 at 3:41 pm Thank you for this I was plagued by this problem, and your solution worked for me Loading.

Reply Mark Taylor on April 4, 2012 at 7:49 am Brilliant thank you.

I think this was all working but i used the content db domain account for the ups.

Once I gave rights to that directory, it started up with no issues.

Follow me on Twitter My Tweets Categories Cooking (11) Barbeque (5) Pressure Cooker (1) devOps (21) DevSecOps (1) Metrics (6) Family (5) Microsoft Certification (2) Personal (5) Organization (1) Sustainable Living (58) Backyard Farming (14) Camping (2) Composting (4) Continuous Learning (13) Gardening (8) Home Schooling (4) Organic Living (18) Recycling (2) Sustainable Resources (21) Technology (282).NET (9) Active Directory (6) Consulting (2) CSS (2) Geek Fu (23) HTML5 (3) IIS (2) InfoPath (2) JavaScript (3) Microsoft (3) Microsoft Office (3) PowerShell (31) Search (4) SharePoint (201) SQL Server (7) Team Foundation Server (6) Training (8) User Groups (5) Visual Studio (4) Windows (6) Windows Server 2012 (3) Uncategorized (9) Writing (3) Designed by Elegant Themes Powered by WordPress Share This Twitter Facebook Google LinkedIn d bloggers like this.