SharePoint 2013/SharePoint 2016 – Applying Cumulative Update removes all users with db_owner

Hey All – Recently ran into an issue where a customer had AvePoint installed in the farm (Which requires the DocAve account to have db_owner) and after every CU it’d remove an user that was manually granted db_owner. This is actually a security measure in place to make sure there isn’t an errant account left with db_owner permissions on the database. There are times when we want that account to stay (For things like third party tools or RBS..though they should find a way to use SP_DATA_ACCESS instead!) There is a registry key BypassDboDropMember that was added to SP2013 in the October 2016 CU and to SP2016 in the October 2017 CU (Note: You will need to be on these CU levels to gain access to this functionality) for bypassing this behavior:

Instructions For SP2013 (From link above):

Note: For SP2016 just change the registry subkey to 16.0

  1. After you install this update, you can follow these steps to control the metafiles optimization:
    Start Registry Editor:

    • In Windows Server 2012, if you’re using a mouse, move it to the upper-right corner, go to Search, enter regedit in the search text box, and then select regedit.exe in the search results.
    • In Windows Server 2008, go to Start, enter regedit in the Search programs and files text box, and then select regedit.exe in the search results.
  2. Locate and then select the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\
  3. On the Edit menu, point to New, and then select DWORD Value.
  4. Enter BypassDboDropMember, and then press the Enter key.
  5. In the Details pane, press and hold (or right-click) BypassDboDropMember, and then select Modify.
    In the Value data box, enter 1, and then select OK.
    Note If you don’t want to bypass the behavior, you can set the value to 0.
  6. Exit Registry Editor.

SharePoint 2013 SP1 – Windows Server 2012 R2 Prereq Install Error

So I got my hands on the SharePoint 2013 w/ SP1 ISO as well as a shiny new Windows Server 2012 R2 ISO and decided to give it a go! I installed Server 2012 R2 (Return of the shiny “start” button in the lower left), then installed SQL 2012 w/ SP1, and then moved on to SharePoint 2013 SP1. I fired up the splash screen and chose to install the Prerequisites…Good news is IIS installed/configured on the first attempt. In Server 2012 RTM there was a bug where sometimes IIS would fail to configure and you would have to install IIS manually and then let the prerequisite installer configure it appropriately. I DID get an install error though! This time the culprit is the Microsoft Information Protection and Control Client. I tried rebooting a few different times and could not get it to install so I decided to give an offline install a whirl.

You can download the install file for the Protections and Control Client here:

After downloading setup_msipc_x64.msi save it somewhere on the SharePoint server.

Then open CMD and type the following commands (If the CD drive is different than D change the directory to that drive letter):

After this you will be all set!


Also, my last post talked about installing SP1 after installing RTM + March 2013 PU…I did find one other difference with the ISO. The yellow bar at the top for Yammer/Office 365 is green if you install with the SP2013 SP1 Iso! Check it out:



SharePoint 2013 – Service Pack 1

SharePoint 2013 SP1 has been released! I’m a day late…so this isn’t exactly hot off the press

Check out the new addition to the Central Administration menu! SharePoint got Yammered..



Testing Notes: I setup a SharePoint 2013 Server (Windows Server 2012 RTM/SQL Server 2012 SP1) Farm to test out Service Pack 1 and what it brings to the table. This was a fresh installation – installed the Server OS > installed SQL 2012 > installed SP2013 RTM bits > upgraded to March 2013 PU bits > upgraded to SP1 bits > ran config wizard.

The Bad:

  1.  The Document Conversions Load Balancer Service appears to be in a state where it will NOT start: (NOTE: This also happened using a SP2013 SP1 ISO)ServicesOnServerErrorLB
    1. I am able to click the LB Service link, which brings me to the settings page
    2. LBSettings
    3. But when I click Start I get redirected to this error page:
    4. Error Starting Load Balancer
    5. UPDATE – As mentioned in the comments by Tuppence Weix, this can be fixed with the following PowerShell command:
  2. Also, apparently Yammer and OneDrive for business are critical issues (You can just click the X to close)
  3. YammerO365CriticalError

The Good:

  1. When creating a new User Profile Service Application you are presented with the option to use Yammer for Social Collaboration!
  2. SP1UPSCreation
  3. This adds  the following entry to the navigation bar (Starting to look more and more like O365):
  4. SP1NavBarYammer
    1. Clicking Yammer Redirects to http://webappurl/_layouts/15/Yammer.aspx
    2. sp1clickyammer
    3. Clicking TAKE ME TO YAMMER redirects to
  5. By clicking the Office 365 link on the left (Current) navigation in Central Administration you can configure Yammer (Which is just an activate/deactivate functionality for the link in the navigation bar..discussed above) and you can configure Office 365 settings for the OneDrive and Sites links in the top navigation bar.
  6. This is the screen you are presented with..pretty cool! I actually just worked on a project where we deployed an IIS HTTP Handler to rewrite URL’s to an Office 365 tenant…now this functionality is baked into SharePoint
  7. OneDriveConfigSP1
  8. I did some testing by typing in my trial Office 365 tenant so I could play around here.
  9. After clicking OK the change was nearly instant (I did need to clear browser cache in IE..but I tested in Firefox/Chrome right away which I wasn’t previously authenticated to the SharePoint site and the links were updated within a matter of seconds).
  10. Clicking  OneDrive and Sites Redirected Perfectly!
  11.   OneDriveO365Redirect
  12. For every good thing there is a bad thing though. The About Me link still redirects to the On Premise MySite Host…This is OK because most of the content here is directly synchronized from Active Directory, which makes the profile pages On Prem/Office 365 very similar (minus manually typed in information – Skills, About Me, Ask Me About, etc.). If the user had permissions within the UPS to create a personal site and has ALREADY done so..the links to that On Prem personal site collection will still show as links on the left-hand side. If you are looking for a truly hybrid environment there will need to be settings adjustments to lock down users being redirected to Office 365 (UPS Permissions settings, Decide if you want to use audiencing/targeting to send some user on prem/some users to Office 365, etc.
  13. Just note setting these features in Central Admin to redirect users to an Office 365 tenant will not change user permissions settings in the UPS (This is very similar to using Trusted MySite Locations pre-SP1…and then using audiencing to route specific users to the MySite Tenant. In the past you could point a MySite Location at an Office 365 tenant, but the About Me link would be broke (User Not Found) and when clicking on a people column containing that user it would give the same error (Because the URL structure after person.aspx is different for on premise and Office 365..Hence the need for a HTTP Handler or some other form of URL redirect). Otherwise you may end up managing personal site collections on prem, when these users actually have storage in Office 365.
  14. MyProfile

SharePoint 2010 Service Pack 2 – Server 2012 Support

Short and sweet here. If you want to install SharePoint 2010 on a Server 2012 machine you need to go to MSDN and grab the updated ISO. This new ISO file has updated installers (prerequisites included) that now support Windows Server 2012. A slipstreamed install with previous releases will not work like you want it to. If you do not grab the new ISO and you want SharePoint 2010 on a Server 2012 machine take a look at the steps needed to get that done: This is a great post by Trevor Seward, but I’d definitely rather just have it work out of the box.


Applying March 2013 PU – BdcServiceDatabase is not upgraded

After applying the March 2013 PU for SharePoint 2013 you may notice that the BdcServiceDatabase has the following status “Database is in compatibility range and upgrade is recommended.” This can be seen by going to Central Admin | Upgrade & Migration | Review database status. You may also see the following Health Analyzer Problem:


This can be fixed easily by running the following PowerShell command: