Error: 17207 - Open; Operating System error 5

Question

Error: 17207 - Open; Operating System error 5

khahlediet

SSC Veteran

Points: 298
More actions
February 11, 2008 at 3:21 am

#183822

Hi. I need your help on solving this error:
Error: 17207
FCB::Open: Operating System error 5 (error not found) occurred while creating or opening file 'C:\ Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf'
Thanking you in advance.
Regards
Tshidiso

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

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

Deepak-405225 SSCertifiable Points: 6120 More actions · Answer 1

Ensure that the Sql Service account has modify permissions on the folder containing data and log files. In your case I think SQL Server would not have started. For user databases it will reflect the status as Suspect in such cases.

[font="Verdana"]- Deepak[/font]

khahlediet SSC Veteran Points: 298 More actions · Answer 2

Thank you for the reply Deepak. And then what must I do now to solve this error?

- Tshidiso

satishjobs.n SSC Veteran Points: 234 More actions · Answer 3

Hi,

try with this

it works for both as u asked and i mentioned

SQL SERVER – FIX : Error 945 Database cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server error log for details

http://blog.sqlauthority.com/2007/08/02/sql-server-fix-error-945-database-cannot-be-opened-due-to-inaccessible-files-or-insufficient-memory-or-disk-space-see-the-sql-server-error-log-for-details/

1) If possible add more hard drive space either by removing of unnecessary files from hard drive or add new hard drive with larger size.

2) Check if the database is set to Autogrow on.

3) Check if the account which is trying to access the database has enough permission to perform operation.

4) Make sure that .mdf and .ldf file are not marked as read only on operating system file system level.

1.STEP1: identify the db status:

use master

select databaseproperty(’db_name’,'isShutdown’)

Most of them it would return 1 in this situation

2. STEP 2: Clear up the internal db status:

use master

alter database db_name set offline

it would return with no error in most cases

3. STEP 3: Get detail error message:

use master

alter database db_name set online

Then refresh database from object explorer console

Try to connect any one table of that DB, if ur able to connect then all set

Thanks

Satish

Dayal Bangalore SSC Veteran Points: 236 More actions · Answer 4

This error is due to the non-existing file path for .mdf and .ldf files while restoring the database using .bak file.

Solution:

1) While restoring database using .bak file, Go to Files properties of that database and check to see if the path of both .mdf and .ldf files are correctly pointed to known location like C: drive and so on. (In my case, I had no D: drive on my machine but .mdf and .ldf files were pointed to some folder under D: drive which was NOT existing on my machine).

Also see that, your logon account has security permissions to write to these .mdf and .ldf files while restoring!

Hope that helps,

Cheers

Dayal

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

Dayal Bangalore (2/9/2012)
This error is due to the non-existing file path for .mdf and .ldf files while restoring the database using .bak file.

No, it is not. It's error 5, that is permission denied. It means the folder and files exist but the windows user (the sql server service account in this case) does not have permission to open the files.

p.s. 4 year old thread.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

maheshsqldba7 Valued Member Points: 55 More actions · Answer 6

maheshsqldba7

Valued Member

Points: 55

November 13, 2014 at 1:41 am

#1758155

pls give me more information about error no 17204