I can go to http://localhost/IdentityManagement/aspx/syncrule/AllSyncRules.aspx, new, create inbound Sync rule, General tab, enter info, Scope Tab, enter info, (person, text file, person), Relationship tab, any metaverse object to connectedsystemobject:person, and then when I hit "next" BANG. Unable to process request. The description for Event ID 8214 from source Windows SharePoint Services 3 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: A request was made for a URL, http://localhost, which has not been configured in Alternate Access Mappings. Some links may point to the Alternate Access URL for the default zone, http://testfim. Review the Alternate Access mappings for this Web application at http://testfim:36021/_admin/AlternateUrlCollections.aspx and consider adding http://localhost as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854 the message resource is present but the message is not found in the string/message table and The portal was unable to complete a request and showed a user the default error page. An unhandled exception was caught. Check the product diagnostic log file and then check the SharePoint log file. The alternate address mappings collections are "sharepoint - 80" and "central administration" and do not have http://localhost in them. I added http:/localhost to "sharepoint - 80" and received the same results. No errors on installation, everything looked good there.

Do you get the same results when you access it throw the testfim url (not localhost)?David Lundell www.ilmBestPractices.com

Yes. After looking further, it seems that this is data driven, where the data that is in the text file is somehow not correct and caused this error. (?) I added the localhost in the alternate mappings and the 8214 error stopped showing up in the event viewer, but the " The portal was unable to complete a request and showed a user the default error page. An unhandled exception was caught. Check the product diagnostic log file and then check the SharePoint log file. error still shows up. I'm following the "Introduction to publishing to AD from 2 auhoritative data sources" and have now changed to creating the sync rules for AD, which is working properly. However, the text file sync rule is still throwing the same error above from the "Microsoft.ResourceManagement.PortalHealthSource" source in the Application Event log. "

This appears to only blow up on an Attribute-Value Pair file when trying to create a Sync Rule...

Further test: The beginning in the Attribute-Value pair text file is: dn: dc=domain, dc=com This passes the MA creation tests, but when this line is in the Attribute-Value pair file, the Sync rule will not work, and throws the error listed above. When I remove this line, the MA is created properly AND the sync rule is created propelry.

Please contact product support and open a support case. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation