Recently encountered this on a client environment.  IIS reset did resolve the issue.