tvordlj | (no subject)

Sorted out that problem. One of the webby guys mentioned that it looked like the url was trying to access an application on Server a. I was under the impression it was on server B but apparently there's a version on A as well. Ahhhhh..... Light goes on. Send me the webserver configuration file.
Yep, there it is.
Several months ago a database was moved to a new server and we had to change the pointer to the new server. This was done and tested on the servers that we thought were the ones where the applications were. Did not know about this other server so it's been pointing to a non -existent database since early february. The request said they used this application on a daily basis. Well some of your staff might but whoever was using that particular url couldn't possibly be because it hasn't worked since early February.

I was able to get to the server and change the setting but i couldn't restart the web server bit so had to wait for an administrator with access to do that. Badda bing badda boom and we're in business again. On both servers. The server we'd been familiar with is a testing server ("QA" for those of you that know the lingo) and I did wonder why they were running an application on that but that's what I was told so that's what we fixed back then. The server that "broke" yesterday is the Live environment server. That makes more sense. Now apparently we'll have people using it on both but both are pointing to a Live database not a QA one so it's ok for now. These are applications written by a former employee from when the web eservices programming was done from a different department, not our IT Developer team. That programmer left and the rest of us are mystified most of the time as to what the apps do and how to fix them if something goes wrong. We'll end up rewriting them in the new technology we're learning now though.

Bring on vacation! I'm off now and G. arrives on Saturday! Woot!