ACC1x: "Invalid Path" Error Message on Network Installation

Last reviewed: May 7, 1997
Article ID: Q109316
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SUMMARY

After performing a network installation of Microsoft Access using the SETUP /A command to set up the server, and the SETUP /N command to set up the workstation, you receive an "Invalid Path" error message when you try to start Microsoft Access.

MORE INFORMATION

During the installation process Microsoft Access checks to see what type of network you are running. If the network type is Microsoft LanMan, Windows for Workgroups, or WindowsNT, Microsoft Access will write the paths of necessary files in the MSACCESS.INI file using the uniform naming convention (UNC). With other network types, the paths of necessary files are written using drive letter references.

In either case, the server name must be 11 characters or less in length, and must use no more than three characters as an extension. This is standard MS-DOS naming convention.

Filing systems like WindowsNT's NTFS, OS/2's HPFS, UNIX's POSIX, and Novell's Netware use naming conventions that do not follow standard MS-DOS naming conventions. This can cause the error message stated above when Microsoft Access tries to locate a server that is identified in the MSACCESS.INI file.

REFERENCES

Microsoft Access "User's Guide," version 1.1, Appendix D, "Setting Up Microsoft Access on a Network"


Keywords : kberrmsg kbsetup StpNet
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbinfo


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