Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Creating a Conditional Job Using Tasks

Created: 14 Jun 2010 • Updated: 09 Sep 2010 | 5 comments
Steven.Riley's picture
0 0 Votes
Login to vote
Symantec single video player.

This video demonstrates a basic conditional task that works on a client, makes the client "do some work" then the client reports back based on the work it did. The condition executes the if else statement based on the condition that comes back from  the client.

Please Note:
This video is best viewed in full screen mode by selecting the square icon in the lower right hand corner of the video player.

Video Upload: 

Comments 5 CommentsJump to latest comment

noodleNT's picture

I am using the "Control Service State" task to poll what the service status is and then trying to use a conditional task to run a task if the service is not running or not. However the conditional step will toss an error. Is this a known issue?

 

Error:

 

An unknown exception was thrown.
 
System.Exception: The parameter name "b9b60c41-59f0-449f-9298-2e92b6810924_ServiceState" is not in our input list and this condition cannot be evaluated at Altiris.TaskManagement.Common.Jobs.BaseConditionEntry.Evaluate(ParameterValueCollection inputParameterValues) at Altiris.TaskManagement.Common.Jobs.PreviousReturnConditionConfig.EvaluateCondition(ParameterValueCollection inputParameterValues) at Altiris.TaskManagement.Jobs.Conditions.ServerPreviousReturnValueTask.OnExecute(IServerTaskExecutionInstance instance) at Altiris.TaskManagement.ServerTasks.BaseServerTask.OnExecute(ITaskExecutionEngine engine, IServerTaskExecutionInstance instance, TaskInstanceRequest request) at Altiris.TaskManagement.ServerTasks.BaseServerTask.Execute(ITaskExecutionEngine engine, IBaseTaskExecutionInstance instance, TaskInstanceRequest request) at Altiris.TaskManagement.Common.Execution.Engine.TaskEngineExecutionThread.ExecuteTaskHandler()

 

0
Login to vote
benmarkowitz's picture

I'm seeing the exact same error with SMP 7.1 sp2. Anyone else?

0
Login to vote
benmarkowitz's picture

Apparently it's a known issue, originally slated to be fixed in sp2. Does anyone have an update on when the fix will be released?

http://www.symantec.com/docs/TECH167206

0
Login to vote
noodleNT's picture

Is this fixed?

0
Login to vote
luisdg's picture

I'm having the issue as well almost 1 year later than the last post.  What's up with this?  We're running 7.1 SP2 MP1.1v4.

0
Login to vote