After setting up a X500 address for one of our users that was migrated from a now-removed Exchange org, we're getting the following in our Exchange Application log: Event Type: Error Event Source: MSExchangeSA Event Category: General Event ID: 2035 Date: 8/10/2011 Time: 9:28:04 AM User: N/A Computer: [Our corporate exchange server] Description: The e-mail address description object in the Microsoft Exchange directory for the 'X500' address type on 'i386' machines is missing. For more information, click http://www.microsoft.com/contentredirect.asp. I've been able to track it down to the addrType entry for X500 is missing in ADSIEDIT. Is there a way to add this entry to AD? I thought that x500 was support OOTB with Exchange 2003. The mail appears to still be working, but these errors are filling up our event logs already and I've only made the change for 1 user. Any ideas? Below is the screenshot of the addrTypes in ADSIEDIT:

My environments don't X500 listed under address-types either although we have no problems with event logs or x500. Check the formatting of your x500 to make sure it is correct. I have seen where it looks like: /O=organization/OU=server/Recipients/alias When it should have been: /O=organization/OU=server/cn=Recipients/cn=aliasDJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

I've checked the users that have X500 configured and they appear to be correct. Is the x500 address case sensitive? I've changed the entries to all caps now, but they match the format you gave me.

On Thu, 11 Aug 2011 13:56:33 +0000, JoelIClark wrote: > > >After setting up a X500 address for one of our users that was migrated from a now-removed Exchange org, we're getting the following in our Exchange Application log: > >Event Type: Error Event Source: MSExchangeSA Event Category: General Event ID: 2035 Date: 8/10/2011 Time: 9:28:04 AM User: N/A Computer: [Our corporate exchange server] Description: The e-mail address description object in the Microsoft Exchange directory for the 'X500' address type on 'i386' machines is missing. > >For more information, click http://www.microsoft.com/contentredirect.asp. I've been able to track it down to the addrType entry for X500 is missing in ADSIEDIT. Is there a way to add this entry to AD? I thought that x500 was support OOTB with Exchange 2003. The mail appears to still be working, but these errors are filling up our event logs already and I've only made the change for 1 user. Any ideas? > >Below is the screenshot of the addrTypes in ADSIEDIT: You're not using X550 as an address type in a recipient policy, are you? Have a look at the gatewayProxy and see if there's something there. Way down at the bottom of this KB: http://support.microsoft.com/kb/286356 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Joel, This behavior appears to be "by design" and does not affect the performance of the System Attendant or RUS. Could you ignore it and try to find whether there's any effect?Best Regards!

I saw that KB earlier as well. The x500 addresses are only on 2 users in our entire org, although that'll be increasing to about 25 soon. Interestingly, when I made sure all the x500 addresses were in all caps, the event log entries have disappeared. Now if I add it to the recipient policies (since a whole org will need these x500 addresses in place), will that cause any issues? Can I add the x500 addrType in adsiedit or will that cause more issues?

On Fri, 12 Aug 2011 12:41:50 +0000, JoelIClark wrote: >I saw that KB earlier as well. The x500 addresses are only on 2 users in our entire org, although that'll be increasing to about 25 soon. Interestingly, when I made sure all the x500 addresses were in all caps, the event log entries have disappeared. Now if I add it to the recipient policies (since a whole org will need these x500 addresses in place), Do *not* add it to any recipient policies. >will that cause any issues? Probably. I never tried it, but you already said there's no X500 address type generator. >Can I add the x500 addrType in adsiedit or will that cause more issues? I've used X500 address types for a long time and never had the problem you note. I wouldn't use ADSIEDIT to add theose addresses. That bypasses everything built into the Exchange software. Use the ADUC and add them as "Custom" addresses. As far as "case sensitivity" goes, I've always use whatever the original legacyExchangeDN property value had in it to populate the proxyAddresses property. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP