| Event Id | 523 |
| Source | MSExchangeMTA |
| Description | (MTA OPERATOR(18) Proc 166) (MTA OPERATOR(18) Proc 166) 12-03-02 02:57:57pm Add operation failed, entity /DC=NET/DC=EXAMPLE/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=COMPANY/CN=ADMINISTRATIVE GROUPS/CN=ROUTING GROUPS - FIRST/CN=ROUTING GROUPS/CN=RG-4/CN=CONNECTIONS/CN=FAX GW already configured (4) |
| Event Information | According to Microsoft: CAUSE : This issue occurs because the routing component cannot decode the X.400 address. The routing component only decodes the X.400 address if it determines that the X.400 address matches the local sites X.400 address. The local site address is determined from the default recipient policy instead of from the recipient policy for the particular site. The routing component incorrectly processes the X.400 address in situations where the address does not match the X.400 address of the local site. If a recipient policy has a Legacy (Exchange Server 5.5) distinguished name (DN) that does not match the Legacy DN contained in a specific local recipient policy, the routing component uses the default recipient policy. However, the Microsoft Exchange Information Store uses the local recipient policy to create the X.400 address, instead of the default recipient policy. WORKAROUND:To work around this issue, use one of the following methods: Remove the Local Recipient Policy 1. Delete the local recipient policy for the site where you experience this issue. 2. Allow sufficient time for the routing change to propagate throughout the organization. 3. Stop and then restart the IIS Admin Service. When you follow these steps, the Microsoft Exchange Information Store (Store.exe) uses the default recipient policy to match the routing destination. When you move to a native mode Exchange 2000 organization, it is best to delete all local recipient policies and use only the default recipient policy. Change the X.400 Proxy Address Change the X.400 proxy address on the affected recipient policy so that it matches the proxy address on the default recipient policy. |
| Reference Links | Message Sent Through a Fax Connector Generates an NDR After You Move the Routing Group |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.