Common data access page deployment Errors

Article translations Article translations
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).

Expand all | Collapse all

SUMMARY

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.
    This page has been saved to a web server that is not configured to allow connections to the datasource.
    Could not find file.
    The Microsoft Jet Database engine cannot open the file '<PathToFile>'. It is already opened exclusively by another user, or you need permissions to view its data.
    The UseRemoteProvider property is supported only for pages saved to Web folders.
    Safety settings on this computer prohibit accessing a data source on another domain.
    Could not use "; file already in use.
    Cannot start your application. The Workgroup information file is missing or opened exclusively by another user.

MORE INFORMATION

"Internet Server Error" Error

This 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:
  • Execute Permissions On Microsoft Internet Information Server 4.0 (IIS), the permissions of the MSADC virtual directory must be set to Execute (Including Script). On Microsoft Internet Information Server 5.0, the permissions of the MSADC virtual directory must be set to Scripts and Executables.

    For additional information about troubleshooting Remote Data Services, click the article number below to view the article in the Microsoft Knowledge Base:
    251122 Troubleshooting Common Problems with Remote Data Services
  • On Microsoft Internet Information Server 4.0 (IIS), the permissions of the MSADC virtual directory must be set to Default Web Site If your data access pages are running under a site other than the Default Web Site in IIS, you must have a separate MSADC virtual directory for your Web site.

    For additional information about configuring RDS for a virtual server, click the article number below to view the article in the Microsoft Knowledge Base:
    184606 HOWTO: Use RDS from an IIS 4.0 Virtual Server
  • On Microsoft Internet Information Server 4.0 (IIS), the permissions of the MSADC virtual directory must be set to IP Address and Domain Name Restrictions On a clean installation of Microsoft Windows 2000, all IP addresses are denied access to the MSADC virtual directory.

    For additional information about configuring RDS on Windows 2000, click the article number below to view the article in the Microsoft Knowledge Base:
    250536 HOWTO: Configure RDS for Windows 2000
174518 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" Error

This 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:
230680 INFO: Working with RDS Handlers
  1. On the Web server, open the msdfmap.ini file in WordPad. This file is in the WINNT folder.
  2. In the "[connect default]" section, change
    Access=NoAccess
    					
    to read:
    Access=ReadWrite
    					
    IMPORTANT: This will allow read/write connections to all data connections on the server through RDS.

  3. to read: In the [sql default] section, change:
    sql=" "
    					
    to read:
    ;sql=" "
    					
    IMPORTANT: This allows any SQL statement to be executed against any data source on the Web server through RDS.

  4. to read: Save and close the msdfmap.ini file.

"Could not find file errors" Error

These errors include the following messages:
  • Could not find file "<PathToDatabase>".
    Not a valid file name.
    Microsoft Office Web Components could not open the database "<PathToDatabase>".
NOTE: Before you receive these error messages, you may first receive the following error message:
Data provider could not be initialized.
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:
304324 HOW TO: Change the connection string for an Access 2002 data access page
For 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:
304521 ACC2002: Supported providers for data access pages
When 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:
  1. Start Microsoft Access, and then open the data access page that you are deploying in Design view.
  2. On the View menu, click Properties to view the property sheet if it is not already visible.
  3. On the Edit menu, click Select Page to view the properties for the page.
  4. On the Data tab, set the UseRemoteProvider property to True.
  5. Close and then save the data access page.IMPORTANT: As soon as you set the UseRemoteProvider property to True, data can no longer be viewed when the page is opened from the file system. Do not set the property until you are ready to publish the page from a properly configured IIS Web server.

"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" Error

This 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:
299373 ACC2002: Introduction to .ldb Files
You may also receive this error if the database is opened exclusively by another user.

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" Error

You 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:
http://ServerName/PageName.htm

"Safety settings on this computer prohibit accessing a data source on another domain" Error

This 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" Error

You 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" Error

This 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:
  1. Start Microsoft Access, and then open the data access page that you are deploying in Design view.
  2. Right-click the page, and then click Page Properties.
  3. On the Data tab, click the Build (...) button to the right of the ConnectionString property.
  4. On the All tab, change the Jet OLEDB:System database property to the UNC location for the workgroup file.
When you are using three-tier deployment, put the workgroup file with the database and make sure that the Jet OLEDB:System database property points to the correct path of the .mdw file.

REFERENCES

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:
291783 ACC2002: How to Deploy Data Access Pages over the Internet
For 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://msdn2.microsoft.com/en-us/library/aa139939(office.10).aspx

Properties

Article ID: 300699 - Last Review: March 27, 2007 - Revision: 4.7
APPLIES TO
  • Microsoft Office Access 2003
  • Microsoft Access 2002 Standard Edition
Keywords: 
kbconfig kbhowto KB300699

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com