Beginner: ASP.net Access database using OLE DB adapter The various connection exceptions occur

It's also a common problem, especially under WIN2003, and it's often asked.
A connection exception is usually caused by disk permissions, and the system default ASP.net account has minimal privileges for the NTSF partition and may cause an access exception. The solution is to fix the appropriate permissions in the system.
Another: The exclusive access method specified in the connection string may also cause a connection exception. This situation can only be fixed by fixing the connection string.
Such as:
Conx. ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0; password=; User id=admin;data source= "+ Server.MapPath (" Data elegant holiday. mdb ") +"; ";
Can
Attach MSDN about creating custom accounts to run ASP. NET articles to facilitate understanding of security deployment asp.net projects.
----------------------------------------------------------------------------------
How to create a custom account to run ASP.net
Microsoft Corporation
Goal
This module is used to:
& #8226; Create a least privileged account with sufficient permissions to run the ASP.net application correctly.
& #8226; Configure ASP.net to run using a custom least-privileged account.
Apply to:
This module applies to the following products and technologies:
& #8226; Microsoft_ Windows_ XP or Windows Server (with Service Pack 3) and later operating systems
& #8226; Microsoft. NET Framework version 1.0 (with Service Pack 2) and later
& #8226; Internet Information Services (IIS) 5.0 or 6.0 (only if you are using IIS 5.0 isolation mode)
How to use this module
Use this module to the fullest extent:
& #8226; Must have experience developing asp.net Web applications and be familiar with the purpose and structure of machine.config files.
& #8226; You must have experience using Windows management tools to create and manage stand-alone or domain-based Windows user accounts.
& #8226; Read the module "asp.net security". This module will provide you with more information about how ASP.net security works, how the worker process identifies the impact on the permissions of an executing application, and how you can use impersonation to easily grant the appropriate permission level to users of the Web application. asp.net

Summary
By default, each ASP.net worker process runs in the context of the least privileged account named ASPNET. If the ASP.net application is deployed on a domain-based server, or if you need to access resources on a remote server, you can simplify management by configuring ASP.net to run in the context of different accounts.
This module describes how to configure ASP.net to run in the context of a custom local or domain account, and describes the permissions that are assigned to this account to work properly.