Exactly right. Wish I had mod points for this. One of the numerous advantages of many open source solutions is that they are designed by hackers and when things go wrong, usually there are very distinct error messages and good logging capabilities. Coupled with some googling and/or IRC rooms, things usually get resolved very quickly. If you're a hacker yourself, you can usually resolve issues pretty quickly.
A common experience for me with closed source has been more along the lines of a message-box-only delivery of a very random error message with no other clues to go on. At that point you are at the mercy of the profit-motivated corporation's support center who has often outsourced their support operations. You'll have to fight for days or weeks jumping through meaningless hoops before you get your support case escalated to someone who can actually give you a correct answer.
That said, there is another edge to that sword. Being designed by hackers often means that unless you are a hacker yourself or have made smart choices in hiring one, you might find yourself struggling to maintain it because you don't have the skills to also manage the other open-source systems they build upon ( e.g. Database, http server, external libraries ). This can be solved usually by hiring people familiar with the open source world, but I can understand that it's tough to make a switch once you've hired a staff who is accustomed to the pointy-clicky way of doing things.