Validated that the 3rd Party Rules Extension DLL, was in the <FIM INSTALL PATH>\2010\Synchronization Service\Extensions folder.
Reviewed the Metaverse Extension in the Options dialog, and discovered that we had a Metaverse Router DLL.
Utilized a tool called
Process Monitor, which assisted in isolating the issue.
Downloaded and Extracted Process Monitor
Process Monitor starts logging immediately on the launch of the tool
Preview one of the objects throwing the error
Once the error occurred, stop Process Monitor by clicking on the Magnifying Glass on the button bar
From the Filter menu, select Filter
In the Filter dialog, select Path, then contains, then type the name of the DLL in question.
Click the Add button to include the DLL, and filter to just that DLL.
Click the Ok Button
Your process monitor log will filter down to anything containing the name of the DLL in the Path column. In my scenario, it appears like the below picture. We had four file locations that were checked, and in each case, we received
PATH NOT FOUND or NAME NOT FOUND.
Based on this information, we checked the locations, and in-deed the file did not exist.
Placed the DLL into the first directory referenced
Stopped the Synchronization Service in the Services MMC
Start the Synchronization Service in the Services MMC
Tested with success