"Who's our ASP expert?"
All eyes turn towards me. "Uh, I did ASP for about two months, but that's all."
Thus, I am their ASP expert.
The scenario: an ASP page is using an Excel spreadsheet for a database. The client has complained that they made some format changes to the spreadsheet and now the darned ASP page won't read it. Stupid ASP pages (sarcasm, folks).
Since the problem is either in the spreadsheet or the ASP page that reads it, the client decides to "fix" (?!?) the global.asa file. This is a file used with ASP pages (if used correctly) to store application and session information. That's it. It should have nothing to do with the fact that this guy changed his spreadsheet format. Fortunately, Front Page kept crashing whenever he tried to open the file. For once I am happy that MS apps can be flaky.
Meanwhile, I'm looking at the email complaint and it's
I still need to replicate the error. I need to get pass the password screen. I try forcing an error to see if they have weak security that I can break (we host the site, so I'm not worried), but no dice. I know the filesystem and, on a lark, type in the real URL directly, knowing that it won't work. But it does. I now have access to the appropriate screen, but it looks perfect. I hit reload a couple of times and it crashes and burns with a beautifully formatted "Database Results Error: Unspecified error".
Now I need to find the error log. Searching the Web, I find examples of VBScripts (!) that allow me to figure out the Web site number which I can then use to run on another script to determine the logs. (This is user-friendly?) Then another page tells me how to use the drag-n-drool GUI to figure out where the logs are hidden. Once I finally get to the log, it turns out to be an access log. I can't find error logs anywhere. I check the headers the page is returning and even on errors, it's returning a 200 OK status, thus implying that whatever errors might get reported, I may not even find them in an error log, if it exists. I don't know ASP very well, I don't know IIS very well. It's going to be a long day.