Hi I have noticed that when i go into the backend of my site there is a feature ( a link to a script) that when clicked generates "static html" for seo purposes pages - but on executing, it throws up a 500 internal error message. I have not executed the script to generate html static pages for a while, since before updating to 2008 server IIS7 but prior to upgrading it worked perfectly. Any pointers would be appreciated, as I have looked in the forum & read on the developers site to no-avail and as the rest of the site is working properly so I am assuming that it has something to do with the upgrade. I have set up error reporting on the script page (is this correct?) and it does generate a log file in a folder that I designated. The log file is pretty long and before I post it up here and since that I am not familiar with these files not sure what I am looking for, is there any info - from a security or other perspective that I should omit before posting the log file data for evaluation? I suspect that it will be a simple setting in IIs7 but I've read myself out on this one time to call in the experts! Many Thanks Nelly
SERVER ERROR 500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed. generic with no details Nelly
I would highly recommend using the Failed Request Tracing module in IIS: http://learn.iis.net/page.aspx/266/troubleshooting-failed-requests-using-tracing-in-iis-7/ You can enable it on your account, and set it to log all 500 errors in a specific folder. So when the error occurs, it notes it down in the logs, and it'll tell you the exact error of why it's having problems. These 500 errors are a bit tricky, since they don't really provide you information as to WHAT is wrong, just tell you something is wrong.
I looked at the URL you sent over private message. What you are seeing is a custom error displayed by IIS. If you disable the custom error (IIS), you should see the real error message.
Thanks for your suggestions and kind help Jose & Bruce apologies for the delay been tied up back on it, will report shortly Nelly
Hi again Ive been trying to learn so that I can resolve my original issue and been dipping in and out of this for the past few weeks to no avail. Heres a copy of my web.config file <?xml version="1.0" encoding="UTF-8"?> <configuration> <location path="_html_createpages.asp"> <system.web> <identity impersonate="false" /> </system.web> <system.webServer> <tracing> <traceFailedRequests> </traceFailedRequests> </tracing> </system.webServer> </location> <system.webServer> <httpErrors errorMode="Custom" /> </system.webServer> </configuration> as you can see it relates directly to the page script (highlighted) that is used to generate the static html pages and is generating the 500 - Internal server error. I would appreciate it if someone could take a look and forward any suggestions as I want this issue resolved asap. Pm me if it's not a simple fix and more investigation is required - so that I can start regrowing my hair regards N3lly
...Why a classic ASP file? Scratching my head here...Are you including that inside an ASP.NET page? Additionally, the underscores, are they needed? Will that page execute if you hit it directly?
The e-commerce site is classic asp - we were previously on 2005 IIs6 upgraded to 2008 IIs7 - page is in root, in the backend admin panel there is a "generate static html" button, hitting this used to generate all site pages as html version pages in an upload folder with "index" - the idea being that you link from the home page to the index file to enable search engines to find & index the html page which fair better than dynamic pages in se's on hitting this now generates 500 error - prior to upgrading to 2008 IIs7 all worked fine hope ive given enough info thanks Nelly
This is the real error Server.MapPath() error 'ASP 0175 : 80004005' Disallowed Path Characters /_html_createpages.asp, line 153 The '..' characters are not allowed in the Path parameter for the MapPath method. You'll need to contact support to have them enable Parent path on your site.
Bruce and anyone who has tried to help many thanks for your efforts, I'll report back after ive been in contact with support to confirm that the solution worked. Nelly
Bruce / DASP Brilliant support! All working fine after Bruce's suggestion and quick response by the support team. Excellent, hope it helps others in the future. Nelly
