SharePoint 2016 July 2018 PU Configuration Failure

The July 2018 PU for SharePoint 2016 has this fix in it which comes from a long standing bug:

When a farm administrator creates a search service application by using PowerShell, the database owner of the search service application database is the farm administrator and not the farm account that is used to run the timer service. The database owner of all databases should be the farm account. This update changes the owner of search-related databases to be the farm account.

The fix is self explanatory, except it doesn’t work. It will cause this failure when running the Config Wizard after installation, provided you have indeed created the Search Service Application via PowerShell with a user other than the timer service account, which of course is best practice.

Ultimately this will not impact Search functionality and can be ignored. All Search components should be in a healthy state post-Config Wizard run. Due to the failure of the Config Wizard, make sure to run iisreset /start on all of your SharePoint servers post-update as the IIS sites will likely be in a stopped state.

This will hopefully be resolved in a future update.


  1. Thanks Microsoft :( I have been fighting this since last week, was just about to rebuild my Search application. Thank you!

  2. Many thanks Trevor. Just faced this issue on some customers farm after installing the July18 patch through Windows Update. Already started troubleshooting and investigating til I’ve found your blog post. I’m glad to see that this can be ignored, so I stop working now and grab a beer :) Cheers!

  3. After installing this update in my test farm, all three servers hang when running psconfig on step 8 of 10. It will sit for hours, if you hit cancel, it too will sit for hours. I have yet to get past this! Any idea?

  4. Andrew J. Federico, Jr.

    Thank you, Trevor. It looks like when it fails on 7 of 7, it leaves the status in Upgrade Available, which can be seen in CA. Is that the same thing you are seeing?
    I assume running next month’s update will resolve this.

  5. If it helps, my issue above was with a KB that broke IIS, if you issued a stop or reset command it wouldn’t come back up, and stayed stuck in stopping…Ms broke this with an important update, and fixed it with an optional. The link below goes back to 2008, but was updated recently to announce the issue was back.

    Installing the optional update fixed the issue.

  6. Mephistopheles Jones

    What is the issue this fix, changing the search db owners, is trying to resolve? All my dbs are owned by my sp_install account, not just the search dbs.

    • Mephistopheles Jones

      Nevermind. Your linked to the issue at the top of your article. So it seems granting your Farm account db_owner role on your search dbs will prevent the 2014 bug, but not prevent the 7/18 PU failure.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.