From the LTUG listserve:
Lacerte is aware of this issue and is working on it. It was caused by last week’s update and it only affects network users that use UNC paths for identifying network folders.
View solution in original post
