BUG: Transfer Manager Encrypts Passwords Twice

Last reviewed: May 5, 1997
Article ID: Q154163

The information in this article applies to:

Microsoft SQL Server version 6.0

SYMPTOMS

In SQL Server 6.0, when logins are transferred from one server to another using Transfer Manager, the passwords are not transferred correctly. The password that gets stored on the destination server gets encrypted twice.

WORKAROUND

Use SEM to generate SQL scripts for login, and execute that on the destination server. This will transfer the password as NULL, and the users can change that next time they log on.

STATUS

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

MORE INFORMATION

In SQL Server 6.5, the transfer utility transfers NULL password, and the log file created contains a message such as:

   ::Warning::
   Transfer Status: Scripting Logins
   The login 'Albert' was scripted with a Null password for security
      reasons.

Additional query words: Transfer Manager
Keywords : kbnetwork SsrvTrans
Version : 6.0
Platform : WINDOWS

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