FIX: Remote Backups and xp_loginconfig Fail With Access Denied

 Last reviewed: May 2, 1997
Article ID: Q140332

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 12222 (6.00)

SYMPTOMS

Database dumps to remote devices and the xp_loginconfig extended stored procedure can fail with access denied errors if Microsoft SQL Server is using Per Seat licensing mode.

For database dumps, the client will get a 3201 error and the Windows NT Application log of the computer SQL Server is running on will contain the following event: 

   Event ID: 17055
   Type: Error
   Source: MSSQLServer
   Category: Kernel
   User: could be any user connected to SQL Server
   Description: Mesg 18204: dbswritecheck: Backup device '<device path
   and file>' failed to open, operating system error=5(Access is
   denied.)
When running xp_loginconfig, the query will return the message: 

   Unable to query SQL Server security information.

WORKAROUND

Switch the SQL Server security mode to mixed or integrated security.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.0. For more information, contact your primary support provider.

Additional query words: sql6 Security Impersonation Delegation
dbswritecheck winnt windows nt
Keywords : kbbug6.00 kbfix6.00.sp3 kbprg SSrvStProc
Version : 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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.