v10 OnPremise MF Cobol-SafeNet Sentinel Errors

So we're an on premise client who completed our upgrade to v10 in December as a fresh install on new servers with a new database. Windows 2012 application servers (VM), 2012 SQL Server cluster. Production system goes down 3-4 times a week and errors point to the same issue each time but I'm an ex-functional consultant that knows enough tech to be a novice admin but that is the role my organization is asking me to fill at this time. Anyway, the issue manifests itself as Portal is up and users can inquire/submit but update actions (first in batch form) start failing and eventually even inquires will go down if we allow the issue to fester for an hour. Looking at submitted jobs the log will display an error of 'Cannot talk to the license server on host 127.0.0.1' or 'Licensing error cannot communicate with licensing daemon'. Looking at the Windows server event viewer the error observed occurring before each outage is an error message pertaining to lservnt.exe / ntdll.dll faulting application SafeNet Sentinel. That service is being used to validate the MF Visual Cobol license status and each time it appears to be the first warning that errors are occurring. Faulting application name: lservnt.exe, version: 8.5.1.17, time stamp: 0x4ec6addd Faulting module name: ntdll.dll, version: 6.3.9600.18233, time stamp: 0x56bb4e1d Exception code: 0xc0000005 Fault offset: 0x00077696 Faulting process id: 0x674 Faulting application start time: 0x01d288516c84b657 Faulting application path: C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT\lservnt.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 62d944a3-f4a1-11e6-815c-005056ad3852 Faulting package full name: Faulting package-relative application ID: Has anyone run into issues with SafeNet and MF Cobol licensing similar to this and if so did you find a resolution other than turn it off & on again or stop/start Lawson. It is definitely a volume related incident but it is not occurring at our peak usage hours so it's not a concurrent licensing issue but possibly a total licenses consumed over time or orphaned cobol licenses that aren't getting released properly. Thanks in advance for the feedback.