May 22nd, 2012 6 comments
While busy looking into a strange error on Exchange 2010 provisioning this week I learned something again. While trying to export a new user to Active Directory (with Exchange 2010) mailbox provisioning I received the following error message.
The description for Event ID 0 from source FIMSynchronizationService 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:There is an error in Exch2010Extension AfterExportEntryToCd() function when exporting an object with DN CN=SMokgele,OU=Users,OU=Windmill,OU=SIML Business Units,DC=corp,DC=simlds,DC=com.Type: Microsoft.MetadirectoryServices.ExtensionExceptionMessage:**** ERROR ****Property RoleAssignmentPolicy can’t be set on this object because it requires the object to have version 0.10 (184.108.40.206) or later. The object’s current version is 0.0 (6.5.6500.0).**** END ERROR ****Stack Trace: at Exch2010Extension.Exch2010ExtensionClass.AfterExportEntryToCd(Byte origAnchor, String origDN, String origDeltaEntryXml, Byte newAnchor, String newDN, String failedDeltaEntryXml, String errorMessage) the message resource is present but the message is not found in the string/message table
Looking into the Sync Rules declared on the solution I found that the msExchServerName attribute that was being applied was specifying the DN of the server and not the legacyExchangeDN value.
Incorrect value: CN=ExchServer,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN= Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=simlds,DC=comCorrect value: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=ExchServer
Simple fix for a strange error.