Schedule Service Cannot Access Redirected Netware Drives

 Last reviewed: August 28, 1996
Article ID: Q121073
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

Under Windows NT, batch files started by the AT command cannot access NetWare drives that were redirected using File Manager or Net Use at the command prompt. If the batch file attempts to access an existing NetWare drive, this message may appear: 

     Access is denied
This occurs even when the Schedule service was started under the same user account and password that was used to connect to the drive in File Manager.

CAUSE

Schedule service logs on as separate session and does not have access to the resources created by another session.

RESOLUTION

Have the batch file access the drives it needs using the Net Use command or a UNC name inside the batch file.

Users with Service Pack 2 installed have a problem using AT to start a batch file that contains a Net Use to a NetWare drive. This was corrected in the latest U.S. Service Pack for Windows NT and Windows NT Advanced Server version 3.1. See Knowledge Base article Q117791 for more information.

The NetWare product discussed here is manufactured by Novell a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional reference words: prodnt 3.10 gsnw csnw services cmd command
scheduler winat
KBCategory: kbnetwork
KBSubcategory: ntnetserv NTSrv

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