BizTalk and SMB FileShare

I have seen issues with different NAS devices not fully supporting SMB 2/3 protocols where files were locked incorrectly. When locking is not working correctly or if there is a network issue the file can incorrectly become unlocked, which is then picked up by BizTalk. BizTalk has been tested with Windows NTFS file system as mentioned also in documentation:
https://docs.microsoft.com/en-us/biztalk/core/file-adapter
https://docs.microsoft.com/en-us/biztalk/core/configure-the-file-adapter

Here are some tips which may avoid the issue:
- use temp file options in file adapter send port options so files are not available to others while in transit
- disable antivirus for the BizTalk process (BTSNTSvc*.exe, msdtc.exe, entsso.exe) and file locations used by BizTalk
- cluster receive and send file hosts so only one host instance is operating on the file at the same time
- ask producer of files (if other applications outside of BizTalk is producing the files) to use temp files and moving/renaming files when they are fully available

It can also be related to network issues.

Similar to SMB server, some NAS devices may also have tuning/configuration which can be optimised.

For those using Windows SMB server, this guide can be useful:
https://docs.microsoft.com/en-us/windows-server/administration/performance-tuning/role/file-server/smb-file-server

Troubleshooting tips/known issues:
https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/smb-known-issues
https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/troubleshooting-smb

Disabling SMB 2/3 may work if the NAS i successfully using SMB 1, but this is not recommended as it will cause the whole BizTalk server to use SMB 1, and it is strongly recommended to not use SMB 1 anymore: 
https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3
https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858