On rare occasions we have seen that when user creates a position and goes straight to PA to use it, he can get this error message. If user logs off/on, it is resolved. I suspect some kind of database delay or buffering, but we have not been able to reproduce it to the point where we can figure out what is going on.
I don't know if this fits your scenario or not.
/Kirsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.