Error Details
Error Message:
The request failed with HTTP status 401: Unauthorized.
Message Stack:
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.HelpdeskWS.WebService.ExecuteQuery(String queryText, Int32 maxRowsToReturn)
at Symantec.Workflow.Components.ServiceDesk.FindServiceDeskContact.Run(IData data)
at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context) in c:\Stuff\projects\platform2006\core\LogicBase.Core\ExecutionEngine\ExecutionEngineDelegates.cs:line 238
at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.DoRunComp(IOrchestrationComponent comp, IData data, TLExecutionContext context) in c:\Stuff\projects\platform2006\core\LogicBase.Core\ExecutionEngine\ExecutionEngineImplementation.cs:line 42This problem has also been observed while running a project in debug mode. You may see the first form appear, but then the 2nd form times out and when reviewing logs, both LAN trace logs and Workflow service logs result in 401 errors.
One other cause that has been obeserved is that the FQDN (fully qualified domain name) of the Notification Server was entered into the Notification Server Credentials Tool.
Applies To
Workflow Solution 6.0
Workflow Solution Advanced 6.5