Group model reports write locks that do not exist with SMB3
search cancel

Group model reports write locks that do not exist with SMB3

book

Article ID: 395460

calendar_today

Updated On:

Products

CA Plex

Issue/Introduction

User needs to update a CA Plex group model from his local model. 

The group model and the library models are connected by a network drive. 

There no write locks on the group and library models. The user exclusively uses the group and library models. 

On logging into the group and library models, write locks are reported. 

This happens only if the network protocol between the group model and the Plex workstation is SMB3.

The same setup using SMB1 or SMB2 succeeds.

Environment

CA Plex 7.2.1 and 7.3

Windows Server 2022 or Windows 2025
Network Protocol SMB3 between group model server and CA Plex workstation

 

Resolution

Check the Windows share's 'LeasingMode' properties.

To know the current leasing mode for the share(s):

1.  Launch Windows PowerShell

2.  Run the following command to obtain the current 'LeasingMode' setting for all shares

     Get-SmbShare | Select-Object Name, LeasingMode


     

You can query a specific share via the following command

Get-SmbShare -Name <ShareName> | Select-Object Name,
LeasingMode

To set/update a share's 'LeasingMode' setting:

1.  Launch Windows PowerShell

2.  Run the following command similar to the following

Set-SmbShare -Name <Share Name> -LeasingMode shared

Example: Set-SmbShare -Name GrpShare -LeasingMode shared

The above command sets the 'GrpShare' share's 'LeasingMode' to 'Shared'.

There are 3 leasing modes available,

  • Full: Use default lease and oplock behaviors from SMB3
  • Shared: Grant read-caching lease, but not write or handle-caching.
  • None: No oplocks or leases, behave like SMB1

Try to verify the locking issue with all above 'LeasingMode' (FULL, Shared and None) options for specific share that hosts Group models.

In most instances, setting the 'LeasingMode' setting to NONE will resolve the issue