I can reproduce it. Apparently it was caused by the Developer's code. She removed a couple page references from her project (i.e. basicsearch.aspx and advsearch.aspx) and now just processes everything with a single page. However, when people now try to go to these old pages directly the application cycles through, throws an error, then displays a contact the webmaster page. This also generates the parse error since I assume she is not handling the error gracefully. If All in all, I believe I need to speak with the Dev to try to make the case that this is probably not the best way to handle this. I know this can have a performance impact on the application but any suggestions as to why this is not a good practice?
Main Topics
Browse All Topics





by: abelPosted on 2009-08-24 at 07:58:50ID: 25168965
I'm afraid you are going to need some coding experience to get this solved. On the referred to page, there's probably a class or a control (ascx) that is doing the advancedsearch (it apparently fails on your advanced search page). To resolve this error, we need two things:
1. It must be reproducible
2. Setup Visual Studio to debug (either local or remote)
Without the error reproducible, it will become really hard, even for experienced programmers and debuggers. If we can somehow get this reproducible, we have done half the work. To find out what to do, inspect your log files of IIS just before or around the moment the error occurs, so you know exactly what request was made (it will likely have an URL corresponding with mypage.aspx, but not necessarily).
-- Abel --