KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q162012: XADM: Unable to Change the Routing Calculation Server

Article: Q162012
Product(s): Microsoft Exchange
Version(s): 4.0
Operating System(s): 
Keyword(s): 
Last Modified: 21-APR-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Exchange Server, version 4.0 
-------------------------------------------------------------------------------


SYMPTOMS
========

In a Microsoft Exchange Server Site, with multiple Servers, you may choose to
change the Routing Calculation Server on the Site Addressing property page in
the Microsoft Exchange Administrator program. After making the change, the Apply
button is grayed out and if you click the OK button and reopen the property page
to check the setting, the Routing Calculation Server will be set back to the
original Server.

WORKAROUND
==========

After changing the Server selection, select and deselect the Share Address Space
with other X.400 Systems checkbox. This will enable the Apply button and allow
you to successfully change the Routing Calculation Server.

STATUS
======

Microsoft has confirmed this to be a problem in Exchange Server 4.0. It has been
corrected in Exchange Server 5.0.

Additional query words: routing server change calculation
======================================================================
Keywords          :  
Technology        : kbExchangeSearch kbExchange400 kbZNotKeyword2
Version           : 4.0

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.