BUG: DMO BCP Fails with Mixed Security and Trusted Connection

 Last reviewed: February 9, 1998
Article ID: Q180711
The information in this article applies to:
  • Microsoft SQL Server version 6.5
BUG #: 17804 (SQL6.5)

SYMPTOMS

When you use SQL-DMO to perform a bulk copy operation with a forced trusted connection and SQL Server is running under mixed security, you will receive the error message 

   [SQL Server] Login failed
if the password of the specified login user is not null.

WORKAROUND

You can use any of the following methods to work around the problem.

  • Use integrated or standard security.

    -or-

  • Make a standard connection.

    -or-

  • Use Vbsql.ocx in place of SQL-DMO for a trusted bcp operation using mixed security.

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. 

Keywords          : kbbug6.50 SSrvDMO
Version           : Windows:6.5
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending

================================================================================

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