+1-888-365-2779
Try Now
More in this section

Forums / General Discussions / Failed workflow operation

Failed workflow operation

71 posts, 0 answered
  1. Keivan Kechmiri
    Keivan Kechmiri avatar
    38 posts
    Registered:
    16 Aug 2009
    19 Nov 2010
    Link to this post
    Hi

    When I try to Publish or Save as Draft i get a Popup saying Failed workflow operation and the page changes doesn't get saved.

    I'm having EN & Swedish as languages. I've checked no Workflow active.

    /Keivan
  2. Francois MARTIN
    Francois MARTIN avatar
    29 posts
    Registered:
    07 Aug 2005
    20 Nov 2010
    Link to this post
    ... got the same issue.
    Did you find a workaround ??
  3. Keivan Kechmiri
    Keivan Kechmiri avatar
    38 posts
    Registered:
    16 Aug 2009
    20 Nov 2010
    Link to this post
    No, so this is my biggest problem, can't do anyting on the site.

    /Keivan
  4. Francois MARTIN
    Francois MARTIN avatar
    29 posts
    Registered:
    07 Aug 2005
    20 Nov 2010
    Link to this post
    I've worked all day long yesterday to try to find a workaround the "Invalid time zone standard name", and finnally I installed a brand new Windows Server 2008 R2 in english with SQLServer 2008 R2 and Sitefinity...
    After long hours I got it to work... but immediately found that "Failed Workflow operation" whenever I try to save a page. Everything else seems to work but if it is impossible to save a page, them I'm definitly stuck...

    I have to admit that these two poblem combined are making Sitenity 4.0 RC completely unusable for me...
    This is frustrating.

    By the Way, my Windows server is purely US english with no french at all...

    **EDIT**
    In fact, this Failed Workflow thing does NOT happen if Sitefinity is used from Visual Studio 2010. It happens ONLY if project is used under IIS 7
  5. inanc
    inanc avatar
    5 posts
    Registered:
    11 Mar 2009
    20 Nov 2010
    Link to this post
    I'm having the same problem. I've installed the RC version on Windows2008 server and SQL2008. I can not create a new page. It always says:Failed workflow operation
  6. Jaime Weise
    Jaime Weise avatar
    120 posts
    Registered:
    02 Nov 2008
    21 Nov 2010
    Link to this post
    Possible Solution
    When I was first installing SF on the server I noticed that I was prompted to install the latest Telerik control suite to which I declined. For some reason I thought I had clicked on the wrong installer. I reinstalled the SDK this time installing the latest version of Telerik controls this time. Now, I seem to be able to use SF 4 as I imagined it would be. I don't get the WorkFlow errors anymore. 

    Sitefinity.4-0-907-0.msi reinstallation seemed to get me back on track. 

    EDITED
    Nope, I am still receiving the Failed Workflow Operation Errors. 

    Please Fix this problem!

  7. Jaime Weise
    Jaime Weise avatar
    120 posts
    Registered:
    02 Nov 2008
    21 Nov 2010
    Link to this post
    PROBLEM SOLVED
    I noticed that the SF4 worked fine until I integrated my projects. So, it appears that the legacy references, from work that I had done in the past, to Telerik assemblies are the root of the problem. After removing the dlls from my legacy projects, my publishing worked fine.

    Found the problem References

    So, the logical thing to do was to go and check what was going on in those projects. I looked inside the dll and sure enough there were references to Telerik.OpenAccess from the past.

    Removed the References from the Problem Project
    Beware, I had a rough time removing these references. I went to my project settings and removed all telerik references from the project. I also deleted the files in the bin and recompiled. 

    Side Note
    I remember in this particular project I was having trouble working with OpenAccess so I dumped it for LINQ to SQL. Therefore, those problem references (to Telerik.OpenAccess) weren't necessary. Most likely you will have to update the Telerik References in your project for this problem to go away. In my case, I just irradicated them.

    Finally Removed The References
    I had surely removed every trace of Telerik from the problem project. Still, I got the Failed Workflow Operation again. So, I opened up the dll from the project with Red Gate Reflector. That revealed that there was still a reference to Telerik.OpenAccess. Because, I couldn't seem to kick this problem,  I created a new project and moved all the files into the new project, compiled and then...

    SUCCESS!
    I am now in business--fingers crossed--but it looks good so far.
  8. Francois MARTIN
    Francois MARTIN avatar
    29 posts
    Registered:
    07 Aug 2005
    21 Nov 2010
    Link to this post
    Brilliant!
    I hope that this will be usefull to the Telerik guy to understand and fix the problem for this week's build!
  9. Jaime Weise
    Jaime Weise avatar
    120 posts
    Registered:
    02 Nov 2008
    21 Nov 2010
    Link to this post
    Not so Fast..
    I did this on my development machine and was getting the Failed Workflow Operation. The aforementioned steps did get me working on this machine. I haven't however been able to get it working on my server. So, I don't think we are out of the woods yet. 

  10. Francois MARTIN
    Francois MARTIN avatar
    29 posts
    Registered:
    07 Aug 2005
    22 Nov 2010
    Link to this post
    I'm pushing this topic "up".
    Please you guys from telerik, would that be possible to include a fix for this issue in your release today, or as "soon as possible" ?

    We know that your are doing your best, thanks for that.
  11. Keivan Kechmiri
    Keivan Kechmiri avatar
    38 posts
    Registered:
    16 Aug 2009
    22 Nov 2010
    Link to this post
    Any response from Telerik?
  12. SolarX
    SolarX avatar
    14 posts
    Registered:
    24 Oct 2006
    22 Nov 2010
    Link to this post
    I have the same problem!
    Uninstalled everything. No luck.
  13. Francois MARTIN
    Francois MARTIN avatar
    29 posts
    Registered:
    07 Aug 2005
    22 Nov 2010
    Link to this post
    The new build is online.
    Problem disapeared.

    Solved.

    Thanks guys.
  14. Kristian
    Kristian avatar
    214 posts
    Registered:
    03 Jun 2010
    22 Nov 2010
    Link to this post
    Still happens for me :(
  15. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    22 Nov 2010
    Link to this post
    Hi Kristian,

    Do you get the exception in the project you have previously created, and then upgraded to the new version? Or you get the error when you set up a new project with the latest release (build 910)

    Greetings,
    Radoslav Georgiev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  16. Kristian
    Kristian avatar
    214 posts
    Registered:
    03 Jun 2010
    22 Nov 2010
    Link to this post
    It is the previous project I have had when upgrading it gives me the exception. im upgrading it from beta 2 to 4.0.910.0
  17. bemara57
    bemara57 avatar
    135 posts
    Registered:
    27 Mar 2008
    22 Nov 2010
    Link to this post
    I am getting the same error. I created the project locally and deployed to an DiscountASP hosting environment. Everything is fine until I publish the page I get the error.
  18. Rich
    Rich avatar
    27 posts
    Registered:
    20 Feb 2010
    23 Nov 2010
    Link to this post
    I have a new 2 page project that I deployed to the production server.  There are no remnants from older projects.  It works fine when put on my development box.  The Firebug reported an empty guid being sent to the webservice.  The details of this are located in the support call:

    http://www.sitefinity.com/account/support-tickets/view-ticket.aspx?threadid=369010

  19. bemara57
    bemara57 avatar
    135 posts
    Registered:
    27 Mar 2008
    23 Nov 2010
    Link to this post
    The error went away for me after yesterday's update release
  20. Rich
    Rich avatar
    27 posts
    Registered:
    20 Feb 2010
    23 Nov 2010
    Link to this post
    I just discovered the reference to fixing the problem in yesterday's release, so I'm downloading it now.

    The new version did fix the problem.

    Thanks,
    Rich
  21. Jesper
    Jesper avatar
    4 posts
    Registered:
    10 Nov 2010
    03 Dec 2010
    Link to this post
    Hi Rich,

    Are we to understand that you installed the latest release (Sitefinity.4-0-941-0) and the "Failed Workflow Operation" went away ?

    We have two installations on IIS that failed, and for some reason one of them suddenly worked on the previous release (still does on 4-0-941-0 after the upgrade) but the other fails. We are lost as to what we did that made it work - and we cant get the other site running without the error.

    This is so time consuming and frustrating.

    Jesper
  22. Georgi
    Georgi avatar
    3583 posts
    Registered:
    20 Sep 2016
    06 Dec 2010
    Link to this post
    Hello Jesper,

    Unfortunately we are not able to reproduce the problem locally.
    It is really interesting for us the environment on which the project runs. Can you please describe it in more details? You can check if the /Workflows directory exists. You can also try to upgrade to 962 build, which we released on Friday.

    Best wishes,
    Georgi
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  23. Bill Y
    Bill Y avatar
    22 posts
    Registered:
    04 Nov 2010
    09 Dec 2010
    Link to this post
    I'm having the same issue too since original RC version. I am currently using RC 962.

    This seems to only relate to one particular action:

    [PUT]http://website/Sitefinity/Services/Workflow/WorkflowService.svc/MessageWorkflow/446197dc-b7ba-413b-8a4d-c803136d0a6f/?itemType=Telerik.Sitefinity.Pages.Model.PageNode&workflowOperation=Publish

    this will result a timeout, with following response:

     {"Detail":"There was no endpoint listening at http:\/\/website\/Workflows\/PagesApprovalWorkflow.xamlx that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details."}

    but when manually navigated to http://website/Workflows/PagesApprovalWorkflow.xamlx, the page is indeed reachable.
  24. Jesper
    Jesper avatar
    4 posts
    Registered:
    10 Nov 2010
    09 Dec 2010
    Link to this post
    We found that if we insert a reference to the internal IP adress and the domain name, the problem dissapears.

    On the server you have to edit the hosts file (Windows\system32\drivers\etc\hosts):
    10.0.0.3    www.domaininquestion.com

    Hope you all can use this.

    To Telerik; is this a viable solution?

    regards
    Jesper
  25. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    09 Dec 2010
    Link to this post
    Hi Jesper,

    Thank you for joining the conversation.

    The problem is caused because Sitefinity is messaging the workflow internally, not from the same location from which you are trying to publish the item. We have been able to find a temporary workaround the issue which can be used until we resolve the problem. The workaround includes referencing the the host header in the hosts file:
    127.0.0.1   domainname.com

    And also adding the host header with this IP to the configuration of the site in IIS as in attached screen cast.

    All the best,
    Radoslav Georgiev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  26. Bill Y
    Bill Y avatar
    22 posts
    Registered:
    04 Nov 2010
    09 Dec 2010
    Link to this post
    Thanks Jesper and Radoslav, the workaround works for me!
  27. Jaime Weise
    Jaime Weise avatar
    120 posts
    Registered:
    02 Nov 2008
    13 Dec 2010
    Link to this post
    This workaround leads me to this error. 

    The requested service, 'http://ellevate.net/Workflows/PagesApprovalWorkflow.xamlx' could not be activated. See the server's diagnostic trace logs for more information.

    Please help me out with this. I need to deploy my website fairly soon.


  28. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    15 Dec 2010
    Link to this post
    Hello jaime,

    Can you please send us the SdrConfigExample.e2e file from the root of your website, so that we can examine the svc call trace log?

    Kind regards,
    Radoslav Georgiev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  29. Jaime Weise
    Jaime Weise avatar
    120 posts
    Registered:
    02 Nov 2008
    16 Dec 2010
    Link to this post
    Mabye I was on to something in my earlier post
    I was able to isolate the problem to when I added my data project as a reference to the project or to be more specific when I added the data project dll to the bin folder. From that point I start to get the workflow operation failed error.

    Telerik leaves a reference in your .proj file
    There is an interesting side-effect of having OpenAccess(older version) referenced in your project. That is, not only will it break your application but, if you delete all the references to OpenAccess from within your project, you will find that inside the dll there will still be a reference, embedded in the dll, to open access after build. What you need to do is open up your .proj file in your favorite text editor and delete the open access targets element. From that point on you will "really" have eradicated the troubled reference. I don't know if there are other things that come into play and make this problem happen but I certainly could turn the problem on and off by adding or removing the problem dll. 

    Just update it probably
    I assume that if you add the current OpenAccess library to your project the headache will also go away. I did get more headaches but I am going to assume for now that I caused them.

  30. Mikael
    Mikael avatar
    1 posts
    Registered:
    31 Mar 2009
    01 Feb 2011
    Link to this post
    Hello,

    I'm continuing this thread. Is there a permanent solution to this? I have downloaded the trial and installed the Standard Edition of Sitefinity (4.0.1098.0) on IIS7 (Windows Server 2008).

    I am stuck at my first page... When trying to publish the page I get the following messagebox:

    'There was no endpoint listening at http://<mydomain>/DefaultWorkflows/PagesApprovalWorkflow.xamlx that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.'
71 posts, 0 answered
1 2 3