locked
Cannot resume or Activate Workflows at PRODUCTION RRS feed

  • Question

  • When try to resume suspended workflows we get :

    A value of the wrong type was retrieved from the instance store.  A value of type {/prod.services.bankpozitif.com.tr/retail/loandomain/application/web/}Loan.xamlx was expected, but a value of type {/prod.services.bankpozitif.com.tr/Retail/LoanDomain/Application/Web/}Loan.xamlx was encountered instead.

    And When try to activate idle or persisted workflows we get :  

    System.ServiceModel.FaultException: The execution of an InstancePersistenceCommand was interrupted because the instance key '5c02a695-02ca-bcd1-8a81-3f447440f0da' was not associated to an instance. This can occur because the instance or key has been cleaned up, or because the key is invalid. The key may be invalid if the message it was generated from was sent at the wrong time or contained incorrect correlation data.

    We just add http header to workflow site

    Wednesday, June 6, 2012 7:29 PM

Answers

  • Since you mention the problem occurs in production, note that if your problem is urgent or business critical, the most fast and reliable way to get help is via Microsoft paid support.

    The first symptom mentioned suggests that you have changed case of URIs that are being used somewhere in workflow instance serialization. Since URIs are case sensitive according to standard, this could equate to a breaking change in serialization format.
    Tim

    • Marked as answer by Ugur KARATAS Friday, June 8, 2012 8:13 AM
    Thursday, June 7, 2012 10:15 PM

All replies

  • Since you mention the problem occurs in production, note that if your problem is urgent or business critical, the most fast and reliable way to get help is via Microsoft paid support.

    The first symptom mentioned suggests that you have changed case of URIs that are being used somewhere in workflow instance serialization. Since URIs are case sensitive according to standard, this could equate to a breaking change in serialization format.
    Tim

    • Marked as answer by Ugur KARATAS Friday, June 8, 2012 8:13 AM
    Thursday, June 7, 2012 10:15 PM
  • Thanks Tim.

    Yes you right, reliable way is getting help from direct support MS (In fact, we have enterprise agreement with MS, so its includes all level incidents and supports). But is not fast way.

    Anyway, you are right, URIs are case sensitive, and we do not changed any URIs case. But when we add host header to IIS for https protocol, i think URI generation is changed on IIS internals.

    So we easily changed existing xaml path "/Retail/LoanDomain/Application/Web/" to "/retail/loandomain/application/web/" and we get back functionality.

    Friday, June 8, 2012 4:42 AM