Micorsoft do a lot of interesting stuff to improve performance on their servers but invariably it is detrimental to traditional software that is based on file sharing.
We have written many articles on this but this is an update for Windows Server 2012 as it is getting widely used.
Again it is about SMB (Server Message Block)
The Server Message Block (SMB) protocol is a network file sharing protocol that allows applications on a computer to read and write to files and to request services from server programs in a computer network. Windows Server 2012 introduces the new 3.0 version of the SMB protocol.
While SMB3 enhances the performance of one type of database (client/server) it can introduce data integrity issues for other database types (file system/ISAM). DataEase is a file based system and it is our recommendation is that the server is reverted back to version 1.
Disabling Server Message Block version 3 on Windows Server 2012
Note: To complete the following steps you will need to be logged onto the Windows 2012 Server as an administrator
Windows Server 2012 introduces the new Set-SMBServerConfiguration Windows PowerShell cmdlet. The cmdlet enables you to enable or disable the SMBv1, SMBv2, and SMBv3 protocols on the server component.
Note: When you enable or disable SMBv2 in Windows 8 or in Windows Server 2012, SMBv3 is also enabled or disabled. This behaviour occurs because these protocols share the same stack.
You do not have to restart the computer after you run the Set-SMBServerConfiguration cmdlet.
? To obtain the current state of the SMB server protocol configuration, run the following cmdlet:
Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol
? To disable SMBv2 and SMBv3 on the SMB server, run the following cmdlet:
Set-SmbServerConfiguration -EnableSMB2Protocol $false
When you have done this open RegEdit and go to the following address
Make sure that the DependOnService is set to SamSS Srv rather than SamSS Srv2