We brought up a new Mail Cluster (CCR) and on the 2nd Cluster - we cannot add new EMAIL Addresses to a Distribution list - we get the following errorsI found an article that's similar that's KB928811 but its for an SCC cluster not a CCR cluster and says the MTA is missing but I checked with ADSI edit and the MTA isn't missing.Errors-------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- The following error(s) occurred while saving changes: Set-DistributionGroup Failed Error: A proxy generator DLL on server EMAIL-CLUSTER2.acme.com could not be found or failed to initialize. Proxy addresses for the current recipient cannot be calculated. Please ensure that all the proxy address generator DLLs have been installed on the target server.

This could be related: This may be related: Log Name: Application Source: MSExchangeSA Date: 11/10/2009 12:44:06 PM Event ID: 2030 Task Category: General Level: Error Keywords: Classic User: N/A Computer: EMAIL-CLUSTER2.acme.com Description: Unable to find the e-mail address 'X400:c=us;a= ;p=Acme;o=Exchange;s=bitbucket; ' in the directory. Error 'c0072019'. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchangeSA" /> <EventID Qualifiers="49152">2030</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-11-10T17:44:06.000Z" /> <EventRecordID>15876</EventRecordID> <Channel>Application</Channel> <Computer>EMAIL-CLUSTER2.acme.com </Computer> <Security /> </System> <EventData> <Data>X400:c=us;a= ;p=Acme;o=Exchange;s=bitbucket; </Data> <Data>c0072019</Data> </EventData> </Event> I wonder if the X400 Addresses arent getting created on the new mailbox environment.

Troubleshooting: 1. Please describe the exchange topology 2. Does the issue happen to all DLs? Does the issue happen to newly created DL? 3. You said We brought up a new Mail Cluster (CCR), is there an old CCR? If yes, please compare the attributes between fine DL and problematic DL, see if theres any difference 4. Please add -verbose parameter after the cmdlet and reproduce the issue, check the output 5. Error c0072019 indicates Unable to contact the global catalog server, Please run "DCdiag.exe /v" and 'Netdiag.exe /v" command on the problematic node to see if there is any failed tests in the result 6. Please run ExBPA against the exchange server for health check 7. Please go to C:/Programfiles/Microsoft/Exchangeserver/Mailbox folder on the problematic node, verify if Address or/and Schema folder are missing, and the folders have permissions for System account on both at NTFS and share levelsJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

I would also run EXBPA just in case to make sure all exchange configs are in place. http://www.microsoft.com/downloads/details.aspx?FamilyID=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3&displaylang=enVinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Interestingly enough - we turned off "Automatically update email addresses based on email address policy on the Email addresses tab of the Mail-Enabled Distribution Group Object and the error has gone away.I am wondering if this is a leftover RUS policy or something where it tried to stamp it with X400 but didn't know how to.When I open that object - I can see the 90+ SMTP aliases and 1 X400 address - and since the eventvwr was spitting errors related to X400.I am running the stuff you all requested above as well!Thanks,Rob

Follow that KB and make sure that the values it references are actually correct. I've seen this happen where the MTA objects exist but have bad data on them.Thanks, Brian Desmond Active Directory MVP www.briandesmond.com Active Directory, 4th Edition - www.briandesmond.com/ad4/