I have a report that needs to access a foxpro database that is located on
another server on the network. There are no issues in accessing the report
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. How can I get this report to work?
regards,
ChrisI am having similar problems with a link server (W2K to a VFP 6 dbc). The
error is
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Microsoft][ODBC Driver Manager] Driver's
SQLSetConnectAttr failed]
[OLE/DB provider returned message: [Microsoft][ODBC Visual FoxPro
Driver]Cannot open file \\myserver\myshare\folder\subfolder\mydbc.dbc.]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize
returned 0x80004005: ].
This is strangely intermittent. Some attempts work and some throw this
error. I repeat: this problem is intermittent. I'm beginning to suspect a
network problem, but don't have the faintest idea where to start
troubleshooting.
There are a number of posts in many different newsgroups concerning this
error, but no resolution. Would anyone from MS care to weigh in on this?
This issue is seriously hobbling my Biztalk EDI implementation, and the boss
wants a fix NOW.
TIA for your time and expertise.
--
Phil Hegedusich
Senior P/A
IIMAK
--
A skeleton walks into a bar and says, "I need a beer and a mop."
"Chris Diery" wrote:
> I have a report that needs to access a foxpro database that is located on
> another server on the network. There are no issues in accessing the report
> 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. How can I get this report to work?
> regards,
> Chris
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment