Those three responses are what I have heard very often while working with this product for the past few years.
However, what is missing from option 1 is finding out WHY it failed. Is there a log I can review to see if there is something getting flagged? Are there diagnostics that can be run so that when I click the Check button someone from the back-end can view what is happening? Is there ANYTHING that can help fix this before resorting to option 2?
This is a server, not a desktop, so scheduling a day and time to reboot is already fixed by contract. If option 2 fails - and it has in many cases on desktops - I am going to have to reboot to remove the software altogether, and then run the clean utilities and reboot twice more. And then I am going to be using option 3. I am also going to have to devote several hours to get all of this accomplished.
As I have stated in other posts, I have alot vested in this product; therefore, I want it to improve. So I would like to know how best to identify what ails it, rather than patching around it. Otherwise, I'll be forced to find another vendor with a product that doesn't have a list of problems that recur without vendor-provided solutions.