Some applications are pretty complicated. For example, email and scheduling applications can be insanely complex with a lot of configuration files; incoming, outgoing, administrative, and extra queue directories; and so on. It can be hard to identify a corrupt file—or any other cause—that’s the monkey wrench in the works.
Here are some strategies that work with file and print application problems:
Check server and application logs.
Change the rules. (Can you simplify them? Can you move the app?)
Restore from a known good point in time.
A log file typically tells the tale pretty well. You’ll want to make sure that your application is configured for verbose- or debug-level logging if you’re experiencing problems. ...