Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 1 down vote favorite

I am a newbie when it comes to server configuration and maintenance. I installed a copy of SharePoint 2013 for evaluation purposes and got everything up and running okay, but have run into issues installing/configuring the 2013 workflows.

I have followed all of the instructions here: http://technet.microsoft.com/en-us/library/jj658588.aspx and have also reviewed several other blogs and instructions to try and answer my question, but have had no luck.

I am able to install the Workflow Management Site with no issues, but I run into a problem when I try and "register" the workflow to the site collection using the Register-SPWorkflowService cmdlet.

Here is the cmdlet I am running:

Register-SPWorkflowService -SPSite "http://00.000.00.0/sites/sandbox" -WorkflowHostUri "http://workflow.00.000.00.0:12291" -AllowOAuthHttp

Here is a portion of the error I am receiving:

Register-SPWorkflowService : A response was returned that did not come from the Workflow Manager. Status code = 401: HTTP headers received from the server - WWW-Authenticate: Negotiate,NTLM.

So obviously I am seeing here that there is an authentication problem, but after dozens of google searches I am not finding anything that specifically speaks to authentication errors while running this cmdlet.

I am totally at a loss and have spent more than a day working on this. Thank you in advance for your help! :)

share|improve this question

1 Answer

up vote 0 down vote

I am not sure what you wanted to say by 

http://workflow.00.000.00.0:12291

but if you really added not only server name, but also "workflow" before it that could be the cause of the issue. Also, try to add "-Force" parameter at the end.

share|improve this answer
Hi @MikhailSP, Thank you for the response! I also was confused where the "workflow" came in, but every example I found online included the 'workflow' before the domain. I tried removing it and I get a 400 "Bad Response" error instead of an "Authorization" error. I also tried using the -Force parameter per your suggestion, but received the same error. – Sunburnt Ginger May 2 at 20:22
If you are using IP address of the server instead of its name, try to use its name. If it doesn't help, please provide us the full error mesage, please. – MikhailSP May 2 at 20:27

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.