FoxPro database over network

  •  I have a report that needs to access a foxpro database that is located on

    another server on the network.  The report works fine when building it but once it is deployed to the reportserver the database

    cannot be accessed using either an OLE or ODBC connection.

    The initial error message for ODBC is:

    Cannot create a connection to data source 'FoxPro'.

    (rsErrorOpeningConnection) ERROR [S1000] [Microsoft][ODBC Visual FoxPro

    Driver]Cannot open file \\server\data\sapphire.dbc. ERROR [IM006]

    [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed ERROR

    [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the

    version of ODBC behavior that the application requested (see SQLSetEnvAttr).

    If I specify user credentials in the datasource properties, I receive the

    following error:

    Query execution failed for data set 'FoxPro'. (rsErrorExecutingCommand)

    ERROR [S1000] [Microsoft][ODBC Visual FoxPro Driver]Cannot open file

    \\server\data\spjobs.dbf.

    This is the table the query is being executed on.  NTFileMon shows that the

    process w3wp.exe has successfully read the sapphire.dbc file that failed in

    the first instance but cannot open the spjobs.dbf file.

    Similar errors occur using OLE.

    I have tried giving full permissions for the files and network share for

    everyone but this makes no difference.  If the database is located locally there is no problem - it is only when it is accessed via the network.

    Does anyone have any experience in

    regards,

    Chris

  • What version of MDAC is running on the server?  Is it the same as your development machine?

    You might try using an admin account just to verify if it works.

    FYI: Here's the most recent version of Foxpro OLE DB

    http://msdn.microsoft.com/vfoxpro/downloads/updates/default.aspx

    I hope this is of some help to you.

     

  • Thanks for the help, I have fixed the problem which was due to IIS using NTLM authentication which fails on the second hop to the foxpro server.  Switching to kerberos authentication solved everything.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply