Getting Error 945 Severity Level 16 Message Text Database '%.*ls' cannot be opened due to inaccessible files when starting SQL service

Potential Symptoms

  • Getting  Error 945 Severity Level 16 Message Text Database '%.*ls' cannot be opened due to inaccessible files when starting SQL service.
  • Service will not start
  • Error Logs look like the following
    2016-05-11 11:37:39.65 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/corpws030.tpi.townpump.com:NUCLEUS ] for the SQL Server service. Windows return code: 0x200b, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.

    2016-05-11 11:37:39.69 spid7s      Error: 17204, Severity: 16, State: 1.
    2016-05-11 11:37:39.69 spid7s      FCB::Open failed: Could not open file E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf for file number 1.  OS error: 21(The device is not ready.).
    2016-05-11 11:37:39.69 spid7s      Error: 5120, Severity: 16, State: 101.
    2016-05-11 11:37:39.69 spid7s      Unable to open the physical file "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf". Operating system error 21: "21(The device is not ready.)".
    2016-05-11 11:37:39.75 spid11s     Error: 17204, Severity: 16, State: 1.
    2016-05-11 11:37:39.75 spid11s     FCB::Open failed: Could not open file E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\model.mdf for file number 1.  OS error: 21(The device is not ready.).
    2016-05-11 11:37:39.76 spid11s     Error: 5120, Severity: 16, State: 101.
    2016-05-11 11:37:39.76 spid11s     Unable to open the physical file "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\model.mdf". Operating system error 21: "21(The device is not ready.)".
    2016-05-11 11:37:40.01 spid7s      Error: 17207, Severity: 16, State: 1.
    2016-05-11 11:37:40.01 spid7s      FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
    2016-05-11 11:37:40.01 spid7s      File activation failure. The physical file name "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf" may be incorrect.
    2016-05-11 11:37:40.05 spid11s     Error: 17207, Severity: 16, State: 1.
    2016-05-11 11:37:40.05 spid11s     FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
    2016-05-11 11:37:40.06 spid11s     File activation failure. The physical file name "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\modellog.ldf" may be incorrect.
    2016-05-11 11:37:40.06 spid11s     Error: 945, Severity: 14, State: 2.
    2016-05-11 11:37:40.06 spid11s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
    2016-05-11 11:37:40.06 spid11s     SQL Server shutdown has been initiated
    2016-05-11 11:37:40.06 spid11s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

 

  • You may see an error such as this:
    • "Database 'Nucleus Database' cannot be opened due to inaccessible files or insufficient memory or disk space. See SQL Server errorlog for details."

     Databaseerror.jpg

     

    Environment

    • Product Family: Software
    • Product: Venus 1500 v4
    • Component: MSSQL  2014
    • Control System:

    Cause

    • Installation put files in an incorrect path and cannot open them.

    Resolution

    KB ID: DD3357386


    DISCLAIMER: Use of this content may void the equipment warranty, please read the disclaimer prior to performing any service of the equipment.

    DAKTRONICS DOES NOT PROMISE THAT THE CONTENT PROVIDED HEREIN IS ERROR-FREE OR THAT ANY DEFECTS WILL BE CORRECTED, OR THAT YOUR USE OF THE CONTENT WILL PROVIDE SPECIFIC RESULTS. THE CONTENT IS DELIVERED ON AN "AS-IS" AND "AS-AVAILABLE" BASIS. ALL INFORMATION PROVIDED IN THIS ARTICLE IS SUBJECT TO CHANGE WITHOUT NOTICE. DAKTRONICS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. DAKTRONICS DISCLAIMS ANY AND ALL LIABILITY FOR THE ACTS, OMISSIONS AND CONDUCT OF YOU OR ANY THIRD PARTIES IN CONNECTION WITH OR RELATED TO YOUR USE OF THE CONTENT. ADJUSTMENT, REPAIR, OR SERVICE OF THE EQUIPMENT BY ANYONE OTHER THAN DAKTRONICS OR ITS AUTHORIZED REPAIR AGENTS MAY VOID THE EQUIPMENT WARRANTY. YOU ASSUME TOTAL RESPONSIBILITY FOR YOUR USE OF THE CONTENT AND ANY LINKED CONTENT. YOUR SOLE REMEDY AGAINST DAKTRONICS FOR DISSATISFACTION WITH THE CONTENT IS TO STOP USING THE CONTENT. THIS LIMITATION OF RELIEF IS A PART OF THE BARGAIN BETWEEN THE PARTIES.

    The above disclaimer applies to any property damage, equipment failure, liability, infringement, or personal injury claim arising out of or in any way related to your use or application of the content, whether such claim is for breach of contract, tort, negligence or any other cause of action.