In last days i got some problems on SharePoint 2016 Farms, when we tried to create new service applications using the Central Administration and/or Powershell scripts. The UI was working on it and this took very long without that anything happened. The Service Application stucks on starting/ending.
The Service Application status was stucking on Starting
What we tried then:
- provisioning and unprovisioning like this post recommends.
- Stop and Start the service via Powershell like in this post.
We also updated the farm with the latest Cumulative Update. After running the PSConfig Wizard the state changed to started. But the next Service Application we created had the same problem.
Until now, we don’t know exactly the reason. But we found a solution which helped us.
Empty the Timer Service Cache
So first we stopped the service SharePoint Administration and the SharePoint Timer service
Then we went to C:\ProgramData\Microsoft\SharePoint\Config\<guid>\ and deleted everything except the cache.ini file. We edit the cache.ini file and replace the number in it by a “1”.
After that we start again the SharePoint Adminstration and SharePoint Timer Service. It take some minutes and the cache gets refilled.
Then we used Powershell to provision the service application.
$serviceapplication = Get-SPServiceApplication -Identity <Guid>
That did the trick.
Unfortunately we had to do this each time we changed a service application. Is it possible that the root cause is Cumulative Update in SharePoint 2016? Does anyone made the same experiences?