The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SYMPTOMSCustomers may report that their X.25 connection is no longer working. Symptoms of this behavior can be tracked down with Event Viewer by setting the logging for the diagnostic option "X.400 service" to Medium. This should produce the following event:
Logging will also register another event:
When you use Eicon's diagnostics ECMODULE, STATUS X25 shows no "x25listen"
application. An Eicon Trace shows only incoming calls, which will be
refused right away with Clear code 40 (Call set up, clearing, or
registration problem).
CAUSEMicrosoft Exchange Server configured with the Eicon X.25 stack may be set to an incorrect number of control blocks or virtual circuits. WORKAROUND
WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry Editor
can be solved. Use Registry Editor at your own risk.
MORE INFORMATIONMicrosoft Exchange Server configured with the Eicon X.25 stack can only support up to 32 control blocks or virtual circuits. If any more than 32 control blocks are configured, error 9106 will be logged at initialization, and no X.25 functions will be available. Additional query words: X.25, Eicon, X25
Keywords : |
Last Reviewed: May 7, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |