The solution to the failure to access the IIS metadatabase has not been used for IIS for a long time. After reading the solution today, it seems that there is a problem with IIS, So I Unmount and reinstall it, I did not expect this unload to take more than two hours to solve a series of problems. The first is the permission problem. The files in my new virtual directory said that I have no access permission, then Baidu said it was about to raise the right: the specific steps for raising the right of www.2cto.com are as follows: the virtual directory you want to escalate permissions to -----> all tasks -----> permission wizard -------> next ------> inherit all security settings ------> next ------> replace all directories and file access permissions (recommended) click "complete permission" to solve the problem. Next, let's talk about the solution to "failed to access the iis metadatabase": 1. Click "start"> "run ". 2. Enter www.2cto.com "C: \ WINDOWS \ Microsoft. NET \ Framework \ v2.0.50727 \ aspnet_regiis.exe-I" in the "run" column, and click "OK. 3. The displayed cmd window displays "start to install ASP. net xxx" and other content. Wait until the window is closed automatically. Now, the problem is solved. If the problem persists, refer to the following article. Source: Internet. ---------------------------------- Install VS2005 and then install IIS. As a result, a small problem occurs when accessing the IIS metadatabase. This may be due to a problem in sequence. 1. Open CMD and go to C: \ WINDOWS \ Microsoft. NET \ Framework \ v2.0.50727 2. Enter aspnet_regiis.exe-I www.2cto.com and wait a moment. The registration will solve the problem. Then there will be a "failed to create Mutex" problem solution: 1. Close your VS2005 first. 2. Open C: \ WINDOWS \ Microsoft. NET \ Framework \ v2.0.50727 \ Temporary ASP. NET Files, find the directory of the program you just debugged, and delete it. 3. Disable the IIS server and restart it once. Www.2cto.com 4. Use IE to browse your program and solve the problem. Important Note: If you have installed Multiple clients, you can perform the aspnet_regiis.exe-I operation for each of them. This will solve the problem smoothly. I would like to dedicate it to my friends who have encountered this problem and hope to help you.