Microsoft KB Archive/308777

From BetaArchive Wiki
Knowledge Base


Article ID: 308777

Article Last Modified on 10/17/2003



APPLIES TO

  • Microsoft SQL Server 2000 Standard Edition



This article was previously published under Q308777

BUG #: 354183 (SHILOH_BUGS)

SYMPTOMS

If you assign a SQL Mail MAPI Profile name that is longer than 132 characters in Enterprise Manager, a buffer overrun occurs and garbage data appears after the MAPI Profile name.

CAUSE

Enterprise Manager uses a buffer of 132 characters to hold the MAPI Profile name but the text box only allows 255 characters. Thus, the user interface lets you enter a Profile name that is longer than the buffer that holds the Profile name, which results in a buffer overrun.

Furthermore, Enterprise Manager allows you to enter a MAPI Profile name that is longer than 64 characters, although the maximum length of a MAPI Profile name is only 64 characters.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


WORKAROUND

To work around this problem, limit the size of the SQL Mail Profile name to 64 characters, which is the maximum length allowed for MAPI Profile names.

STATUS

Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

MORE INFORMATION

You cannot create a MAPI profile that is longer than 64 characters. However, SQL Enterprise Manager does allow you to enter up to 255 characters for the profile name in the properties of SQLMail. If you enter a name that is larger than 64 characters, SQLMail will not start and the xp_startmail extended stored procedure fails with this error message:

Server: Msg 18025, Level 16, State 1, Line 0
xp_startmail: failed with mail error 0x80070057


Additional query words: Junk garbage

Keywords: kbbug kbfix KB308777