Leaving the hosts entry for the local server name in the hosts file pointed to 127.0.0.1 breaks the Workflow Manager Configuration Wizard if you ever try to get Workflow 2013 working in a farm created using autospinstaller.
I must have spent 30 hours on this issue for a client back in January, including an unresolved call with Microsoft where the rep eventually told me I should reinstall my farm. Never got the 2013 workflow going and just had to move on. Working on installing Workflow 2013 on a new farm today (that was also created using autospinstaller) and ran into the same issue. Searched for the error, found my previous thread on TechNet, and someone had responded saying to take out the server name hosts entry to 127.0.0.1. I thought no way... but that was it. After removing that entry (which was created by autospinstaller) the wizard ran and worked fine. Here's the thread for reference: http://social.msdn.microsoft.com/Forums/windowsazure/en-US/28918650-7913-45ef-bfdf-1b73f2eee1cb/cannot-configure-workflow-manager?prof=required
Comments: ** Comment from web user: brianlala **
I must have spent 30 hours on this issue for a client back in January, including an unresolved call with Microsoft where the rep eventually told me I should reinstall my farm. Never got the 2013 workflow going and just had to move on. Working on installing Workflow 2013 on a new farm today (that was also created using autospinstaller) and ran into the same issue. Searched for the error, found my previous thread on TechNet, and someone had responded saying to take out the server name hosts entry to 127.0.0.1. I thought no way... but that was it. After removing that entry (which was created by autospinstaller) the wizard ran and worked fine. Here's the thread for reference: http://social.msdn.microsoft.com/Forums/windowsazure/en-US/28918650-7913-45ef-bfdf-1b73f2eee1cb/cannot-configure-workflow-manager?prof=required
Comments: ** Comment from web user: brianlala **
The only way the server name would have been added to the local HOSTS file is if it was used in one of your URLs - which is a no-no. Therefore, avoid using machine names in your URLs, and instead use non-machine FQDNs (they don't even have to exist in DNS at script run-time either).
However I'll look into adding a check in the AddToHOSTS function to avoid adding local computer names to the HOSTS file altogether.
Brian
