Error Message: Sys License Count Exceeded when two users access any package

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system.  Use Registry Editor at your own risk.

Disable Opportunistic Locking on the Db server by completing one of the options below:

1. Open Regedit on the Database Server

2. Find the Following Key: [HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]

3. Create the following two new dword entries with the respective vaules:

     EnableOpLockForceClose=dword:00000001
     EnableOpLocks=dword:00000000

1. Restart the Database Server

2. Retest the License Problem

--or-- 

1. Run the Disable_OpLocks.reg file on the AGRIS database server.  The file can be found by browsing to 

https://ftp.agris.com/TACTools/

1. Restart the Database Server

2. Retest the License Problem

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system.  Use Registry Editor at your own risk.

This affects Windows Server operating systems.  The resolution described above is the same for Windows 2000 Server, Windows Server 2003 and Windows Server 2008 as all of these operating systems reference the same exact location in the registry for OpLocks.  

NOTE:  In very rare cases the "Sys License Count Exceeded" has been traced to a permission problem where users might not have full rights to the AGRIS\Datasets\Status.AGR file on the database server.  In such instances, it may be necessary to reset permissions and ownership to the Apps folder where AGRIS resides.

Comments

• It seems that a license count exceeded error can be related to PSQL 3112 errors based on a recent customer issue. So the issue may not be a valid license issue, or an OpLocks issue, but a network problem. A 3112 error is 'failure during receive from target server.' The Pervasive Auto-Reconnect (PARC) feature my help prevent network issues from resulting in errors. It is important to note that the best solution would be to identify and correct the network issue, though such troubleshooting can prove extremely difficult as the errors are transient.