PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 01/23/2017 11:18 AM by  SurvivorAC
Security With DB Connection Failures
 0 Replies
Sort:
You are not authorized to post a reply.
Author Messages
SurvivorAC
Systems Analyst
Owensboro Health
Veteran Member
(221 points)
Veteran Member
Posts:105


Send Message:

--
01/23/2017 11:18 AM

    A couple of weeks ago, we had reports that the security was not not working properly.  We have the following in a rule:

    getDBFieldByIdx('EMPLOYEE','PROCESS-LEVEL','EMPSET1',COMPANY,EMPLOYEE)

    The reasoning for this piece is that employee information for employees in specific process levels is restricted to a small number of individuals.  The LASE and LADB logs were filling up with errors stating there was a database connection failure, and the error even points to getDBField.

     

    default.SEVERE author.runtime.JSRMFactory.getDBField()(): Exception when executing this function com.lawson.rdtech.opf.OPFRuntimeException:

    File /EMPLOYEE.

    tsFindMidRngDBRec error is Database error (94).

    Additional Text is:

    FindBegRngSqlRec(dbo."EMPLOYEE", 0)

    CMsfCSRSqlStatement::First(BNLF0536I00_V72) -

      SQL Server Error Code: 0, Source: Microsoft OLE DB Provider for SQL Server, Description: Connection failure

     

    Stack Trace : com.lawson.rdtech.opf.OPFRuntimeException:

    File /EMPLOYEE.

    tsFindMidRngDBRec error is Database error (94).

    Additional Text is:

    FindBegRngSqlRec(dbo."EMPLOYEE", 0)

    CMsfCSRSqlStatement::First(BNLF0536I00_V72) -

      SQL Server Error Code: 0, Source: Microsoft OLE DB Provider for SQL Server, Description: Connection failure


    The rest of Lawson seemed to be running fine.  Finance and materiels management users were running transactions with expected results.  Batch and report jobs were running and giving expected results.  The DB connection failure errors were only with the rule in security.  Because we run on VMs, we were told the issue was our VMware and given KBA 1200396.  We checked that out, and everything was fine (Snapshots off, VMs not moved, and NICs set up according to the KBA).  We restarted the system, and it was back to normal.  This has not happened since.

     

    I need to come up with a reason why there were database connection failures.  I would appreciate any suggestions.

    You are not authorized to post a reply.