I keep getting a HTTP 500 – Internal server erroron one of my servers here at paxtonland labs. HTTP 500 – Internal server error from IIS 4/5.0, is one of the most widespread, yet ill-documented problems a webmaster can face.
Once, after exhausting every single possible fix, I had to actually resort to formating the hard drive of a web server that I was working on. No warnings, no explaination as for a cause, nothing changed in the server configurations… just one day, bang: “HTTP 500 – Internal server error”
And my difficult journey began.
I try to avoid cliche analogies but, can you imagine if you had to fix your car by employing the measures and techniques that you often have to resort to fix MS products? If your spark plug wires were deterriorating and begin to malfunction, then you would literally have to rewire the entire electical system of the vehicle. If a belt became worn, then every single component that the belt interacted with would also have to be replaced along with the belt. Too complicated? How about this: If your muffler fell off of your car, you’d replace the entire drive train of the vehicle.
What’s even more interesting to think about is this: If MS used the same techniques a mechanic would use to would fix your car, then when an important system driver became corrupt or, overwritten with an outdated version, it would automatically restore it from a stored backup, without bothering you with errors. You know, like a part on the shelf? Broken part, replace it. Simple.