We were told that 5.2.3 fixed it, but it didnt. We spent significant time troubleshooting with TAC and sent tons of debug logs. They did find the issue and address it, but Im not sure if its released or not yet. I would suspect it is by now, but it wasnt 5.2.3, there must be a patch or a later rev number than 5.2.3 to fix it.
bob