This is getting weird, and I am assuming that no-one can help or is interested as I received no response to my last posting. I went through a full cycle, keeping careful notes as I went. If logs are desired, I could send them but they are of no help in this situation. Added note: Symantec Backup Exec also runs on this server. This section of SQL Server has NO Problem.... (Interesting detail...)
Quick Rundown of results. I'll skip as much detail as possible to save space.
1)Wiped Logs and started uninstall. Strangely, the uninstall requested me to close SQL Monitor application, while NOT requesting me to close any of the other apps that were running. Also, for the first time, upon completion of the uninstall, all SQL services were running OK. Checking the Logs at this time showed NO errors whatsoever. SQL Operating correctly.
2) Re-booted server to complete the uninstall, as requested by the program. SQL Server starts up fine for Backup Exec but the Main database does not start. Only two entries in the System log. Timeout and a notification that the service did not start in a timely fashion. SQL error log for Back-up Exec shows what I consider to be a normal startup. Main Errorlog not opened at all. Still contained the data from the previos startup while SEP was loaded. (File not modified. Service didn't access the ERRORLOG file.)
3) Seeing that this problem prevents SEP from from being upgraded, or uninstalled, without losing SQL, which is this servers main function, my only recourse is a full re-load with a new AV and back-up program, as there is obviously some relation, either undocumented on unintended. The business owners have decided that enough is enough, so new server and applications are in order. I have no progblem with Backup Exec, but all related products to SEP are in hot water with the bosses, and losing the server due to something like this is unacceptable to them. I can think of several ways that this could have taken the system down in such a way as to require a reload during business hours. Not the way to garner faith in the product, if you know what I mean. Had the SEPM auto-upgraded........
I thank-you all for your time, and will keep checking here over the rest of this week, but with the time already spent, I doubt Symantec has a future in this company. I am sorry about that as I actually like the package, and have had no problems with it until now. (Well, the little ones with any large network, but they were all solveable with a couple days research.) If anyone has a clue as to where to go from here, or any test for further information, please let me know. A full change of the network will take time to go through purchasing, and selection of new AV packages and Back-up will also take time, giving me the ability to keep trying. I am re-installing SEP 11 right now, as that operation fixes all. Quite a way to ensure product loyalty, but a questionable business practice, if you ask me.
Has anyone else seen this type of situation? With ANY other application? I maintain quite a few networks and don't want to think about having to recomend changing to them all. One is more than enough until I fully learn the new package's operation. Also, any recomendations there?
Thanks again for any help that anyone can provide.