I just read through this ENTIRE thread, and it's some of the funniest stuff I've read in a long time.
Had to sign up, just to add my two cents.
WMI backup became a problem for me on August 30. Interesting, I had just upgraded the problem server from SAV 9.0 to SAV 10.0 the week before. I was forced to do an uninstall/reinstall, because a straight upgrade didn't work.The server was NOT rebooted, at the time of the SAV upgrade, rather, it was rebooted that tuesday, when automatic Updates installed some updates and rebooted. BAM! After the reboot, my WMI doesn't mbackup, and each job of the server since then fails, locking up BE, and requiring either a server reboot, or restart of the BE services. So, in my case (as well as several others, it appears here), the problem is some incompatibility between BE and SAV 10.0.
How many of your problems began after an upgrade to SAV 10.0, or the next reboot after SAV10 was installed? I suggest we all try "Chief Bottlewashers" suggestion from page 5:
"Nah, I'm a Symantec tech support wallah, and I'm looking at issues with SAV 10 and the WMI and errors with the BackupExec.
Would you care to try excluding the C:\WINNT\system32\wbem\Repository from the autoprotect and see if that helps ? "
I'll do it, and let you know.