JimMueller
asked on
Missing Fax addresstype
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
Description:
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 http://www.microsoft.com/contentredirect.asp.
---
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
Description:
Permanent failure reported by policy group provider for 'CN=Recipient Policies,CN=ced-concord,CN =Microsoft Exchange,CN=Services,CN=Co nfiguratio n,DC=ced-c oncord,DC= com':'MAD. EXE', error=8000ffff. Taking provider offline.
For more information, click http://www.microsoft.com/contentredirect.asp.
---
Do I need to restart System Attendant after each RUS policy change? Where is it still finding the reference to the FAX address type?
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
Description:
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 http://www.microsoft.com/contentredirect.asp.
---
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
Description:
Permanent failure reported by policy group provider for 'CN=Recipient Policies,CN=ced-concord,CN
For more information, click http://www.microsoft.com/contentredirect.asp.
---
Do I need to restart System Attendant after each RUS policy change? Where is it still finding the reference to the FAX address type?
ASKER
I also forced replication via Sites & Services to no avail.
ASKER
Everything we've found is leading us down paths we already tried. Anyone?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
https://www.experts-exchange.com/questions/22900700/RUS-template-edit.html
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.