My every interaction with client teaches me something new. Recently someone contacted me through email and informed that they have issues with SQL Server Startup. When we checked ERRORLOG, we found below messages at the end of the ERRORLOG where Via Support library was mentioned.
The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.
TDSSNIClient initialization failed with error 0x7e, status code 0x60.
TDSSNIClient initialization failed with error 0x7e, status code 0x1.
I asked them to check SQL Server configuration manager and look for the Protocols enabled for that instance of SQL Server. As per error message, it caused due to VIA protocol. Sure enough, it was enabled.
We disabled VIA protocols using the SQL Server Configuration Manager. In the highlighted section, right click and choose disable.
On a side note, when I checked SQL Server 2016 configuration manager, I found that this is already removed from the product.
Here are a few blog posts which I have written on this subject you may find them helpful as well.
- SQL SERVER – Connecting to Azure Storage with SSMS
- SQL SERVER – How to Connect Using NT AUTHORITY \ SYSTEM Account?
- SQL SERVER – Connecting to Azure SQL DB
Reference: Pinal Dave (http://blog.SQLAuthority.com)