BUG: Xp_sendmail with Large Row Results May Cause Error 35909

Last reviewed: June 10, 1997
Article ID: Q169641
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16962 (6.5)

SYMPTOMS

Running xp_sendmail can cause SQLMail to get an exception error and stop if all of the following conditions are true:

  • One of the rows returns more that 2,000 bytes.
  • The @width parameter is set greater than 2,000
  • The results are not attached as a file.

WORKAROUND

To work around this problem, do either of the following:

  • Use the parameter @attach_results=true.

    -or-

  • Do not set @width greater than 2000.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The following is the error that the client process will receive:

   Msg 35909, Level 18, State 1
   EXCEPTION error encountered in MAPI extended procedures, exception error
   code = 0xC0000005

The following are the errors from the SQL Server errorlog:

   ods      Error : 18009, Severity: 18, State: 1
   ods      EXCEPTION error encountered in MAPI extended procedures,
   exception error code = 0xC0000005
   ods      Stopped SQL Mail session.


Additional query words: mapi mail sp_processmail 18009
Keywords : kbbug6.50 kbusage SSrvGen SSrvGPF SSrvStProc
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.