This is a known issue that occurred after updating to Vectorworks 2017 SP2 on a Mac. The solution described here should solve the issue.