Article ID: 926939 - View products that this article applies to.
Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect the computer.
Consider the following scenario. On a Web server that is running Microsoft Internet Information Services (IIS) 7.0, you host an active server page (ASP) that connects to a database. The ASP page data provider is the Microsoft.Jet.OLEDB.4.0 data provider. The ASP page data source is a Microsoft Access database (.mdb) file. In this scenario, you may receive the following error message when you request the ASP page:
Note You will encounter a similar error message when you use both of the following:
Microsoft JET Database Engine error '80004005'
This problem may occur if IIS 7.0 is configured to load the current user profile for an application pool identity. This may cause compatibility issues with legacy ASP-based applications and ADO-based applications because the current user may not have sufficient permissions to write to the temporary directory.
To resolve this problem, you must add the correct access control entries to the temporary directory for the process identity. To do this, follow the steps for your operating system.
Windows Server 2008 and Windows Vista with SP1 or later versions
To resolve this problem on an IIS 7.0 Web server that is running on Windows Server 2008 or Windows Vista with SP1 or later versions, follow these steps:
To resolve this problem on an IIS 7.0 Web server that is running on Windows Vista RTM, follow these steps:
Note By default on Windows Vista RTM, the process identity is NetworkService, and the temporary directory is %windir%\ServiceProfiles\NetworkService\AppData\Local\Temp.
To resolve this problem, use the method that is described in the "Resolution" section. However, if you do not want to add access control entries to the temporary directory for the process identity, you can work around the problem by disabling the loadUserProfile property for the application pool. When this property is disabled, IIS 7.0 does not load the current user profile for the application pool.
Important If you disable this property, a security risk may be created. Make sure that you understand and evaluate the risks before you implement this workaround.
To disable the loadUserProfile property for the application pool, modify the ApplicationHost.config file. The following example demonstrates how to do this.
For more information about temporary directory permissions when you run a database query in an ASP page, click the following article number to view the article in the Microsoft Knowledge Base:
315456Using Classic ASP with Microsoft Access Databases on IIS 7.0 and IIS 7.5
(http://support.microsoft.com/kb/315456/ )You receive a database results error message when you connect to database from an ASP page in FrontPage