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

Forums / General Discussions / Failed workflow operation

Failed workflow operation

71 posts, 0 answered
  1. Solomon Shaffer
    Solomon Shaffer avatar
    22 posts
    Registered:
    18 Jan 2011
    02 Aug 2011
    Link to this post
    Crazy, M6 is listed as a Sitefinity hosting partner. They should at least be able to host a SF4 site.

    Solomon
  2. Micke Palm
    Micke Palm avatar
    17 posts
    Registered:
    27 Aug 2012
    14 Sep 2011
    Link to this post
    Bump!

    Have anyone any solution on this??

    /Thanks
  3. Solomon Shaffer
    Solomon Shaffer avatar
    22 posts
    Registered:
    18 Jan 2011
    14 Sep 2011
    Link to this post
    For me,  this was a routing issue. The problem is the system needs a URL to connect to the WCF services (even though the WCF services are served from the same site). My host had a temporary URL for me (i.e. mydomain.hostdomain.com) that was doing some routing on the back end to get me to my IIS site. The WCF service default URL is determined at runtime (i.e. mydomain.hostdomain.com/services/blahblahblah.svc) and was not able to access the service because of the routing (a common problem in WCF). When I switched to a proper domain name (i.e. mydomain.com), everything worked because the routing was not happening anymore. 

    That was my problem anyway. If your environment looks anything like that, I would bet that is your problem.

    You may be able to get around this by setting the service URL in the Settings module to something like an IP or non-routed URL - I did not try this. 

    Solomon
  4. Micke Palm
    Micke Palm avatar
    17 posts
    Registered:
    27 Aug 2012
    14 Sep 2011
    Link to this post
    I'm digging a little bit more in this and it's seems the server will lookup to another dns. I think that is the problem and I think you have right. It is a routing problem...

    /Thanks
  5. Jeremy
    Jeremy avatar
    37 posts
    Registered:
    17 Jan 2011
    27 Jan 2012
    Link to this post
    I've finally fixed this although I'm not sure how. In case my experience is of value to other I'll list our configuration and what we changed to get it working. It's important to note that the same project files and database worked fine locally on my development machine.

        Windows Server 2008 R2
        IIS 7.5
        Website running under a sub domain like http://mysub.mydomain.com
        Domain points at external IP and firewall routes external IP to internal IP
        Host header in IIS for sub domain and internal IP

    What we did to get it working

        Changed Host file to "interal IP mydomain.com"
        Changed WorkflowBaseURL to http://mysub.mydomain.com
        Added a loopback rule in the firewall to allow internal Sitefinity requests to use the public address. Here's more info on this. http://www.firewalls.com/videos/video/sonicwall-loopback-nat-policy.html
        Deleted Temp Internet Files and cookies to be thorough
        A few IIS restarts in the middle of all that
  6. Kunal Johar
    Kunal Johar avatar
    8 posts
    Registered:
    22 Jan 2010
    28 Mar 2012
    Link to this post
    Hey guys,

    I ran into this issue as well.  I solved it by going on the server and editing the hosts file.

    I added entries for domainname.com and www.domainname.com to 127.0.0.1

    In IIS I had the site listen to "every available ip address"

    Problem was likely because DNS would have pointed domainname.com to an external IP so the server could not find its own way
  7. Dan Sorensen
    Dan Sorensen avatar
    256 posts
    Registered:
    13 Aug 2010
    16 Apr 2012
    Link to this post
    Clarifying question: Is there a physical file associated with this call?

    Since our problem server was inside our firewall, we identified the cause of our issue to be a problematic internal DNS server. The HOSTS file work around worked fine. But the real solution was to ensure that our DNS server was back up and running.

    That said, I'm still curious about my clarifying question above.
  8. Anh
    Anh avatar
    3 posts
    Registered:
    07 Apr 2014
    07 Apr 2014 in reply to Radoslav Georgiev
    Link to this post

    Hi

    I also having same issue publishing a page and one of the solutions I saw after google around is to add value "https://mydomain" to the WorkflowBaseUrl. However, I can save changes; I got a message "Access to the path ...\Configuration\SystemConfig.config" is denied." Anyone know how to by pass this issue? I'm using Sitefinity 4.2

     

    Thank you.

  9. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    07 Apr 2014 in reply to Anh
    Link to this post

    @Anh

      Means that file is either ReadOnly, or your app pool doesn't have write access to the App_Data folder on your site.

  10. Anh
    Anh avatar
    3 posts
    Registered:
    07 Apr 2014
    07 Apr 2014 in reply to Steve
    Link to this post

    Hi Steve,

     

    Thanks for reply. I've checked, the SystemConfig.config is not Read-only however it Read-only for App_Data\Sitefinity\Configuration folders. Could you please let me know how to config the app pool to have write access to app_data?

     

    Thanks.

  11. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    07 Apr 2014 in reply to Anh
    Link to this post
    Add "iis apppool\<name>" as a user on the folder permissions, then give him write
71 posts, 0 answered
1 2 3