Article ID: 300699 - View products that this article applies to.
This article was previously published under Q300699
Advanced: Requires expert coding, interoperability, and multiuser skills.
This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).
With the introduction of data access pages in Access, you can now create data bound Web pages that can be viewed in Microsoft Internet Explorer 5 or later. By default, these pages try to bind to data on the client computer, making them ideal for Intranet solutions. However with special considerations, you can also successfully deploy data access pages over the Internet.
This article describes some of the common error messages that you may receive when you deploy data access pages over the Internet. This article describes the message, and then gives you troubleshooting steps.
The following error messages are described in this article:
"Internet Server Error" ErrorThis error message is related to the configuration of Remote Data Services (RDS) on the Web server, represented by the MSADC virtual directory. Possible causes of the error include:
(http://support.microsoft.com/kb/174518/EN-US/ )INFO: Errors Raised by Remote Data Service
"This page has been saved to a web server that is not configured to allow connections to the datasource" ErrorThis error is typically associated with the msdfmap.ini file on the Web server. The following steps allow any connection through RDS to data sources on the Web server. Use these steps for troubleshooting only.
For additional information about configuring the msdfmap.ini file, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/230680/EN-US/ )INFO: Working with RDS Handlers
"Could not find file errors" ErrorThese errors include the following messages:
These errors occur when the database cannot be found because of a data source that is not valid in the ConnectionString for the page, or when the UseRemoteProvider property is not configured properly. For additional information about valid connection strings for data access pages, click the following article number to view the article in the Microsoft Knowledge Base:
Data provider could not be initialized.
304324For additional information about which OLE DB providers can be used with data access pages, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/304324/ )HOW TO: Change the connection string for an Access 2002 data access page
304521When you set the UseRemoteProvider property to False, the data access page checks on the local computer for the data source. When you set the UseRemoteProvider property to True, the data access page checks the Web server for the data source. This is known as three-tier data access. To configure the UseRemoteProvider property, follow these steps:
(http://support.microsoft.com/kb/304521/ )ACC2002: Supported providers for data access pages
"The Microsoft Jet Database engine cannot open the file '<PathToFile>'. It is already opened exclusively by another user, or you need permissions to view it's data" ErrorThis error is typically caused when there are not enough file system permissions for either the folder in which the database resides, or for the database file itself. Users accessing your pages must have at least read, write, create, and delete permissions to work with the .ldb file that is created by the Microsoft Jet database engine.
For additional information about .ldb files, click the article number below to view the article in the Microsoft Knowledge Base:
299373You may also receive this error if the database is opened exclusively by another user.
(http://support.microsoft.com/kb/299373/EN-US/ )ACC2002: Introduction to .ldb Files
NOTE: This error does not occur with pages that are bound to SQL Server objects.
"The UseRemoteProvider property is supported only for pages saved to Web folders" ErrorYou receive this error when you open a data access page from a file system location after the UseRemoteProvider property has been set to True. When the UseRemoteProvider property is set to True, you must access the page through an Internet protocol such as HTTP. For example, if the page is stored in the wwwroot directory on the Web server, you access it as follows:
"Safety settings on this computer prohibit accessing a data source on another domain" ErrorThis error is caused by cross-domain settings on the local computer and occurs when accessing data across domains is not allowed. Note that "domain" refers to Internet/Intranet domain, and not to network domain.
"Could not use "; file already in use" ErrorYou receive this error when the database is opened exclusively by another user. This is common when browsing to a data access page after you create a new database. Close the database, and then refresh the page to remove the error.
"Cannot start your application. The workgroup information file is missing or opened exclusively by another user" ErrorThis error message occurs when a data access page cannot find the workgroup information file (.mdw). When you are using two-tier deployment, make sure that you put the workgroup file in a shared folder along with the database. Change the connection on the page to use the UNC path to the workgroup file as follows:
For additional information about how to deploy data access pages over the Internet, click the article number below to view the article in the Microsoft Knowledge Base:
291783For additional information about deploying data access pages and additional security concerns and configurations, please see the "Deploying Data Access Pages on the Internet or Your Intranet" white paper from MSDN online at the following Microsoft Web site:
(http://support.microsoft.com/kb/291783/EN-US/ )ACC2002: How to Deploy Data Access Pages over the Internet