SQL Server Instance failing to start

  • I am seeing below errors in the error log. I tried every option but same issue. Need your suggestions.

    2011-08-30 17:42:59.66 Server Error: 26055, Severity: 16, State: 1.

    2011-08-30 17:42:59.66 Server 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.

    2011-08-30 17:42:59.69 Server Error: 17182, Severity: 16, State: 1.

    2011-08-30 17:42:59.69 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: Unable to initialize the VIA listener. The specified module could not be found.

    2011-08-30 17:42:59.70 Server Error: 17182, Severity: 16, State: 1.

    2011-08-30 17:42:59.70 Server 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.

    2011-08-30 17:42:59.70 Server Error: 17826, Severity: 18, State: 3.

    2011-08-30 17:42:59.70 Server 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.

    2011-08-30 17:42:59.72 Server Error: 17120, Severity: 16, State: 1.

    2011-08-30 17:42:59.72 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    Thanks

  • have you checked the Windows application log

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • I found this.

    FCB::Open failed: Could not open file D:\SQL Server\MSSQL10.SQL2K8\MSSQL\DATA\model.mdf for file number 1.

  • so, verify the path and filename 😉

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Everything is ok. Path is pretty much accessible.

  • check the permissions, they should contain ACLs for the sql server service account.

    If sql server cant open model it cant create tempdb and so, wont start!

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply