Workflow and ServiceDesk Community

 View Only
  • 1.  Workflow 7.0 - An item with the same key has already been added

    Posted Apr 15, 2011 03:58 PM

    I had a user walk through a workflow, and at the end, they received this error below...

    Has anyone seen this before?

     

    Error Details
    Error Message:
    An item with the same key has already been added.

    Message Stack:
    at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
    at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
    at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
    at Symantec.Workflow.Core.AltirisUtil.GetWebProxy(WebServiceStruct svc)
    at Symantec.Workflow.Core.AltirisUtil.GetWebService(WebServiceStruct svc, String notificationServerName, ProxySecurityToken token, Boolean useHttps)
    at Symantec.Workflow.Core.BaseAltirisSinglePathWSComponent.GetWebService(WebServiceStruct svc, IData data)
    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)
    at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.DoRunComp(IOrchestrationComponent comp, IData data, TLExecutionContext context)
     



  • 2.  RE: Workflow 7.0 - An item with the same key has already been added

    Posted Apr 15, 2011 04:46 PM

    Can you post some information about the workflow and what components are in use or screenshots of the interfaces? As the error says it has something to do with duplicate keys in a dictionary but it's hard to tell where that's coming from right now.



  • 3.  RE: Workflow 7.0 - An item with the same key has already been added

    Posted Apr 18, 2011 12:36 PM

    I get this error message sometimes and it usually comes from the Find Help Desk Contact component. I'm not sure what causes it but if a user gets this error but tries the same request right away it works.I can't seem to pinpoint this error because it's random and not always the same user.