i did... still get the error. support is looking into it and supposedly have replicated the problem. what I didn't get from the release notes for the patch was whether it had been fixed or not. It doesn't look like it.. ;[-(