PRB: Accessing FoxPro table in ASP returns error 80040e14

Last reviewed: December 11, 1997
Article ID: Q175801
The information in this article applies to:
  • Microsoft Visual InterDev, version 1.0
  • Microsoft Visual FoxPro ODBC Driver, version 5.0

SYMPTOMS

The following error occurs when previewing an Active Server Pages (ASP) page that contains a connection to a Visual FoxPro table:

   'Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
   [Microsoft][ODBC Visual FoxPro Driver]File '<your .dbf filename>' does
   not exist.
   /<your web name>/<your .asp filename>, line <line number in .asp>

When you access the Visual FoxPro tables from within Visual InterDev through the Query Builder, the records return without error.

CAUSE

This error message can be caused by any of the following configuration scenarios:

  • The FoxPro database file is located on a machine other than the Internet Information Server (IIS) server. For example, your Web server with IIS is on "Server 1" and your .dbf files are on "Server 2."

    -and-

    IIS Server is configured to use NT Challenge/Response when accessing secured script files. For example, either by setting ACLS or selecting only the "NT Challenge/Response" check box in the "IIS Manager."

  • The FoxPro database file is located on a machine other than the machine running IIS.

    -and-

    IIS is configured to use the IUSR_computername account for anonymous access.

    -and-

    The script file being access is not secured and permits anonymous access.

    -and-

    The IUSR_computername is a local account and the same account/password does not exist on the remote machine (the machine that has the FoxPro database).

  • The FoxPro database file is located on a machine other than the machine running IIS.

    -and-

    IIS is configured to use Basic (Clear Text) authentication when accessing secured script files.

  • The FoxPro database files are located on the same server as the IIS

    -and-

    You are using UNC pathing to the .dbf files.

RESOLUTION

A possible workaround for this issue is to move the FoxPro database file to the server running IIS.

If it is not possible to move the FoxPro database file locally, the following workarounds can be used.

Use Basic Authentication instead of NT Challenge response when accessing secured scripts that query FoxPro database files located on another server. You can do this with the following:

  • Create another IUSR_computername account with the same password on the remote machine containing the FoxPro database file or specify DOMAIN\IUSR_computername for anonymous logon to IIS.
  • Grant access to the FoxPro database file or share for the authenticated user.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

When using NT Challenge/Response with IIS, the users credentials are created at the browser. The credentials are then sent to IIS. IIS cannot forward those credentials on to another server.

The connection is attempted, but there is no username specified when connecting to the remote machine, so the connection fails.

REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q166029
   TITLE     : PRB: Cannot Open File Unknown Using Access

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

   http://support.microsoft.com/support/vinterdev/


Additional query words: delegation
Keywords : VIServer odbcFox kberrmsg
Technology : kbInetDev odbc
Version : WINDOWS:1.0,5.0
Platform : WINDOWS
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: December 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.