SecurityNegotiationError Action unrecognized after some time RRS feed

  • Question

  • My Workflow Service has a problem that it works for a while but then (sometimes a day, sometimes 2 hours) I get the following error when calling a send and recive activity:

    Fehler bei der Freigabe
    An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.

    Type: System.ServiceModel.Security.MessageSecurityException
    Server stack trace:

       at System.ServiceModel.Security.SecuritySessionClientSettings`1.SecurityRequestSessionChannel.ProcessReply(Message reply, TimeSpan timeout, SecurityProtocolCorrelationState correlationState)
       at System.ServiceModel.Security.SecuritySessionClientSettings`1.SecurityRequestSessionChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    The message could not be processed because the action 'http://tempuri.org/IService/TaskComplete' is invalid or unrecognized.
    Type: System.ServiceModel.FaultException

    When this error once happend all Send and Recive operations stop working also the operations of the WorkflowControlEndpoint like terminate do not work anymore. Only possibility to solve this is restart the application

    What irritates me most is that he suddenly does not find the method anymore, not just for the instance (what could be related to persistance) its not possible to call anything anymore for the complete WorkflowService.

    There are articles about clock time related with An unsecured or incorrectly secured fault was received from the other party but the operation is called by the same process on the same maschine (Actually the client calls one service which calls then the workflow service).

    I've found this threads related to the problem with, but none solved my problem


    Have someone already expirienced this?

    Tuesday, November 20, 2012 1:35 PM

All replies

  • Hi, I got a similar exception from a workflow consuming a WCF Service...

    Did you find a fix?

    Saturday, May 18, 2013 7:38 AM