Since this a specialized protocol, most systems don't use this, so it's quickest and less frustrating method to fix is to disable the protocol. To do this
- Go in sql server configuration manager
- Drill down under SQL Server Network Configuration | Protocols for MSSQLSERVER
- Disable VIA
- While in there for good measure disable VIA under Native client configuration
- Start SQL Server and it should work like a charm
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. Reason: Unable to initialize the VIA listener. The specified module could not be found.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The specified module could not be found.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
1 comment:
Fuck yeah, man. Thank you so much. I am having a headache with SQL Server this evening. I'm doing a homework assignment for my Web Applications class at Western Michigan University. Anyways, thanks so much. You have saved a little piece of the sanity of a Computer Science undergraduate.
Post a Comment