One of the recent Prism updates fixed a bug, which could result in this problem. Are you using the latest Prism version (v1.2.1.50 at the moment)?
One of the recent Prism updates fixed a bug, which could result in this problem. Are you using the latest Prism version (v1.2.1.50 at the moment)?