none
Mail delivery is slower than expected, or mail delivery stops, on an X.400 connector to a remote site in Exchange Server RRS feed

  • 問題

  •  

    We are Mixed Mode Exchange Organization & Windows 2000 AD, use X.400 connector in Exchange 5.5 to connect to remote site each other within the organization. But the mail delivery was slower than expected, even the mail delivery stop. The the scene was only existed in our exchange site, the remote X.400 connector server was functioned normally to other remote site. We have installed hotfix KB 904712, but the problem is still existed in our Exchange organization, any other solution.

     

    Regards

     

    James

     

     


     

    2008年8月14日 上午 02:22

解答

  •  

    Dear customer:

     

    As the support for Exchange 5.5 has been stop, we will only check the setting on Exchange 2000 Server and try our best to fix the issue, however we cann’t gurantee the issue can be resolved.

     

    IF you want to know more about Microsoft Support Lifecycle, please refer to the following documents:

    Microsoft Support Lifecycle

    http://support.microsoft.com/?pr=lifecycle#Extended%20Support

     

    First, you can try the resolution in the following KB article, and check the effect.

    MTA slows down or stalls in Exchange Server 5.5 and messages back up in the private information store

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;327260

     

    Additionally, please help collect the following information:

     

    1.       Did you have Exchange 2000 server in your enviroment?

    2.       On Exchange 2000, open ESM, right click Exchange 2000 server, select properties, click diagnostic logging,

    3.       Select MSExchangeMTA, click X.400 Service, increase the log level to maximum,

    4.       According to the above steps and increase all categories under MSExchangeTransport to maximum.

    5.       Reproduce the issue,

    6.       Save the application log file on Exchange server 2000 as .evt file and send it to v-rocwan@microsoft.com for further research.

     

    Note: when you send e-mail to me, please add the subject of the post.

     

    Rock Wang - MSFT

    2008年8月14日 上午 09:40
    版主

所有回覆

  •  

    Dear customer:

     

    As the support for Exchange 5.5 has been stop, we will only check the setting on Exchange 2000 Server and try our best to fix the issue, however we cann’t gurantee the issue can be resolved.

     

    IF you want to know more about Microsoft Support Lifecycle, please refer to the following documents:

    Microsoft Support Lifecycle

    http://support.microsoft.com/?pr=lifecycle#Extended%20Support

     

    First, you can try the resolution in the following KB article, and check the effect.

    MTA slows down or stalls in Exchange Server 5.5 and messages back up in the private information store

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;327260

     

    Additionally, please help collect the following information:

     

    1.       Did you have Exchange 2000 server in your enviroment?

    2.       On Exchange 2000, open ESM, right click Exchange 2000 server, select properties, click diagnostic logging,

    3.       Select MSExchangeMTA, click X.400 Service, increase the log level to maximum,

    4.       According to the above steps and increase all categories under MSExchangeTransport to maximum.

    5.       Reproduce the issue,

    6.       Save the application log file on Exchange server 2000 as .evt file and send it to v-rocwan@microsoft.com for further research.

     

    Note: when you send e-mail to me, please add the subject of the post.

     

    Rock Wang - MSFT

    2008年8月14日 上午 09:40
    版主
  • Thanks for your kindly helping. We have Exchange 2003 Server and Exchange 5.5 in Mixed Mode Exchange Organization.

    All the IMS & X.400 connector was installed in Exchange 5.5. Our Exchange orgnaization have a few of exchange site, all of it use x.400 connector run in Exchange 5.5 to connect to remote site within our organization.We found other exchange site within the organization not such the case like us. Our mail was always queued even other connector in same exchange server was normal. We deliver the mail use Exchange 5.5 connector, the exchange 2003 is not services running, so can't check anything. Any cue for it ?

     

    Regards

     

    James

    2008年8月15日 上午 01:27
  •  

    The problem was existed a long time, say 1 - 2 years, but seems not way to solve it. Anyone can help ?

     

     Mail was queued in MTA, Always need to restart for both site MTA services.(Exchange 5.5 X.400 connector connect to both exchange site)

     

     

    2008年8月15日 上午 02:06
  •  

    Just want to know that any other solution can help ?
    2008年8月31日 上午 03:57
  • Dear customer:

     

    We have ended the support for Exchange 5.5 server. We will troubleshoot on the Exchange 2003 server and will try to resolve the issue.

     

    In order to better troubleshoot the issue, please help collect the following information:

     

    1.       Check whether you can ping each other?

    2.       Check whether you can telnet Exchange 5.5 on port 25 on Exchange server 2003,

    3.       Check whether you can telnet Exchange 2003 on port 25 on Exchange server 5.5,

    4.       Check whether you install 898060 hotfix on Exchange server 2003, if no, install it and reboot the server, check the effect.

     

    Network connectivity between clients and servers may fail after you install security update MS05-019 or Windows Server 2003 Service Pack 1

    http://support.microsoft.com/kb/898060/en-us

     

    5.       According to the following article, check the store.exe file versions, if it is older than the version that described in the following article, please install them on Exchange 5.5 server.

     

    The Store.exe process on an Exchange 5.5 Server computer may stop responding, and event 1220 and event 1114 are logged

    http://support.microsoft.com/kb/833317/en-us

     

    A message from a foreign X.400 system causes a non-delivery report to be generated in Exchange 5.5

    http://support.microsoft.com/kb/829706/en-us

     

    6.       On the Exchange server 2003, check whether afd.sys file version is greater than the following article, if not, install the following hotfix, and check the effect.

    The Afd.sys file triggers a "Stop 0x000000D1" error on a Windows Server 2003-based computer

    http://support.microsoft.com/kb/894070/en-us

     

    7.       Check whether you install antivirus software on Exchange server 2003, if so, check whether you exclude the following directory:

    C:\PROGRAM FILES\EXCHSRVR\ and all its sub folders

    C:\WINNT\SYSTEM32\INETSRV\ and all its sub folders

     

    For more information about Exchange Server 2003 and antivirus software coexists, please refer to the following documents:

    Recommendations for troubleshooting an Exchange Server computer with antivirus software installed

    http://support.microsoft.com/kb/245822/en-us

     

    Overview of Exchange Server 2003 and antivirus software

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;823166

     

    8.       Run portquery and check whether port 102 is listening on both the servers.

     

    HOW TO: Use Portqry to Troubleshoot Active Directory Connectivity Issues

    http://support.microsoft.com/kb/816103/en-us

     

    9.       On Exchange server 2003, add black hole registry entry as follows according to the following article:

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP

    EnablePMTUBHDetect

    EnablePMTUDiscovery

     

    TCP/IP and NetBT configuration parameters for Windows 2000 or Windows NT

    http://support.microsoft.com/kb/120642/en-us

     

    10.   Run mtacheck.exe /rd /rp /rl, and restart MTAStacks on Exchange 2003 server.

    Followed XCON: Performing An MTACHECK

    http://support.microsoft.com/kb/175495/en-us

     

    XCON: How and Why to Run Mtacheck

    http://support.microsoft.com/kb/163326/en-us

     

    11.   Run msconfig command and check whether you load third party tool such as Secure port scanner, if so, disable it, restart Exchange server and check the effect.

     

    Hope it helps. If anything is unclear, please feel free to let me know.

     

    Rock Wang - MSFT

    2008年9月25日 上午 11:58
    版主