I am getting the following error when trying to open a aspx file in the website. I just created the website and have permissions set to allow anonymous by using the wizard.<BR><BR>Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. <BR><BR>Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".<BR><BR>I have the web.config setting as described that was copied from another application that work so I know that there is not a typo. I have reset IIS and the website. The error appears when I try to view the page locally on the server as well. What could be keeping the .net pages from running? <BR><BR>The .net page is:<BR><%@ Page Language="C#" Debug="true" %><BR><%@ Register TagPrefix="UserControl" TagName="Hdr1" Src=http://aspmessageboard.com/archive/index.php/"inc/hdr1.ascx" %><BR><%@ Register TagPrefix="UserControl" TagName="Hdr2" Src="inc/hdr2.ascx" %><BR><%@ Register TagPrefix="UserControl" TagName="Ftr1" Src="inc/ftr1.ascx" %><BR><BR><BR><UserControl:Hdr1 id="H1" runat="server" /><BR><UserControl:Hdr2 id="H2" runat="server" /><BR><p><asp:Label id="lblError" runat="server" /></p><BR><BR><BR><BR><p></p><BR><UserControl:Ftr1 id="F1" runat="server" /><BR><BR><BR>Thanks for your help<BR>on the web.config, you have to restart iis after making changes.<BR><BR>on the error, you need to change your TagPrefix= to something unique for each control.I restarted IIS and that did not have any affect. I also made the other change to the tagprefix and that did not have any affect. I don't think that matters because I have used that same code in other pages without errors.<BR>I am still getting the error. Does anyone have any other ideas. I keep thinking this must be a permissions error but I have reset the permissions numerous times with and without the wizard and it does not make any difference.