The reason may be that the .NET, ASPNET account (start ASPNET_WP.exe account) installed on the domain controller is not enough to create the permissions of the process. Please try the following methods: Method 1: Add the account ASPNET to the local administrator. Method 2: Go to the /winnt/microsoft.net/framework/Version/config directory, open the Machine.config file. Find the ProcessModel item, change the username to System or a permissible account you created yourself.
Method 3: Set the security of the site in IIS to only integrate Windows verification, then in Web.Config in the site
China plus one line:
The methods listed above may need to restart IIS services. The reason is when using Machine, the system will run the ASP.NET app with the ASPNET account, and the ASPNET account is not enough to permission on the domain controller. When using System, the system will run the ASP.NET app with the System account (with privilege to this machine). Only ASPNET account issues on the domain controller, why is Microsoft to know so, maybe it is a security factor, or a bug. As for the Window integration, access the database, the database will be accessed by the start-up account of the visitor process, so when the startup account is changed to SYSTEM, the native database should be accessed without the third step. When using a third method, the system will access the required resources in the actual identity of the visitor, not when the machine accesses in the same domain are required to enter the username and password.
