I am having an issue with a SharePoint 2013 workflow not working when the “Send Email” action is utilized. Every other part of the workflow is working as it should.
The error I get is: RequestorId: f44ac52a-0202-dafe-d2f7-400168d2e1bb. Details: System.ApplicationException: HTTP 400 {“Transfer-Encoding”:[“chunked”],”X-SharePointHealthScore”:[“0”],
It appears that the request does not even make it to the SMTP server. It hits that action and cancels.
I have configured workflow manager. The User Profile services and synch are running fine. The FIM services are running fine along with the Service bus services. I had this working for a short period of time and then it stopped working. I originally thought that this may be a permissions error but as the User profile services and all the other services running under this account are running properly that makes me think that it is something else.
I am not running the workflow under system account.
I have tried running the workflow under other accounts and get the same result.
Has anyone else had this error? If so what did you do to resolve it? Any help is appreciated!
I had the 400 error and I fixed it…..
I ran these powershell commands on the root site collection
get-spuser -web http://sitecollection | select DisplayName, ID
This gave me the ID of the user I was using in the workflow where email was being sent….
$user = Get-SPUser -Web http://sitecollection -Identity {Id}
replace {d} with the number of ID field you got from the previous command.
Now you can update the email address:
$user.Email = “abc@abc.com”
$user.Update()
Note: Outside email addresses are not allowed with SP 2013 workflow it seems – the email address has to resolve to a user or a name of SP Group in the site collection or else your workflow will fail. I have not tried this with AD group yet.
Does your workflow account have all of the proper permissions? Can you do anything else with the workflows, (ex. write something to a list)?
User Profile Service & Sync work well.. UPS also has proper email addresses..
Also, I have tried any combination for the email parameters.
Is your user profile service and sync up and running? Have you tried hard-coding an actual email address into the field? In your user profile sync, do you have email addresses being brought back?
Well things have gone from bad to worse…. I no longer receive the 400 error. I now am receiving a 401 error that looks like this:
RequestorId: 63a9f880-d461-703d-93dc-4712507b06b9. Details: System.ApplicationException: HTTP 401 {“x-ms-diagnostics”:[“3000006;reason=\”Token contains invalid signature.\”;category=\”invalid_client\””].
I receive this error after uninstalling and re-installing workflow manager. I am going mad trying to get this working! We have a single farm, so going the Kerberos route is not something that I want to do.
Has anyone gotten this issue and gotten past it without Kerberos? The User Profile Service and Sync is working great! Its just the workflows.
Please help!
