Tasks keep being put to sleep
Not sure what is causing this but everytime a task runs it gets hung up. I checked the logs and I found this:
Module: AtrsHost.exe
Source: Altiris.TaskManagement.ServerTasks.ServerTaskExecutionInstance.Sleep
Description: Task instance Re-Run Antivirus inventory on Schedule1 (4/7/2010 1:33:35 PM) is being put to sleep until 4/7/2010 1:43:46 PM
After that I get flooded with a lot of instances with this:
Process: AeXSvc (1484)
Thread ID: 65
Module: AeXSVC.exe
Source: Altiris.Reporting.DataSource.ResourceDS.RModel.RMoResourceTypeItem.get_ResourceAsParentAssociationTypes
Description: ResourceAssociationType failed to load and is ignored:
Failed to initialise DefaultDestinationRMoResourceTypeItem.
Any idea what might be causing this. It was working fine for a few days then I started getting this.
Comments
More details?
What have you asked the task to do, and on what schedule? What version are you using? What OS is this running on? Is it possible the task is attempting to run a process or task that is already running? For example, are you attempting to run an inventory when an inventory is already in process?
Mike Clemson, Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
I'm running NS 7 on Windows
I'm running NS 7 on Windows Server 2003 R2 SP2.
I seem to have problems running any task. I first noticed it doing it with my Antivirus Inventory when it would fail at 100% since it would time out. I've tried some other tasks and they will do the same.
I checked the tasks and jobs and there are no other tasks running. I stopped all scheduled tasks for troubleshooting purposes. I also restarted the Altiris object host service and also the entire server. The same problem arises.
What version of NS and CMS?
Are you version 7.0 with no SPs, or do you have some SPs installed? NS (now called SMP) is on SP4, CMS is on SP2.
What OS is running the inventory task? What happens if you install the agent and run a task on a new computer, or if a new computer isn't available, uninstall the agent and reinstall the agent and then run the task?
Mike Clemson, Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
I'm running SMP SP4 and CMS
I'm running SMP SP4 and CMS SP2.
The inventory task is running through the windows server 2003 R2 SP2 with SMP on it.
The problem dosen't seem to be on the agent side as much as it is on the server.
Is this on a remote subnet?
I have seen a number of issues on remote subnets that don't have task servers. The error you posted above isn't related to task problems, and I think it is slated to be removed at some point. It is just more of an informational message.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
We do have multiple subnets
We do have multiple subnets but they are all in one site with the task server assigned to it. This problem is happening within the same subnet as the task server though.
How many clients?
I would take a look at the site maintenance screen and make sure they clients are reporting to the Task Server and not the Notification Server. The NS should not be directly handling any more than 500.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Ok, since this was a test
Ok, since this was a test instance I deleted the database and created a whole new one and reinstalled SMP and CMS on another Windows 2003 R2 server that was just installed with nothing else on it. I imported active directory and got the agent rolled out. Went to run the antivirus inventory and I'm getting the same thing again.
Since you didn't post your client base
but from the sounds of it, it's not large at this point, I'm not sure what else to add. Are the systems all registering with a task server? Do you have more than one task server?
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Client base is approximately
Client base is approximately 500 spread between two task servers. Clients are being registed with the task server as well.
I've only seen an issue when the exact opposite
was true. Either not enough task servers, specifically on remote subnets (where the clients would try and register with just the NS) OR clients not registering at all. Might be a call to support for you. I'll flag the thread, see if the bat phone gets picked up.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
I'm sorry to retrieve such an old issue, but since we are having a similar problem, did any solution come out?
Would you like to reply?
Login or Register to post your comment.