unable to save pages, etc. - error message

We deployed our sitefinity app to our actual dev server and now we can't publish pages, save pages, etc.
I get the following error message:

There was no endpoint listening at http://dev.myMarketplace/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.”

any suggestions on what is causing this? I can create new pages, templates, etc, but get the error message and I can't publish the new page, etc

Did you see this post? http://www.sitefinity.com/devnet/forums/sitefinity-4-x/general-discussions/no-endpoint-for-anymediacontentapprovalworkflow.aspx. Might help in your situation.

**update- whoops, sorry I see that you did see that post already*

yes I did, and nothing mentioned helped my situation.

Hello CsharpGuy,

Could you please give us some more information about your project - is it running on IIS or VS integrated web server or the Project Manager's integrated web server? Can you please let us know how your IIS is set up if you are running the site there and you have any restrictions on accessing the outside world form the host machine.


Kind regards,
Victor Velev
the Telerik team

I installed it a  web site. I copied the needed files from my dev machine to my server and set it up under IIS as a web site. I can access everything but can't publish, save, etc.

I have the site setup under a folder and setup the site under IIS to point to that folder. the site is running under a port number and not the port 80

Hi NWTResearch,

Thank you for getting back to me.

 The problem with IIS is that the request from outside may come for one location but internally it is forwarded to another and then Sitefinity does not know where exactly the default workflows are. Also another case for this issue is if for example the VPS you are hosting the website has restrictions on outbound traffic.

You can try and take your DB from your PC where it is working and copy the configs except the DataConfig.config and try to run it again.

If this solution does not help can you please share a little bit more how the project is set up on your local VS?

Best wishes,
Victor Velev
the Telerik team

that solution didn't work. Right now the project is setup in two locations on my local

1. setup in a folder for development purposes such as (c:\mysites\clientnumber1) I open sitefinity run the admin portion of it, edit in VS, etc and its fine.

when I want to test it under an IIS environment, I then move it to my clientnumber1 folder under inetpub/wwwroot folder and I'm able to save pages, publish pages, etc with no problem.

On my server, I have the site setup as a virtual on so its point to c:\sites\clientnumber1 and my IIS set is pointing to that, so I access it as http://dev.clientnumber1.com:100/ and I can't save, publish, etc, only view

Do I need to run the site under inetpub/wwwroot directory on my server as well for everything to work correctly and do I need to remove the port number and just have it as http://dev.clientnumber1.com?

My local environment is running Windows 7, IIS7
my server is windows 2008 server, IIS7

Hello NWTResearch,

Are you sure you made all the necessary redirections and settings in IIS, because it seems to be some misunderstanding between IIS and Sitefinity. Can you create a new project on your live server by creating a web site in IIS then browsing to it from Sitefinity Project Manager and check if you have the needed permissions.

Regards,
Victor Velev
the Telerik team

I was experiencing the same issue and none of the suggestions worked.  Our scenario was that I had a web server with multiple sites.  We used a common, internal IP for our server and I had a host-header set up for the site.  Additionally, our domain name was registered elsewhere and had to use the external IP.  However, internally, we had a different IP. What wound up working for me was adding an entry to the HOSTS file for the internal IP and RESTARTING IIS.  After doing that, and setting the services path, everything worked.  Hope this helps.

Hello Assid,

When you set your WorkflowBaseUrl please make sure to write your top level domain, for example " http://q-principle.com "

The problem with it is that the request from outside may come for one location but internally it is forwarded to another and then Sitefinity does not know where exactly the default workflows are.

You can also check the following article:

http://www.sitefinity.com/devnet/forums/sitefinity-4-x/general-discussions/failed-workflow-operation.aspx

Can you try to make domain mapping for the domain into the server hosts file, and then pointed them to the "localhost" address. Are you getting this error if you use our ProjectManager to run the website or you use Visual Studio built-in web server?

Kind regards,
Victor Velev
the Telerik team