OLE DB Connection Failure

Hi All, hope somebody can shed some light on this.  Yesterday we seen these messages in the logs.   We lost connection to the SQL DB.   Cannot find no reason on why the connection would have dropped.    This dropped all activity to Lawson, IPA etc.  No Body could login etc.   After about 20 minutes of digging around and trying to find out what is going on, the connection was restored.   I did end up cycling the Lawson servers the next day, because we had people that could not login to Lawson. 

Has anybody seen this error, and where to look for the cause.   

I checked the Event logs on both the LSF server and LMK server along with the Database server and nothing there.   Windows/SQL env.

Any ideas would be appreciated.  

Thanks

Terry

From Lawson Ladb.log

*** begin msfdb2000 error message ***

FINDMIDRNGDBREC() error on file 'EMPLOYEE' in 'PROD'

FindBegRngSqlRec(dbo."EMPLOYEE", 0)

CMsfCSRSqlStatement::First(BNLF0001I00_V72) -

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

---------------------------------------------------------------------------------------------------------

One of the running jobs:

File PROD/TIMERECORD.

FindNltDBRec error is Database error (94).

Additional Text is:

FindBegRngSqlRec(dbo."TIMERECORD", 9)

CMsfCSRSqlStatement::First(BNLF0001I09_V36) -

  SQL Server Error Code: 11, Source: Microsoft OLE DB Provider for SQL Server, Description: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.

INFORMATION FROM THE LATM.LOG

in config, using default

Sun Jul 09 04:41:51 2017: latm (ConfigLatm): NICE not specified in config, using default

Sun Jul 09 04:41:51 2017: No remote nodes loaded.

Sun Jul 09 04:41:51 2017: latm (main): Transaction Manager Ready.

Mon Jul 10 16:42:52 2017: latm (PrcTPCrash): Received death notification of lacobrts, Uid=4, Pid=10516

Mon Jul 10 16:42:52 2017:                  Program Code = PR45 , DataArea/DataID = PROD         

Mon Jul 10 16:42:52 2017: ERROR:    Exited with error code 1

lacobrts timed out waiting for OPEN message

lacobrts timed out waiting for OPEN message