[Anonymous]

Thank you. I've had this same exception, which was fixed after modifying web.config on ALL frontends…