Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An X.400 queue schedule status that is configured to Always changes to Frozen in Exchange Server 2003


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You configure an X.400 connector between two Microsoft Exchange Server 2003 servers.
  • You set the status on an X.400 connector to Never. To do this in System Manager, right-click the X.400 connector, and then click Properties. Click the Schedule tab, and then click Never.
  • In the Queue Viewer, you see that the queue�s state changes from Active to Scheduled after a few minutes.
  • You set the status on an X.400 connector to Always.
  • In the Queue Viewer, you see that the queue�s state changes from Scheduled to Frozen after a few minutes. You expect the queue�s state to change from Scheduled to Active.
This problem occurs even though it is documented in the Exchange System Manager Help file (the Exadmin.chm file)that X.400 queues cannot be frozen.

For more information about how to use the Queue Viewer in Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
823489 How to use Queue Viewer to troubleshoot mail flow issues

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must have Microsoft Exchange Server 2003 Service Pack 1 (SP1)installed on your computer.

Restart requirement

You do not have to restart your computer after you apply this software update.

Hotfix replacement information

This hotfix does not replace any other software updates.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
 
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   21-Feb-2005  23:38  6.5.7232.85     3,591,680  Emsmta.exe       

↑ Back to the top


Workaround

To work around this problem, restart the message transfer agent (MTA).

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Exchange Server 2003 Service Pack 2.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages

↑ Back to the top


Keywords: KB890739, kbexchange2003presp1fix, kbbug, kbfix, kbhotfixserver, kbqfe, kbautohotfix

↑ Back to the top

Article Info
Article ID : 890739
Revision : 7
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 290