Windows Server 2016: Shared Access Database Getting Corrupt on SMB

Hi everyone

Today less and less people use msaccess, but some still, and some still use multiuser database.

In such case after Windows 2008 R2 it can cause problem with new layer of SMB version, that allow oplock to be used, thus it can cause bug from the Access GUI, or even corruption of the data file.

To disable, on the server :


OplocksDisabled REG_DWORD 0 or 1
Default: 0 (not disabled)


EnableOplocks REG_DWORD 0 or 1
Default: 1 (enabled)

To be disabled at 100% let’s do the client’s computers too. Easily with a GPO



Exchange 2016 – You don’t have permission to perform this action (OWA)


If you receive the error You don’t have permission to perform this action while any user try to send an email, then you are in big trouble..

2-5-2018 10-18-14 AM

Just kidding.

Some FAQ tell to go check the server DNS setting, to be sure it’s only internal’s DNS server listed there, but I found another cause for that problem.

It can happen when you do a CU (Cummulative Update) and the service get stuck in a Inactive state. No windows event log are logged too when such happen and your receive connector can still connect on port 25, but the server just look to do nothing.

To validate please run that powershell commandlet;


You can see some component in inactive state;

2-5-2018 3-54-02 PM

At this point you can put each component active, by issuing that command;

Set-ServerComponentState -Identity ServerName -Component HubTransport -State Active -Requester Functional

After all component are active it should be listed more like that;

2-5-2018 3-54-27 PM