I have a development environment where I have Workflow manager 1.0 installed on the same server as Visual Studio. Immediately after VS 2013 was installed all of the workflows suspended and showed the initiator as Anonymous. When it originally occurred my only solution was at the time to reinstall Workfow Manager. As soon I reinstalled it the workflows went back to normal. Recently we installed VS2015 and the same issue occurred. After this I was able to install the latest CU and the workflows started working once again.
This time Office Developer Tools 2015 was installed and the workflows show the correct initiator but when they run they suspend with a 401 error. These workflows worked immediately before the office tools were installed.
I'm hoping someone might have a clue as to why installing these would cause the associations to change and permissions to now be denied.
Jennifer Knight (MCITP, MCPD)