FIX: xp_sendmail Unable to Login to SQL Server Version 4.21a

Last reviewed: April 30, 1997
Article ID: Q132346
The information in this article applies to:
  • Microsoft SQL Server, version 4.21a
BUG# NT: 9139 (4.21a)

SYMPTOMS

When you use the xp_sendmail extended stored procedure to send a mail message containing the results of a query, you receive Message 17969:

   Unable to login to SQL Server

This problem can occur if all of the following conditions are true:
  • SQL Server is running mixed mode security.
  • The client running xp_sendmail has logged in using a trusted connection with 'sa' privilege.
  • The 'sa' login id has a non-null password.

CAUSE

In order to run a query, the xp_sendmail procedure must log back in to SQL Server. This 'loopback login' can fail under the conditions listed in the "Symptoms" section above.

WORKAROUND

You can use any of the following options to avoid this problem:

  • Log in to SQL Server using a trusted connection with user (non-sa) privilege when you run xp_sendmail.
  • Log in using a non-trusted connection by supplying 'sa' as the login id, along with the appropriate password.
  • Set up SQL Server to use integrated rather than mixed mode security.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.21a. This problem was corrected in SQL Server version 6.0. For more information, contact your primary support provider.


Additional query words: sql6 sqlmail mapi sqlmapi
Keywords : kbbug4.21a kbfix6.00 kbprg SSrvStProc
Version : 4.21 4.21a 6.0
Platform : WINDOWS
Issue type : kberrmsg


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: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.