Search

Saturday, April 7, 2012

SQL Doesn't start and Event ID = 17204

After hardening a server, the service didn't start anymore and I found the following error:

Event ID = 17204
FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\DemoData.ldf for file number 2. OS error: 5(failed to retrieve text for this error. Reason: 15105).

Details:
The File C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\
DATA\DemoData.ldf  in the message is not accessible to SQL Server for read and/or write 
operations during startup or database recovery. SQL Server might not be able to find the file, 
the file may be locked by another application, or SQL Server may not have permissions to 
access the file. 

Solution: 
  • Check that the file listed above is exist in the specified location.
  • Check the read write attribute for the file.
  • Check the SQL Server startup account has read and write permission to the folder and file.
  • Check that the file is not opened by another process.
  • Check that the file is not encrypted.
  • Provide FULL CONTROL (not just modify) to the service logon account (in my scenario was Network Service).


7 comments:

  1. HI Arun,

    We have faced the same issue.. today.. we have SQL Server cluster service which was running under specific Domain user account. Unfortunately.. that user was account was changed by someone and tried starting the sql service.. but it throws following error.

    Error: 'FCB::Open failed: Could not open file MSSQL\DATA\master.mdf for file number 1. OS error: 5(failed to retrieve text for this error. Reason: 15105).
    Could not open file MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(failed to retrieve text for this error. Reason: 15100)

    any help would be appreciated..

    ReplyDelete
    Replies
    1. Hello,
      Check below link for solution:

      http://support.microsoft.com/kb/929665

      Delete
  2. This comment has been removed by the author.

    ReplyDelete
  3. Thanks this works great

    ReplyDelete
  4. Nice article simply explained in short. After a long googling I have found this one here you will see a long explanation about SQL Server Error 17204. http://sqltechtips.blogspot.com/2015/12/fcb-open-failed-error-17204.html

    ReplyDelete