In case any of you missed this,

Dayan on page 5 of this thread figured out a work around. I haven't had to use it yet..but nice job! Hopefully I don't encounter the error again today.