Has anyone had issues when using the autobuild script to install SharePoint 2016, the creation of some service accounts hang?
It is generally completely random on if a service application will hang when being created but it is usually happens on the word automation service application, the machine translation service application, or the app management service application.
This does not happen at all with SharePoint 2013. The workaround I have discovered is just to open central admin while the script is still running and delete the hung service application. I then get a error such as:
An update conflict has occurred, and you must re-try this action. The object
WordServiceApplication Name=Word Automation Services was updated by SHAREPOINT\USER, in the w3wp (3320) process,
on machine TEST. View the tracing log for more information about the conflict.
But then the script will continue on creating the other service applications with no problem.
So it seems like me may be related to config cache issues.
If anyone else has seen this or has any recommendations on how it can be fixed?