Was this ever resolved. I am getting the same error right after I upgraded to 6.2.0.154

Thanks Matt. That did it.