Hi All,
I have configured workflow manager on a dedicated server in my sharepoint farm. The configuration steps were completed successfully including the workflow settings and service bus (all steps ticked to show successful)
The workflow manager client has then been installed on the 2 front end servers and the 2 endpoints setup in IIS.
When going to central admin I can see the proxy setup and clicking on it shows it is connected successfully (after registering via powershell)
The issues are as follows;
Opening either endpoint does not display the XML file but a 403 forbidden
SharePoint Designer does not display the 2013 workflow option (even after clearing designer client cache)
It does however open the XML file when opening the endpoint in an IE session opened as administrator – I feel the issue relates to permissions in some way but struggling to see what? The permissions set are set as builtin\administrators.
Looking at that group it has the administrator account and our 2 regular farm accounts.
Any ideas folks I’ve spent a long time on this 🙂 any help would be appreciated
Lee
I know this is a year old, but I was running into the same sort of issue and after a lot of banging my head on the desk, I found that the admin group needed to be something other than builtin\administrators. I created a group in AD and setup WFM with it and it finally works.
Found the info on this site:Â http://www.sp2013blog.com/Lists/Posts/Post.aspx?ID=36
Thanks Hugh & Bujar I will go through both of these and post back tomorrow (I did run the register-spworkflowservice cmdlet)
Lee
Hi Lee
1st. did you download all the cumulative updates for Workflow Manager and Service Bus?
2nd, did you run the Register-SPWorkflowService cmdlet? Below is the link to the example commands:
http://msdn.microsoft.com/en-US/library/jj658588(v=office.15)#section2
Here is a link with video instruction on how to install Workflow manager and all about permissions as well.Â
http://msdn.microsoft.com/en-US/library/dn201724(v=office.15)
Copied from the chat, in case you missed it matey.
-
I had a look Lee
-
So far I’m struggling to absorb the issue
-
I think too much in my head
-
have you gone to the endpoint in the browser
-
if so
-
go to the server
-
stick fiddler on it
-
and record the server side
-
in there you will have a json object
-
which will tell you what the error is
