Here are some steps to begin your troubleshooting: The first step, is always to click on the words ma-extension-error. In some cases, you will discover informtaion on the dialog that is displayed that may assist you in locating the cause of the error message. Go to the Application Event Log and look for errors Event Source: (FIM 2010: FIMSynchronizationService) (ILM 2007 FP1: MIISERVER) Some Event IDs you may look for: 6801, 6500 Troubleshoot / Test the Export. Review this wiki for more information on troubleshooting / testing the export.
Here are some steps to begin your troubleshooting:
In most cases you will notice the ma-extension-error in a GalSync Solution that is exporting to a Microsoft Exchange 2007 and/or Microsoft Exchange 2010 server. The ma-extension-error displayed in the Synchronization Service Manager Console, is a generic error message. You will need to review the dialog, application event log, and possibly do other troubleshooting steps to discover the actual error. In most cases, you will receive this message because something has not been configured correctly when setting up Exchange 2007 and/or Exchange 2010 provisioning. You may want to take a look or a even possibly a second look at the following wiki pages. Provisioning to Microsoft Exchange 2007 Provisioning to Microsoft Exchange 2010
Event ID 6801 - Text of different 6801 errors Could not find the default Administrative Group ‘Exchange Administrative Group’ This text is an indication that the user specified on the “Connect to Active Directory Forest” tab is not a member of the Exchange Recipient Administrators Group if exporting to Microsoft Exchange 2007, or the Microsoft Exchange Security Group – Organization Management if exporting to Microsoft Exchange 2010. The Exchange server address list service failed to respond The text here is an indication that there is a problem on the Microsoft Exchange Server. Here is a Microsoft TechNet Wiki on the topic. TROUBLESHOOTING: Event ID 6801: The Exchange server address list service failed to respond ExternalEmailAddress is mandatory on MailUser In this case, we have found that the problem is in the Exchange PowerShell CMDLET Update-Recipient. The recommendation here is to get to the latest Exchange 2007 Service Pack, which as of May 16, 2012 is Microsoft Exchange 2007 Service Pack 3 Rollup Update 4. You can download it from here. Event ID 6500 is not valid for Alias The above text is a snippet of the 6500 error that talks about the alias (MailNickName) having an invalid value. Here is a wiki page that discusses the issue, and leads you to a resolution. TROUBLESHOOTING: ma-extension-error: Event ID 6500: is not valid for Alias
This text is an indication that the user specified on the “Connect to Active Directory Forest” tab is not a member of the Exchange Recipient Administrators Group if exporting to Microsoft Exchange 2007, or the Microsoft Exchange Security Group – Organization Management if exporting to Microsoft Exchange 2010.
The text here is an indication that there is a problem on the Microsoft Exchange Server. Here is a Microsoft TechNet Wiki on the topic. TROUBLESHOOTING: Event ID 6801: The Exchange server address list service failed to respond
In this case, we have found that the problem is in the Exchange PowerShell CMDLET Update-Recipient. The recommendation here is to get to the latest Exchange 2007 Service Pack, which as of May 16, 2012 is Microsoft Exchange 2007 Service Pack 3 Rollup Update 4. You can download it from here.
The above text is a snippet of the 6500 error that talks about the alias (MailNickName) having an invalid value. Here is a wiki page that discusses the issue, and leads you to a resolution. TROUBLESHOOTING: ma-extension-error: Event ID 6500: is not valid for Alias
Tim Macaulay edited Revision 20. Comment: EN-US, FIM, FIM 2010, FIM2010, FIM TROUBLESHOOTING ARTICLE, FIM RESOURCES, GALSYNC, GALSYNC TROUBLESHOOTING ARTICLE, GALSYNC EXPORT ARTICLE, GALSYNC RESOURCES, EXCHANGE 2007 PROVISIONING, EXCHANGE 2010 PROVISIONING, MIISILMFIM MACAULAY
Tim Macaulay edited Original. Comment: added the see also section