Reply to a comment from Filip Navratil

We upgraded from 12.0.1 to 12.0.2FP2 and started seeing this error. I am not sure why it worked before and not after upgrade. However, your post was a saviour.

Leave your reply right here