No endpoint listening at http://....../DefaultWorkflows/Any...
Hello everyone,
We've just pushed a website live and are getting the attached error when we are trying to create and publish blog posts.
We don't have this issue in the staging evironment...
Can anyone help? It's rather urgent!
Thank you!!!
Vix
Hi Viktoriya,
We have introduced a new property (WorkflowBaseUrl) in Administration -> Settings -> Advanced -> System -> ServicePaths. You should set the base url to the domain name you are publicly viewing your website on, for example http://mydomain.com. The problem might come from the fact 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. If setting the WorkflowBaseUrl does not help, please check with FireBug if the GET & PUT methods work properly when trying to publish a page, because the problem may be coming from request restrictions of IIS.
You can try using a workaround which includes referencing the the host header in the hosts file e.g :
127.0.0.1 domainname.com
and also adding the host header with this IP to the configuration of the site in IIS. Make sure that you bind the correct IP address to your localhost not your domain if you are testing locally.
I hope you find this information useful. If you need any further assistance with this issue, please do not hesitate to contact me.
Regards,
Boyan Barnev
the Telerik team
Hi Boyan,
Thanks for your reply. We found the issue yesterday.
It turned out that the .xamlx handler was not mapped on the server.
I still however followed your instructions about the setting of the WorkflowBaseUrl property.
Thank you again.
Viktoriya
Hi
Hi,
I having the same issue, but when i try to save changes I got a message saying that access to the path .../SystemConfig.config is denied . What would be a solution for this.
Thank you.
Hi Anh,
Most probably the ASP.NET worker process does not have read/write permissions over App_Data and configuration files. Please grant the asp.net user account (or network service) with read/write permissions. You can do this from windows explorer if you have direct access to the server.
Regards,
Svetoslav Manchev
Telerik