I'm up late and figured I would try and get this thing fixed.  It turns out to be a database permission...that I can't fix myself.

Nothing was happening before because of a catch block that was eating the exception.  Took that out and now you'll get this nice error message.  Since I don't have access to the master db I've sent in a ticket to WH4L with all of specifics and hoping they can get it cleared up ASAP.  I checked on my own server and public has execute permissions to that procedure.  I wonder why WH4L would change that.