Altiris Object Host Service stops during Network Discovery
Last Updated July 21, 2012
When trying to set up a series of new Network Discovery Tasks, whenever you apply a schedule to the new Task, and the schedule triggers the task, the Altiris Object Host Service stops on the Notification server.
In the Windows Event Log there is the following error :
Module : AeXSVC.exe Source : Altiris.TaskManagement.ServerTasks.ServerTaskManager.CheckForTasksToProcess Description : ServerTaskManager.CheckForTasksToProcess() : Error setting work event. Restart Altiris Object Host Service. System.Threading.WaithandleCannotBeOpenedException : No handle of the given name exists.
The WMI protocol has no credentials specified in the WMI settings page.
The Default Connection Profile that is used in each discovery task has several protocols enabled by default : HTTP, ICMP, SNMP V1 V2, SNMP Trap Sender, WMI. And each of these has several settings selected by default.
Go to The Default Connection Profile then scroll down to the WMI.
Clicking in the Runtime Credentials tick box, and selecting Runtime WMI Credentials from the drop down, clicking OK, and re-running the task sorts everything out.
Another option is to turn off all protocols that are not being used, by clicking on the on/off button in the top right corner of the page.
Applies To Notification Server 7.0
Network Discovery 7.0
Imported Document ID: TECH127247
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe