PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 09/12/2017 11:12 AM by  JimY
v10 OnPremise MF Cobol-SafeNet Sentinel Errors
 6 Replies
Sort:
You are not authorized to post a reply.
Author Messages
SWilkins
Mgr Administrative Systems
Phoenix Children's Hospital
Basic Member
(27 points)
Basic Member
Posts:11


Send Message:

--
02/20/2017 10:17 AM
    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.
    Brian Allen
    Private
    Private
    Veteran Member
    (276 points)
    Veteran Member
    Posts:94


    Send Message:

    --
    02/20/2017 11:06 AM
    We are not having an issue with that combination, but we're on Oracle 11gR2. We will not be live on v10 until April. Let us know if you find any other details on this issue.
    JimY
    Private
    Private
    Veteran Member
    (1089 points)
    Veteran Member
    Posts:389


    Send Message:

    --
    02/20/2017 11:17 AM
    I have never heard of SafeNet Sentinel. Does it come with the MF install or is it something you installed? We are in the process of going from 2008 servers to 2012 servers and we haven't run into that. Have you contacted Infor Support? Curious what they have to say.
    SWilkins
    Mgr Administrative Systems
    Phoenix Children's Hospital
    Basic Member
    (27 points)
    Basic Member
    Posts:11


    Send Message:

    --
    02/20/2017 11:36 AM
    Back in December when this first occurred Lawson referred me to KB 1824034 and we followed those instructions but the issues have continued. SafeNet Sentinel is part of the MicroFocus Visual Cobol install and it's used to in conjunction with that license. Could be something specific with our network security that is preventing that tool from making calls out to verify licensing status since we're pretty serious about keeping our servers secured here but figured maybe someone would of run into the issue and a resolution.
    Brad Schauer
    Private
    Private
    Veteran Member
    (222 points)
    Veteran Member
    Posts:76


    Send Message:

    --
    09/11/2017 10:45 AM
    Did you find a solution to this issue?
    SWilkins
    Mgr Administrative Systems
    Phoenix Children's Hospital
    Basic Member
    (27 points)
    Basic Member
    Posts:11


    Send Message:

    --
    09/11/2017 3:12 PM
    No a root cause/fix was never found. We've just adopted what seems to be the norm for Windows/SQL clients these days and we reboot the VM weekly during the low use overnight hours which prevents the errors from occurring.
    JimY
    Private
    Private
    Veteran Member
    (1089 points)
    Veteran Member
    Posts:389


    Send Message:

    --
    09/12/2017 11:12 AM
    We reboot Landmark and LSF every two weeks.
    You are not authorized to post a reply.