Has anyone seen this error before? If you click ok it seems to work as it should. This is occurring on our Exec VP's system.



Thanks,
Bill