Quantcast
Channel: Symantec Connect - Endpoint Management - Discussions
Viewing all articles
Browse latest Browse all 373

Workflow process failing in SD 7.5

$
0
0
I need a solution

Hello,

We have a custom workflow failing intermittently with below error logs. This has started after we upgraded our Altiris environment to 7.5. Our SD environment was already at 7.5. I have checked in the workflow and saw that SubmitIncident Component has been configured to time out at 120,000. However, I am unsure if that would cause it to fail as it is just the time process tries before failure.

Application Name : xxxxx.Feeder
Process ID : 4876
Date :3/20/2014 5:09:42 AM
Log Level :Error
Log Category :Symantec.ServiceDesk.Im.Core.Components.SubmitIncidentTicket
Machine Name : xxxxx
Message : 
Exception at Run method with message :Thread was being aborted.

***********************************************************************************************

Application Name : xxxxxx.Feeder
Process ID : 4876
Date :3/20/2014 5:09:42 AM
Log Level :Error
Log Category :LogicBase.Components.Default.Triggers.ExceptionTriggerByComponents
Machine Name : xxxxx
Message : 
System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)
   at System.Net.HttpWebRequest.EndWriteHeaders(Boolean async)
   at System.Net.HttpWebRequest.WriteHeadersCallback(WebExceptionStatus errorStatus, ConnectStream stream, Boolean async)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   at System.Net.HttpWebRequest.EndSubmitRequest()
   at System.Net.HttpWebRequest.GetResponse()
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Symantec.ServiceDesk.Im.Core.IncidentManagementService.IncidentManagement.SubmitIncidentAndReturnPID(IncidentTicket Incident)
   at Symantec.ServiceDesk.Im.Core.Components.SubmitIncidentTicket.Run(IData data)
   at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)

***********************************************************************************************

Application Name : xxxxxx.Feeder
Process ID : 4876
Date :3/20/2014 5:09:42 AM
Log Level :Error
Log Category :LogicBase.ExecutionEngine
Machine Name : xxxx
Message : 
System.Threading.ThreadAbortException: Thread was being aborted.
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)

Ticket does gets created, and as per the process it should be assigned to a group with Percent Completed to be at 25%. However, the ticket doesn't gets assigned to any queue and Percent Completed status at 0%.

Please advise.

Thanks
Snm1502


Viewing all articles
Browse latest Browse all 373

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>