The purpose of this wiki is to cover an issue where exporting to Exchange 2007 dumps a ma-extension-error inside of the Synchronization Service Manager console.
In this case, we were working with a GalSync Solution. We had mail-enabled contact objects that are exporting to Microsoft Exchange 2007. We receive a ma-extension-error on several objects. Investigation takes us into the Application Event Log where we discover the below error message.
Log Name: Application Source: FIMSynchronizationService Date: 6/1/2012 5:45:06 PM Event ID: 6500 Task Category: None Level: Error Keywords: Classic User: N/A Description: The description for Event ID 6500 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 Exch2007Extension AfterExportEntryToCd() function when exporting an object with DN CN=Sample Fim Contact,OU=FIM Contacts,DC=sampledomain,DC=com. Type: Microsoft.MetadirectoryServices.ExtensionException Message: **** ERROR **** "Sample Fim Contact" is not valid for Alias. Valid values are: Strings formed with characters from a to z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each one of them should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the email address which is generated from such an alias. **** END ERROR **** Stack Trace: at Exch2007Extension.Exch2007ExtensionClass.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
Log Name: Application Source: FIMSynchronizationService Date: 6/1/2012 5:45:06 PM Event ID: 6500 Task Category: None Level: Error Keywords: Classic User: N/A Description: The description for Event ID 6500 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 Exch2007Extension AfterExportEntryToCd() function when exporting an object with DN CN=Sample Fim Contact,OU=FIM Contacts,DC=sampledomain,DC=com.
Type: Microsoft.MetadirectoryServices.ExtensionException
Message: **** ERROR ****
"Sample Fim Contact" is not valid for Alias. Valid values are: Strings formed with characters from a to z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each one of them should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the email address which is generated from such an alias.
**** END ERROR **** Stack Trace: at Exch2007Extension.Exch2007ExtensionClass.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
The problem here, is that the MailNickName Attribute contains invalid information for Microsoft Exchange Server 2007 and/or Microsoft Exchange Server 2010.
The best way to correct this issue is to correct the data at the source. If this is a GalSync solution, then you will need to go to the Source Mailbox User object and correct the MailNickName attribute. Once you do that, you will need to walk through a synchronization cycle to import the new information, and then synchronize the information.
Richard Mueller edited Revision 2. Comment: Removed (en-US) from title, added tags
Fernando Lugão Veltem edited Revision 1. Comment: added tags
Good