IIS 500.19 with 0x80070005 The requested page cannot be accessed because the related configuration data for the page is invalid error

🚀 Solving the IIS 500.19 Error with 0x80070005 🚀

So, you're trying to upload your own ASP.NET website on IIS using IIS Manager, but you're encountering a frustrating error: "HTTP Error 500.19 - Internal Server Error. The requested page cannot be accessed because the related configuration data for the page is invalid." 😫

On top of that, you've searched high and low for a solution to this error, but none of the suggested fixes have worked for you. Double 😫

Well, fear not! I'm here to guide you through the most common issues that cause this error and provide you with easy solutions on how to fix them. Let's dive in, shall we? 💪

Possible Cause: Insufficient Permissions 👮‍♂️

The error message itself gives us a hint: "Cannot read configuration file due to insufficient permissions." 🤔 This suggests that the IUSR account, which is responsible for accessing your web.config file, doesn't have the necessary permissions.

Solution: Grant Sufficient Permissions 🔐

To resolve this issue, follow these steps:

1. Open Windows Explorer and navigate to the location of your web.config file. In this case, it's "\\?\C:\Users\Yasso\Documents\Visual Studio 2008\WebSites\WebSite5\web.config".

2. Right-click on the web.config file and select "Properties."

3. In the Properties window, go to the "Security" tab.

4. Click on the "Edit" button to modify the permissions.

5. In the Permissions window, click on the "Add" button to add a new user.

6. In the "Enter the object names to select" field, type "IUSR" and click "Check Names." If it finds a match, click "OK" to select it.

7. Back in the Permissions window, make sure the newly added IUSR account has "Read & execute" permissions. If not, click on the "Full Control" checkbox to grant it.

8. Click "OK" to save the changes and exit the Permissions window.

9. Try accessing your website again in IIS. The error should be resolved now. 🎉

Another Common Cause: Incorrect Application Pool Identity 🏭

If the above solution didn't work for you, there's another common cause that might be at play: an incorrect Application Pool Identity. The Application Pool Identity is responsible for running your website's application pool, and if it's not set properly, it can lead to this error.

Solution: Set Correct Application Pool Identity 👤

To make sure your Application Pool Identity is set correctly, follow these steps:

1. Open IIS Manager.

2. Expand the "Sites" node and select your website.

3. On the right-hand side, double-click on "Advanced Settings" under the "Actions" panel.

4. In the Advanced Settings window, locate the "Application Pool" property and click on the ellipsis button next to it.

5. In the Application Pool dialog, make note of the selected application pool.

6. Close the Application Pool dialog and go back to the main IIS Manager window.

7. In the Connections pane on the left-hand side, select "Application Pools."

8. Locate the application pool you noted in step 5 and right-click on it.

9. Select "Advanced Settings" from the context menu.

10. In the Advanced Settings window, find the "Identity" property and ensure it is set to an account that has the necessary permissions to access the web.config file.

11. Restart the IIS server or recycle the application pool for the changes to take effect.

12. Test your website again to see if the error is gone. 🎉

🙌 Now You're in Control! 🙌

With the solutions provided above, you should be able to overcome the IIS 500.19 error with the 0x80070005 code. Make sure to follow the steps meticulously, and you'll have your ASP.NET website up and running smoothly on IIS in no time. 💃

If you're still facing issues or have any other questions, feel free to leave a comment below. I'll be more than happy to assist you further. Happy coding! 💻