Missing Fax addresstype

Posted on 2008-10-02
Last Modified: 2012-05-05
We had a Fax connector we used with Exchange 5.5, and it was migrated over when we switched to Exchange 2003. We recently switched to using a SMTP connector instead and removed the old connector which the vendor advised was no longer supported by Microsoft.

We are now having problems with newly created accounts having their e-mail addresses being generated. Messages sent to that mailbox are delayed in the local queue. The Exchange app log indicates it cannot rebuild RUS because it is missing a the FAX addresstype for i386. What I've tried so far:

- I looked at the RUS policies and unchecked all FAX options. Looked in ADSIEdit for gatewayproxy, and it was blank. Updated RUS, same error in App log (2035)
- Actually removed the Fax options in the RUS and restarted System Attendant. 2035 error still shows up and RUS will not complete.
- Could not find the 'proxyaddressincluded' nor 'proxyaddressesexcluded' objects in ADSIEdit as mentioned in a related forum question
- Bumped up AL and SA logging

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      2035
Date:            10/2/2008
Time:            10:41:51 AM
User:            N/A
Computer:      FL2000-EXCH002
The e-mail address description object in the Microsoft Exchange directory for the 'FAX' address type on 'i386' machines is missing.

For more information, click
Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8231
Date:            10/2/2008
Time:            10:41:51 AM
User:            N/A
Computer:      FL2000-EXCH002
Permanent failure reported by policy group provider for 'CN=Recipient Policies,CN=ced-concord,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ced-concord,DC=com':'MAD.EXE', error=8000ffff.  Taking provider offline.  

For more information, click

Do I need to restart System Attendant after each RUS policy change? Where is it still finding the reference to the FAX address type?
Question by:JimMueller
  • 4

Author Comment

ID: 22625318
Found this:

The Fax address type was still listed in disabledGatewayProxy, removed them, re-tried Update, still had the same errors. Restarted all Exchange services and SMTP, same errors.

Author Comment

ID: 22625346
I also forced replication via Sites & Services to no avail.

Author Comment

ID: 22633142
Everything we've found is leading us down paths we already tried. Anyone?

Accepted Solution

JimMueller earned 0 total points
ID: 22633763
Here are some of the Microsoft articles I reviewed in troubleshooting this issue, in addition to g00gling for answers: <- informational <- not applicable to us as not receiving the same errors <- We had errors 2035 & 8231, but not 2027 nor 2037 <- generic troubleshooting <- not applicable to us as not receiving the same errors <- this is the one that led me to call you

The fix ended up being:

For each of the recipient update policies:
1)      Right-click, Change Property Pages&, check all options, click OK
2)      Properties, E-mail Addresses, uncheck and/or remove the Fax address type, click OK

In ADSIEdit:
1)      Browse to Configuration > Configuration > CN=Services > CN=[domain] > CN=Address Lists Container > CN=Recipient Update Services
2)      In the right pane, for each of the entries:
a.      Right-click policy and choose properties
b.      Scroll through the attributes and for each of these two attributes [proxyAddresses] and [gatewayProxy]:
i.      Click Edit
ii.      Remove any references to the FAX type
iii.      Click OK
c.      Click OK

Update and/or Rebuild the RUS entries. The errors are now gone and the new accounts are now showing up correctly in the GAL, etc. I would have had this solved earlier but the policies were only showing 1 of the 2 property pages, and that was where the hidden fax fields remained.

Featured Post

Networking for the Cloud Era

Join Microsoft and Riverbed for a discussion and demonstration of enhancements to SteelConnect:
-One-click orchestration and cloud connectivity in Azure environments
-Tight integration of SD-WAN and WAN optimization capabilities
-Scalability and resiliency equal to a data center

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
how to add IIS SMTP to handle application/Scanner relays into office 365.

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question