Is there a common element among these servers (i.e. operating system.)? Does this occur with any patch (i.e. are you able to deploy a single Microsoft patch successfully, has this always been the behavior, etc.)? Is SQL 2005 installed on all of the machines in question?
It may also be very helpful to contact support so that we can obtain some log files.
I'm getting this same error. The location address is different on mine, but everything else is the same. Is there a fix for this?
I'm running VMWare vCenter Protect Essentials v8.0.0. The OS is Server 2003 Standard SP2 running as a VMWare virtual machine.
PatZiegler - I would suggest attempting to rebuild the scheduler service on the affected machine, as outlined below:
1) From an administrative command prompt, navigate to the following directory:
2) Execute the following command:
3) Close the command window, and delete the following directory:
4) Delete the following registry key(s) if they exist:
32 bit - 'HKEY_LOCAL_MACHINESOFTWAREShavlikScheduler'
64 bit - 'HKEY_LOCAL_MACHINESOFTWAREWow6432NodeShavlikScheduler'
5) Ensure that the scheduler service is no longer listed as a service.
Upon deployment, the scheduler service should be re-installed.
If the issue persists, please contact support directly so that we might obtain further details and log files for analysis. Support is available by telephone, toll-free, from 07:00 until 19:00 CST, Monday through Friday at 877.486.9273.
Hi. I get the same error on quite a lot of servers (maybe 20%). The servers all run Windows Server 2003 but some are at R2 and some have SQL 2000 installed but there's no consistency. The only way to move forward is to forcibly reboot the server via the rilo. I've tried removing the Scheduler service and letting the next deployment reinstall it but get the same issue.I run VMware vCenter Protect v8 (build 3787)I'll log a fault with Support but if anyone has already received a fix for this issue, I'd be grateful if you could post it up.Cheers