XCON: X.400 First Contact Form for X.400 Connector Problem

ID: Q165279

The information in this article applies to:

Microsoft Exchange Server, versions 5.5, 4.0, 5.0

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.

SUMMARY

This article contains a checklist that will help you collect information about your system before calling Microsoft Technical Support regarding a problem with the Microsoft Exchange Server X.400 Connector. You can work more effectively with a Microsoft support professional if all the information needed to trace and solve your problem is available.

Please use this checklist to document your problem and include any troubleshooting steps you have taken in an effort to resolve the problem. Be as complete and specific as possible when you fill out this form.

MORE INFORMATION

Microsoft Exchange Server X.400 Connector Problem Report Form

The following Exchange Server information is available in the Exchange Server Administrator program. On the Help menu, click About.

Exchange Server version:
Exchange Server Service Packs:

To collect the following operating system information:

For Windows NT Server 3.51, in Program Manager, on the Help menu, click About.

For Windows NT Server 4.0, click My Computer. On the File menu, click Properties, and then click the General tab.
Windows NT version:
Windows NT Service Packs:

To collect the following network information:

In Windows NT Server 3.51, in Control Panel, double-click the Network icon.

In Windows NT Server 4.0, click Network Neighborhood and select the server. On the File menu, click Properties, and then click the Identification tab.

Problem server information:
Name:
Installed Protocols:
X.400 Transport:

Are you connecting to another Exchange Server computer or another message transfer agent (MTA)? Fill in the following information if connecting to another Exchange Server computer.

To collect the following server information:

In Windows NT Server 3.51, in Control Panel, double-click the Network icon.

In Windows NT Server 4.0, click Network Neighborhood, select the server.

On the File menu, click Properties, and then click the Identification tab.
Other server name:

Fill out the following information if connecting to another MTA. This information is available from the other MTA's administrator:


   General foreign MTA information:

      Foreign MTA Software:                    Version:
      Foreign MTA Operating System:            Version:
      Foreign MTA Transport Stack:             Version:

   Foreign MTA local MTA information:

      Local MTA Name:
      Local MTA Password:
      Foreign MTA Stack Information:
                               TSAP
                               PSAP
                               NSAP

      Foreign MTA definitions for Exchange Server:
      Remote MTA Name:
      Remote MTA Password:
      Remote MTA Stack Information:
                               TSAP
                               PSAP
                               NSAP

What X.400 conformance mode is the MTA operating in?  84  |  X410  |  88

Has this worked before? (Yes/No)

If Yes, when did it quit working?

What, if anything, was changed before it quit working?

Is this problem seen on the foreign mail system? (Yes/No)

Is this problem seen on the local (Exchange Server) system? (Yes/No)

Is this problem intermittent or consistently reproducible?

Can mail be sent from the foreign mail system to Exchange Server by X.400?
(Yes/No)

Can mail be sent from Exchange Server to the foreign mail system by X.400?
(Yes/No)

List Any Error Messages
-----------------------

Files Needed

Find and extract the connector dump files and the stack dump files and have them ready to send to Microsoft Technical Support (preferably electronically):

To obtain these files:

From a command prompt, run Admin with the /r option.

Highlight the problem connector.

Press CTRL+SHIFT, and choose File, Raw Properties. When the Properties dialog box is displayed, close it.

A file called Admindmp.txt is created in the Exchsrvr\Bin directory. Rename it to X400con.dmp. Repeat steps 1 through 3 and rename the Admindmp.txt file created to X400stk.dmp.

Text Event Logs

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.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

To generate text event logs:

Rename the BF*.log and EV*.log files in the Exchsrvr\Mtadata directory.

Using Regedit32, in the following container
```
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA
   \Parameters 
```
create the following value: TextEventLog:REG_DWORD: 1

Restart the MTA.

The Text Event log will be created as Ev*.log in Exchsrvr\Mtadata.

For additional information, please see the following article in the Microsoft Knowledge Base:

Q168906 XCON: Setting up Advanced Logging on Exchange 5.0 and 5.5 MTAs

Diagnostic Logging

To generate diagnostic logging, do the following:

Rename the Ap*.log and Bf*.log files in the Exchsrvr\Mtadata directory.

Run Admin and select Configuration\Servers\<ServerName>\Message Transfer Agent.

Go to the Diagnostics tab and set the X.400 Service, Interface, Interopability, APDU settings to Maximum. This creates Ap*.log and Bf*.log files in the Exchsrvr\Mtadata directory.

Describe the Problem

Additional query words: x400fcc fcc first contact

Keywords : kbusage XCON exc4 exc5 exc55
Version : winnt:4.0,5.0,5.5
Platform : winnt
Issue type : kbhowto