United States*
Microsoft.com Home|Site Map
Microsoft*
Search Microsoft.com for:
Help and Support 
|Select a Product|Search Knowledge Base

Microsoft Exchange Server 2003

Go To: Exchange Server 2003 > Download details
Download details - Exchange Server 2003

Download details - Exchange Server 2003

•A global event sink is not triggered after you restart the Microsoft Exchange Information Store service in Exchange Server 2003 Service Pack 1
Describes a problem that occurs if you restart the computer or if you restart the Microsoft Exchange Information Store service.
•Error message when you run the Eseutil command to determine the amount of free space in a database file in Exchange Server 2003 Service Pack 2 or in Exchange Server 2003 Service Pack 1: "Usage error: Source database has no streaming file"
Describes an error message that you receive when you run the Eseutil command by using the /ms and /s switches in Exchange Server 2003 SP2 or Exchange Server 2003 SP1. Also describes a hotfix.
•Users do not appear in the Global Address List, users cannot connect to their Exchange mailboxes, event ID 8331 is logged, and e-mail names cannot be resolved in Exchange Server 2003
Fixes a problem in Exchange Server 2003 where event ID 8331 error messages are repeatedly logged to the application event log and the Recipient Update Service does not configure all the Exchange attributes for the user accounts.
•The recipient does not receive an attachment when an RTF e-mail message is delivered though an Exchange Server 2003 bridgehead server
Describes that the recipient may not receive the attachment when a rich text format e-mail is delivered through an Exchange Server 2003 bridgehead server. To resolve this issue, you can install a hotfix.
•Replication from the Site Replication Service on an Exchange Server 2003 computer to an Exchange Server 5.5 computer stops, and event IDs 1171 and 1082 are logged in the Application log
Explains a problem in which replication between the SRS on an Exchange Server 2003 computer and an Exchange Server 5.5 computer stops. Provides information about a hotfix that resolves this problem.
•System Attendant service quits when you edit the Lotus Notes proxy address of a user
When you edit the IBM Lotus Notes proxy e-mail address for a user by using the Active Directory Users and Computers snap-in, the Microsoft Exchange System Attendant service (Mad.exe) quits unexpectedly. Additionally, the following event may be...
•Exchange 2000 and Exchange 2003 mailbox size limits are not enforced in a reasonable period of time; fix requires Exchange 2000 SP3
Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003 mailbox size limits may not be enforced in a reasonable period of time. If users log off and log on, performance does not improve. If you restart the information store, the limits...
•Event ID 2116 is logged when a domain controller is not running Windows 2000 Service Pack 3
MSExchangeDSAccess on your Microsoft Exchange Server 2003 computer has stopped, and an event ID error message similar to the following is logged in the application log of Event Viewer: Event Type: WarningEvent Source: MSExchangeDSAccess Event...
•If you use OWA to post a message to a public folder in Exchange 2000 or in Exchange Server 2003, you cannot use Outlook Express to view the message
Describes a problem where you cannot see a message that you posted using OWA in Outlook Express. To resolve this problem, install the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup or Exchange 2003 SP1.
•How to configure SSL Offloading for Outlook Web Access in Exchange 2000 Server and in Exchange Server 2003
Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003 have a configuration option that can help if you are using third-party Secure Sockets Layer (SSL) hardware accelerators. If the SSL session is terminated by an SSL hardware...
•Bcc information is lost for journaled messages in Exchange 2000
When you journal e-mail messages in Microsoft Exchange 2000 Server or in Microsoft Exchange Server 2003, any Blind Carbon Copy (Bcc) information in the message is lost. To resolve this problem, use the appropriate method. Microsoft Exchange 2000...
•Exchange user unexpectedly receives a standard NDR instead of a custom NDR
When a Microsoft Exchange 2000 Server user or a Microsoft Exchange Server 2003 user composes and sends a message to a recipient on an external domain that is configured to use a custom non-delivery report (NDR), if the address of the recipient is...
•Understanding and catching silent exits of the Exchange Information Store in Exchange 2000 Server and in Exchange Server 2003
The Microsoft Exchange Information Store self-terminates in Microsoft Exchange 2000 Server or in Microsoft Exchange Server 2003. This is known as a "silent exit." This article defines what is and is not a "silent exit" and describes the facilities...
•Exchange Server Migration Wizard may crash when you use it to migrate Exchange Server 5.5 mailboxes to .pst files
Describes issue where Migration Wizard crashes when you use it to migrate Exchange Server 5.5 mailboxes to .pst files. To resolve this issue, obtain the latest service pack for Exchange Server 2003.
•Meeting requests are not delivered if a recipient's mailbox has exceeded the storage limit and the recipient has defined a delegate
If a Microsoft Exchange Server user sends a meeting request to another user whose mailbox has exceeded the defined per-mailbox storage limitation and who also has a delegate defined with Editor permissions for Calendar and Tasks , the sender...
•Default POP3 line-wrap set to 72 characters
When you receive a message from a Microsoft Exchange Server computer using the POP3 Internet Protocol, the message text may be wrapped after 72 characters. This behavior can be observed when the Message Encoding is set to MIME and the "Provide...
•Default IMAP4 line-wrap set to 72 characters
When you receive a message from an Exchange Server computer using the Internet Message Access Protocol, Version 4rev1 (IMAP4) Internet Protocol, the message text may wrap after 72 characters. This problem occurs when Message Encoding is set to...
•ISDN line makes connection to remote WAN sites every 15 minutes
If you have two remote sites in your domain that are connected by an Integrated Services Digital Network (ISDN) line, and the ISDN line is scheduled to make a connection one time per hour, the line may instead make a connection every 15 minutes.
•Error message when you use Exchange System Manager to access the Templates tab or the MS-DOS Templates tab in a template's properties: "An Invalid ADSI pathname was passed"
Describes a problem in which Exchange System Manager returns an error message when it accesses the Templates tab or MS-DOS Templates tab of the Properties dialog box for a template. Provides a hotfix and a workaround.
•You cannot copy or move a message that is formatted in Unicode to the Inbox in an organization that is running Exchange Server 2003 SP1
Describes a problem that occurs when you are using a DBCS-based language and you try to move or copy messages stored in the Unicode format in Exchange Server 2003 SP1. A hotfix is available.
•The Inetinfo.exe process stops responding when you enable the Envelope Journaling feature in an organization that is running Exchange Server 2003 SP2
Provides a hotfix to fix an issue in which the Inetinfo.exe process stops responding unexpectedly on an Exchange Server 2003 SP2 server.
•The subject and body of an NDR message are displayed incorrectly when you receive an NDR message by using the German version of Exchange Server 2003
Describes a problem in which a "0D 0A 09" character sequence is inserted in the subject of the NDR when you receive an NDR message by using a German e-mail client. Provides a hotfix.
•FIX: An NDR message that has an embedded TNEF attachment cannot be delivered on a server that is running Exchange Server 2003
Fixes an issue that occurs when an NDR message includes a TNEF attachment. If Exchange Server 2003 parses this NDR message incorrectly, the damaged NDR message cannot be delivered.
•The LegacyExchangeDN attribute for two user accounts may be the same in Exchange Server 2003 SP2
Describes a problem in which the LegacyExchangeDN attribute of users may be duplicated when user accounts have the number sign (#) in the alias in Exchange Server 2003 Service Pack 2.
•Many transaction log files are generated in a short time on an Exchange 2003 Service Pack 2 server
Describes a problem in which many transaction log files are generated in a short time on a server that is running Exchange 2003 Service Pack 2. You may also experience other symptoms. Provides a hotfix to resolve this problem.
Last Review : September 12, 2006
Contact a Support Professional by Email, Online, or Phone.

Need More Help?

Contact a Support Professional by Email, Online, or Phone.

© 2006 Microsoft Corporation. All rights reserved. Terms of Use |Trademarks |Privacy Statement