Article ID: 818797
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition
SYMPTOMS
The message transfer agent (MTA) on an Exchange Server bridgehead server may stop working (crash), and you may receive an access violation error message.
CAUSE
This problem may occur if the remote procedure call (RPC) functions generate exceptions because the functions were called by using binding handles that have been used in a failed RPC call.
RESOLUTION
Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
Exchange Server 5.5 Service Pack 4 (SP4)
Restart Requirement
If the Event Viewer was open while the hotfix was installed, you must restart the computer for the hotfix to be effective.
Hotfix Replacement Information
This hotfix does not replace any other hotfixes.
File Information
Component: MTA
The English version of this fix has the file attributes (or later) 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 -------------------------------------------------------------- 01-Aug-2001 08:02 41,325 Dbserver.sch 16-Sep-2002 06:49 88,248 Dsadap.xv2 16-Sep-2002 06:49 33,049 Edi.xv2 17-Apr-2003 10:39 5.5.2657.39 1,941,776 Emsmta.exe 17-Apr-2003 11:09 5.5.2657.39 69,904 Ems_rid.dll 13-Jun-2001 08:05 133,435 Infoplog.cfg 17-Apr-2003 11:09 5.5.2657.39 19,728 Maxapia.dll 17-Apr-2003 11:09 5.5.2657.39 12,048 Maxapiv1.dll 17-Apr-2003 11:09 5.5.2657.39 167,184 Mtacheck.exe 17-Apr-2003 11:09 5.5.2657.39 743,696 Mtamsg.dll 17-Apr-2003 11:09 5.5.2657.39 16,144 Mtaperf.dll 17-Apr-2003 11:09 5.5.2657.39 16,656 Mtxapia.dll 17-Apr-2003 11:09 5.5.2657.39 11,536 Mtxapiv1.dll 13-Jun-2001 08:06 50,789 P2.xv2 17-Sep-2001 09:45 14,002 P42.tpl 16-Sep-2002 06:49 41,222 P772.tpl 16-Sep-2002 06:49 9,028 P772.xv2 29-Aug-2001 09:16 23,350 Rdi.xv2 18-Apr-2003 09:49 319,488 Uninst.exe 17-Apr-2003 11:09 5.5.2657.39 322,320 X400om.dll 17-Apr-2003 11:08 5.5.2657.39 40,208 X400omv1.dll 16-Sep-2002 06:49 31,276 X500dap.tpl
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
817903 XADM: New Naming Schema for Exchange Server Hotfix Packages
Keywords: kbhotfixserver kbqfe kbexchange550presp5fix kbbug kbfix kbqfe KB818797
