A set of old Asp+access's resurrection notes

Because of the company's business needs, a WINSERVER2008R2 server in the computer room to revive a set of asp+access old information system, considering that the server itself has a asp+mssql system has been running normal, presumably should be easy to fix, Immediately built a two-level directory, the full set of related files copied in, configured under the relevant directory permissions to run, the system has been repeatedly and firmly reported the same error:

Error Number: 2147467259
Error Description: Unspecified error
Error Source: Microsoft JET Database Engine

The following troubleshooting is done in turn:

1. The ASP Site Access database is located in the directory and related to the Special Config directory to give users read and write and modify permissions, even during debugging, once the entire station gave everyone full control, no results;

2. To set the parent path to enable iis--asp:
   

3. To set up a 32-bit application that runs the site's program pool:
   

4. Permission permissions, or permissions issues:
   Needless to say: The C:\Windows\temp directory requires IIS_IUSRS full permissions, and another argument is: IIS7 32-bit MS Jet engine temp directory location: C:\Windows\ServiceProfiles\NetworkService \AppData\Local\Temp also authorized to deal with it.

Later at once accidentally clicked:

Unable to verify access to the Web site's local physical path?

The following settings are immediately made:

Here again to try: Asp+access has been able to access the normal, the problem is solved perfectly.

Summary: No change before this setting, why the previous set of Asp+mssql has been running normally, but this set of asp+access will not work? The official explanations are as follows:

The server is configured to use pass-through authentication with the built-in account to access the specified physical path. However, IIS Manager cannot verify that this built-in account has access rights. Make sure that the application pool identity has read access to the physical path. If this server is joined to a domain and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has read access to the physical path. Then test the settings again.

A set of old Asp+access's resurrection notes