One of the cool things about Font Agent Pro is that you can manage fonts in BOTH Classic and OS X. That convenience ends with the FAP 4.0.3 update. (Actually we have a couple of users who are cool with 4.0.3. But the update took out five production machines, so I’m calling it a problem.)
OK, this is all a little stone age, I know. But some of us still have big legacy workflows in Classic.
Here’s the only fix that I’ve found so far: use the Uninstall Font Agent Pro application that comes in the Tools folder with the FAP 4.0.3 update. I don’t think the Uninstaller really does anything besides throw the app in the trash.
Next, re-install 4.0.2…you did keep the package didn’t you? If not, you’re pretty well screwed.
Finally, check the Activate Fonts in Classic tick box in the Activation panel of FAP Preferences, and then restart Classic. All should be rainbows and unicorns again.