BUG: Transfer Manager May Not Transfer Some Logins

Last reviewed: April 30, 1997
Article ID: Q132276
The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 9831 (6.0)

SYMPTOMS

By design, SQL Transfer Manager does not maintain login passwords when you transfer logins between two Microsoft SQL Server version 6.0 databases. If, however, the encrypted password contains a single quotation mark character, the login may not be added.

STATUS

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

MORE INFORMATION

Transfer Manager builds a script of logins that are installed via SP_ADDLOGIN, and it pulls the information from syslogins on the source server. There is no function to decrypt the password, so the SP_ADDLOGIN procedure adds the login with the encrypted password. The system administrator (SA) needs to change the password to something more user friendly after the transfer.

In some cases, the encrypted password may contain a single quotation mark character (') which causes the SP_ADDLOGIN to fail with an incorrect syntax error. This error can cascade to SP_ADDUSER, object creation, and permission grants if the user owns any objects which are being transferred or the user has permissions that need to be added.


Additional query words: sql6 new user
Keywords : kbbug6.00 kbother SSrvStProc 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: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.