![]() 18233, time stamp: 0x56bb4e1dįaulting application start time: 0x01d288516c84b657įaulting application path: C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT\lservnt.exeįaulting module path: C:\Windows\SYSTEM32\ntdll.dll ![]() 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.įaulting application name: lservnt.exe, version: 8.5.1.17, time stamp: 0x4ec6adddįaulting module name: ntdll.dll, version. 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. 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'. 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. 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. Windows 2012 application servers (VM), 2012 SQL Server cluster. ![]() ![]() 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |