Error: Table is not accessible

Product:  BizInsight
Applies to:  MAS 90/200
Article Type:  Error 

Summary:
After dragging and dropping a BizInsight function into a worksheet, the user receives the following errors:

Error:  System.Data.SqlClient.SqlError:  OLE DB provider "MSDASQL" for linked server "mas90_xxxx" returned message "[ProvideX][ODBC Driver][FILEIO]Table is not accessible".
Error:  .Net SqlClient Data Provider:  Cannot execute the query "select ..... " against OLE DB provider "MSDASQL" for linked server "mas90_xxx". dataset [MAS90_Balances_All]

Details:
This error is known to occur in three circumstances:
1. The user’s Windows account does not have sufficient rights to the MAS 90/200  data files directory on the MAS 90/200 server and Windows authentication is being used with the Linked Server.
2. The Linked Servers have been created on a server other than where the MAS 90/200 data files reside.
3. The data files have been moved to a different location than what the ODBC data sources are pointed to.
4. The various paths to the MAS 90/200 data file locations specified in the ODBC data sources are using a UNC or mapped drive letter instead of the physical path to the MAS 90/200 data files.   For example, while the MAS 90/200 data files are on the same server as the Linked Servers, the paths specified in the ODBC data sources are either “\\servername\sharename\...” or “ [mapped drive letter]:\MAS90\....”

Resolution/Workaround:
To resolve this issue, do the following:
1. To confirm whether it is a user permissions issue, add a user account known to have sufficient rights to the MAS 90/200 data directory under the Security properties of the Linked Servers.  Then when logged in as that user to a workstation with BizInsight installed, open Excel and drag and drop a function.  If no error occurs, check the affected user’s rights to the MAS 90/200 data files directory and correct as necessary.  Read writes should be all that’s required.

2. If the Linked Servers have been created on a different server than where the MAS 90/200 data files reside, either recreate the Linked Servers on the server that hosts the MAS 90/200 data files or, if that is not possible, install SQL Server 2005 Express Edition on each client workstation and create the ODBC data sources and linked servers on each client workstation.

3. On the server where the Linked Servers have been created, go to Start > Control Panel > Administrative Tools > Data Sources (ODBC), select the ODBC data source for the company indicated in the error message and click Configure.  Check the paths in the following fields and confirm that they are the correct location of the data files:
    a. Database Directory field on the Basic tab
    b. Prefix for data files field on the Options tab
    c. Path to Views DLL field on the Options tab

4. On the server where the Linked Servers have been created, go to Start > Control Panel > Administrative Tools > Data Sources (ODBC), select the ODBC data source for the company indicated in the error message and click Configure.  Check the paths in the following fields and confirm that they are not using a UNC path or a mapped drive letter:
    a. Database Directory field on the Basic tab
    b. Prefix for data files field on the Options tab
    c. Path to Views DLL field on the Options tab

  If any of the paths are using a UNC or mapped drive letter, change the path so that it is using the full local drive path.

If the provided Resolution/Workaround does not resolve your issues, please contact BizNet Software Support for further assistance.