Has anyone seen this error more frequent in 5.0.2? We used to see this occasionally in 4.1.3, but since I upgraded the security domain to 5.0.2 more and more users are getting this error.
Yes, I have seen that in our configuration. We have our repository on DB2 and the CAE version we were using was not the correct one. When we upgraded the CAE version it worked fine.
If your repository is not in DB2, I will recreate the BO main key with the 5.0.2 version and see if that reduces the problem and make sure you use the right middleware with your repository database.