Err Msg: An Error Occurred Accessing the Security-Settings File

Last reviewed: September 4, 1997
Article ID: Q168960
The information in this article applies to:
  • Microsoft Network Client version 3.0 for MS-DOS

SYMPTOMS

After installing the Network Client version 3.0 for MS-DOS and starting the computer, you may get these messages while running Autoexec.bat, typically after NET START or NET INITIALIZE is run:

  • Error 2: The specified file was not found.

    -or-

  • An error occurred accessing the security-settings file.

Networking functionality will be lost. System settings in System.ini and Protocol.ini are correct, as are settings in Config.sys and Autoexec.bat.

CAUSE

During setup, the file Wfwsys.cfg is copied to your setup directory (typically, C:\NET). The Shares.pwl file is built using security information that is tied to the Wfwsys.cfg file. If the Wfwsys.cfg file is damaged or missing, the network will not start, and you will receive these error messages.

RESOLUTION

Copy the Wfwsys.cfg file from the clients\msclient\netsetup directory on the Windows NT Server compact disc to your network client installation directory (for example, C:\NET) and delete the existing Shares.pwl file. When you restart the computer, a new Shares.pwl file will be created using the Wfwsys.cfg file.

If you replace the Wfwsys.cfg file without deleting the Shares.pwl file, you will receive an ACCESS DENIED message during system startup.

Keywords          : ntdomain kbnetwork kbsetup
Version           : 3.0
Platform          : MS-DOS
Hardware          : x86
Issue type        : kbprb


================================================================================


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