Knowledge Base

BUG: DMO BCP Fails When Using Mixed Security and Trusted Connection

Article ID: 180711

Article Last Modified on 10/3/2003

Microsoft SQL Server 6.5 Standard Edition

This article was previously published under Q180711

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: kbbug kbpending kbsqlserv650bug KB180711