This is exactly the problem those new to DNN/SQL may be facing, just like me.  New users may not know enough to be able to "find out what config. problem caused the error in the first place".  Without specific steps to help troubleshoot connection issues, such a suggestion is too vague, too general.  I agree there are risks attempting to patch an installation, but sometimes the most important thing maybe be to get up and running.  For the sake of DotNetNuke, that's better than having frustrated new users quit and move on to another application.