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

randy-powell

For the last 3 plus months. We have been getting the following error on the application server, SQL Server Error Code: 0, Source: Microsoft OLE DB Provider for SQL Server, Description: Connection failure.

Thus far we have not been able to pin down the root cause. It does appear the application server drops the connection with the database server. The only way for us to recover from the problem is to reboot the application server.

We have turned of some SQL data base processes in hopes of tracking done the cause. We have turned off incremental SQL backups and moved to one backup per night with no luck. I see others have increased their SQL connections as well. 

Does anyone know or recall if the application has a config file with the named database server or if you have to put a domain controller name in a config file? The problems makes me wondr about a DNS resolution issue.

Has anyone at least found a solution? And of course the network team says there is not a problem?

richardd

I remember this issue from several years ago.  It ended up being caused by VMWare.

KB 1200369
SQL: SQL Server Error Code: 0, Source: Microsoft OLE DB Provider for SQL Server, Description: Connection failure
Description:
I am receiving errors sporadically in the ladb.log file similar to:
FindSqlRec(dbo.EMPLOYEE, 0) CMsfCSRSqlStatement::First(FNRF0000I00_V00) -SQL Server Error Code: 0, Source: Microsoft OLE DB Provider for SQL Server, Description: Connection failure.
Why am I getting these errors and can this be fixed?
Resolution:
This error message is strictly outside of Lawson and most likely related to running on VMware. One or a combination of the following tips may help to resolve the issue:
1. Turn off VM Snapshots. 2. Do not allow the VMs to be automatically moved through Vmotion from one VMhost to another. 3. Investigate possible NIC card driver issues. Make sure you are using the VM NIC card drivers and not vendor NIC card drivers.
Disclaimer Infor does not support VMware software, and the following articles come from VMware's website. If there are any questions regarding these articles, open up a support incident with VMware and not Infor.
If you are running on Vsphere 5.5 this article pertains to the NIC card settings, again any questions on what the settings need to be, will have to be answered by Vmware support
www.vmware.com/.../VMW-Tuning-Latency-Sensitive-Workloads.pdf
ethernetX.coalescingScheme monitor_control.halt_desched monitor.idleLoopSpinBeforeHalt
If you are running on Vsphere 6.x and have not applied update 2, review this article on
Understanding TCP Segmentation Offload (TSO) and Large Receive Offload (LRO) in a VMware environment
kb.vmware.com/.../search.do
Another article that VM Admins will want to review
Large packet loss at the guest operating system level on the VMXNET3 vNIC in ESXi
kb.vmware.com/.../search.do language=en_US&cmd=displayKC&externalId=2039495
Note: -We recommend that you open a Microsoft Support incident for the following error message: DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
-Old solution posted in this article: Root Cause: We found in this instance that the client had the Lawson environment running on a Windows 2003 server connecting to a remote Sql Server 2005 database server which was in turn running Windows 2003. Sporadically, the
Page 1 of 2
10/9/2017www.inforxtreme.com/.../solutions /SoHoView...
client received errors in the ladb.log file about connection lost, at the same time, on the Lawson server, an event viewer message would appear: NT AUTHORITYSYSTEM Ladb.exe Kill – CreateRemoteThread Not enough storage is available to process this command Suggestion: We found a Microsoft KB that addresses the "Not enough storage is available to process this command" message. support.microsoft.com/ If this article does not resolve your issue, contact Microsoft Support.
Affected Products & Releases
Affected Product Affected Release Patch Status Notes
Lawson System Foundation 9.0.0.0
Lawson Core Technology 9.0.0.0
Lawson Core Technology 9.0.1.0
Lawson System Foundation 10.0.0.0
Lawson System Foundation 9.0.1.0
Recommended Articles for Products :
Recommended Articles for Releases :
Keywords : create remote thread
Type : Knowledge
Classification :
JT-Number/Reference Number :
AR_5429695
Severity : 3 - Medium
Status : Complete
Last Updated : 22 Nov 2016
Platform : Windows
Created: 01 Jan 2000 06:00
Revised: 22 Nov 2016 14:23
File Attachments :
No Attachments for this KB
Linked KBs :
No Linked KB's for this KB
Page 2 of 2
10/9/2017www.inforxtreme.com/.../solutions