Comments by ryoaska (Top 2 by date)

ryoaska 20-Jul-10 22:42pm View

I am testing it directly from the actual site, not from the VS development server (which from what I've ready uses some version of the mini web server 'matrix', and is not actually using iis). When I tried to run the project from the debug server it worked fine, but when I browse to the page on the actual site (i use the actual URL of the website , not localhost because I have multiple sites on the same ip using host headers) I get the error messaeg I pasted above. Since debugging in VS is giving me that "network name is invalid" error, I can't get to a point to check the status bar there (I think?). I'll look into that further.

when I created the project I did create it as a .net 2.0 project though. I'll see if I can find anything more specific in the project properties.

Thanks for the link, I'll check that out too.

ryoaska 20-Jul-10 18:31pm View

what do you need to change in IIS? I did change it in VS but I didn't know I could change it in iis. I'm thinking it's something besides that though, because if it was only about debugging, at least other asp.net pages that previously worked would still work... it seems like it's some kind of setting that could have gotten changed by installing something else...idk. Getting VS debugging working is just the only way I can think of to track down what the real problem is here... If there's any other way I can debug this, I would really love to know

also the original error message I included got messed up.. it looks as below. I tried both edits to the web.config file and neither of those changed anything.
------------------------------------------------------------------------------
Runtime Error 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.

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".

<configuration>
<system.web>
<customerrors mode="Off">

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customerrors> configuration tag to point to a custom error page URL.

<configuration>
<system.web>
<customerrors mode="RemoteOnly" defaultredirect="mycustompage.htm">