Video Screencast Help

Issue with "Run Job on Computer" component

Created: 14 Mar 2011 | 2 comments

We just installed a new DS. We are able to set up the connections to it, and the "get Computer component works just fine as well, but if I try to run a job on a PC via a webform process, i get the following...

Symantec.Components.DS.Components.RunJobOnComputerComponent

run Delete from AD and DS on Computer

7f1c2975-ddf4-43b3-a9cc-2a4102829e9d

System.Web.Services.Protocols.SoapException

Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks ---> Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks

System.Web.Services.Protocols.SoapException: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks ---> Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Symantec.Workflow.Core.DS.ScheduleManagement.ScheduleManagementService.CreateJobSchedule(Int32 computerID, Int32 jobID, Boolean scheduleNow, String applicationName, String scheduleAttributes) at Symantec.Workflow.Core.DS.DeploymentServerFacade.CreateJobSchedule(String applicationName, Int32 computerId, Int32 jobId, Boolean scheduleNow, Schedule schedule) at Symantec.Workflow.Core.DS.DeploymentServerFacade.RunJobNow(String applicationName, Int32 computerId, Int32 jobId) at Symantec.Components.DS.Components.RunJobOnComputerComponent.DoRun(IData data) at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context) at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.DoRunComp(IOrchestrationComponent comp, IData data, TLExecutionContext context)

 

The old DS still works fine, but most of the PCs have been migrated to the new one. Any ideas? I've tried recreating the components but get the same issue.

Comments 2 CommentsJump to latest comment

reecardo's picture

If the component runs fine against an old DS< yet a new DS version introduces a problem, the problem lies in the web service.

Jimbaland's picture

DS is the same version, just installed on a new server.