Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You receive an error message when you try locate an ASP database result page that was created in FrontPage


View products that this article applies to.

Symptoms

When you try to locate an Active Server Page (ASP) database results page that was created in Microsoft FrontPage, you may receive an error message that is similar to one of the following:

Error #1:
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object
/_fpclass/fpdbrgn1.inc, line 99
Note This error message may be followed by a description of why the resource was inaccessible.

Error #2:
Execute Access Denied
This Virtual Directory does not allow objects to be executed.
Error #3:
Database Results Error
The database connection named 'Sample' is undefined.

This problem can occur if:

* the connection has been removed from the web.
* the file 'global.asa' is missing or contains errors.
* the root folder does not have Scripting permissions enabled.
* the web is not marked as an Application Root.

↑ Back to the top


Cause

This problem may occur if the following respective conditions are true:

Error #1:

The NTFS file systems permissions are defined incorrectly for the %ProgramFiles%\Common Files\System folder.

Error #2:

The virtual directory that you are connecting to is not marked as an ASP program.

Error #3:

The virtual directory that you are connecting to does not have at least Script permissions defined in the Microsoft Internet Information Service (IIS) settings.

↑ Back to the top


Resolution

Note We strongly recommend that you upgrade to Microsoft Internet Information Services (IIS) 6.0 running on Microsoft Windows Server 2003. IIS 6.0 helps increase Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site: To resolve this problem, use the method appropriate to the error message you are receiving:

Error #1:

Reset the NTFS permisions on the "%ProgramFiles%\Common Files\System" folder. To do this, follow these steps:
  1. Right-click Start, and then click Open to start Microsoft Windows Explorer.
  2. Expand the %ProgramFiles%\Common Files\System folder in Folders view.
  3. Right-click the folder, and then click Properties.
  4. Click the Security tab.
  5. Add Everyone to the exisiting permissions with at least Read permissions and apply these new settings to all files and subfolders.
  6. Click OK.
Error #2:

Mark the folder as an Application Root. To do this, follow these steps:
  1. Start Internet Services Manager. To do this, follow the steps for your version of IIS.
    • For IIS 5.0, for IIS 5.1, and for IIS 6.0:
      1. Click Start, and then click Run.
      2. Type %windir%\system32\inetsrv\inetmgr.exe in the Open box, and then click OK.
    • For IIS 4.0:
      1. Click Start, point to Programs, and then click Windows NT 4.0 Option Pack.
      2. Click Microsoft Internet Information Server.
      3. Click Internet Service Manager.
  2. Expand the path to the folder in Tree view.
  3. Right-click the folder, and then click Properties.
  4. Click the Directory tab or click the Home Directory tab.
  5. Click Create.
  6. Click OK.
Error #3:

Configure the folder to have at least Script permissions. To do this, follow these steps:
  1. Start Internet Services Manager. To do this, follow the steps for your version of IIS:
    • For IIS 5.0, for IIS 5.1, and for IIS 6.0:
      1. Click Start, and then click Run.
      2. Type %windir%\system32\inetsrv\inetmgr.exe in the Open box, and then click OK.
    • For IIS 4.0:
      1. Click Start, point to Programs, and then click Windows NT 4.0 Option Pack.
      2. Click Microsoft Internet Information Server.
      3. Click Internet Service Manager.
  2. Expand the path to the folder in the Tree view.
  3. Right-click the folder, and then click Properties.
  4. Click the Directory tab or click the Home Directory tab.
  5. Select Scripts only for the execute permissions.
  6. Click OK.

↑ Back to the top


More information

If you are trying to gain access to a Microsoft Access database, make sure that you have established the appropriate permissions. When a user tries to perform an Internet Database Connector (IDC) or ActiveX Data Objects (ADO) query, the query is run in context of the authenticated Web user. Typically, you (the FrontPage Web developer) might grant the directory permissions listed later in this article to an anonymous user or to the authenticated Microsoft Windows NT user account. (By default, the anonymous user is IUSR_machine-name.)

When you apply these permissions, apply them to all existing files unless otherwise noted.

When you set permissions for the IUSR account, you need to add all user accounts that need to be authenticated on the Microsoft Internet Information Server (IIS) computer.

The directories identified in the sixth and seventh bullets that follow are located by default in the Program Files/Common Files/System directory and are needed only for ASP and ADO queries.

Typical permissions for IUSR are as follows:
  • Read permission to the root directory of the drive on which ASP is installed.
  • Write permission to the Windows NT directory in Windows NT, or to the WinNT directory in Windows 2000.
  • Read permission to the System32 directory.
  • Read permission to the Inetsrv directory.
  • Read permission to the InetPub (or content directory).
  • Read permission to the OLE DB directory.
  • Read permission to the ADO directory.
  • Change permissions to the database file and directories.
Note The Microsoft Jet database engine uses the System Temp and Tmp environment variables to specify the location of temporary files that are created during Jet operations. By default, these environment variables are defined for users and are not system-wide settings. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
315456 You receive a database results error when you connect to database from an ASP page

↑ Back to the top


References

For more information about how to troubleshoot ASP/IIS errors when you work with FrontPage database connectivity features, click the following article numbers to view the articles in the Microsoft Knowledge Base:
201740 Cannot create object error when browsing ASP pages
219170 Error browsing database results pages after publishing from disk-based Web
315453 "Server object error 'ASP 0177: 800401f3'" error message when you access an ASP database results page in FrontPage 2000
315454 "Server object error 'ASP 0178 : 80070005'" error message when you attempt to connect to a database results page created in FrontPage
315456 You receive a database results error message when you connect to database from an ASP page in FrontPage
For more information about how to troubleshoot IIS permissions, click the following article numbers to view the articles in the Microsoft Knowledge Base:
185874 How to troubleshoot permissions in Internet Information Server 4.0
309051 How to troubleshoot ASP in IIS 5.0
For additional information about virtual directories and application objects, see the Internet Information Services Documentation on your Web server. To view this documentation, follow these steps:
  1. Click Start, click Run, type http://localhost/iishelp in the Open box, and then click OK.
  2. On the IIS Documentation page, click the Index tab, type virtual directory, select the subtopic that you want, and then click Display.

↑ Back to the top


Keywords: KB265161, kbprb, kbpermissions, kbasp, kbdatabase, kbscript

↑ Back to the top

Article Info
Article ID : 265161
Revision : 10
Created on : 1/27/2007
Published on : 1/27/2007
Exists online : False
Views : 350