We are having the same error message, on 1 out of 7 workstations. So frustrating!! Has anyone found a fix for this yet?
