Error: fcb::close-flush: Operating system error 21(The device is not ready.) encountered

We are using sql server 2005 Enterprise Edition with service pack1

I got the following error messages in the SQL log

The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000090000 in file '....mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. fcb::close-flush: Operating system error 21(The device is not ready.) encountered.

I got these errors for about 2 hrs and after that I see these messages in the sql log

Starting up database ' ' 1 transactions rolled forward in database '' (). This is an informational message only. No user action is required. 0 transactions rolled back in database ' ' (). This is an informational message only. No user action is required. Recovery is writing a checkpoint in database ' ' ( ). This is an informational message only. No user action is required. CHECKDB for database '' finished without errors on (local time). This is an informational message only; no user action is required.

Can anyone please help me in troubleshooting this issue. Why this migh have happened.

any help would be appreciated.

Thanks

This sounds like an IO subsystem issue, i.e. SQL Server is having difficulty talking to one of your drives. Are you using direct attached storage or a SAN?|||

Thanks for the reply. We have Netapp SCSI disk storage. Could you please tell me how do I troubleshoot this so that I wont get such errors in future.

Thanks

|||Based on this and what you describe in your other post, you really ought to give Microsoft PSS a call.|||

Do read this kb before contacting PSS. You might be running on an unsupported device.

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

Error: 5123 CREATE FILE encountered operating system error 5A(Access denied.)

HI ,

This is a problem I encountered when I had to detach a database file (type .mdf):

1) I went to the MS SQL Management Server Studi and detached my database file successfully from a connection called Workhorse.

2) I needed to place the .mdf database file into a zip file in order to put it on a remote server. I did this using Shared Portal. This was also successful

3) However when I tried reattaching the database file, I got this error:

CREATE FILE encountered operating system error 5A(Access denied.) while attempting to open or create the physical file "C\Program Files\MSSQL Server\MSSQL\Data\<databasename>.mdf'

Q) The database file and log file (ldf) exist in the correct directory so I don't know what happened. Can any one help?

Thanks much

Tonante

Dear Tonate,

Please, take a look on the following link and might be it will help you :)

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=120536&SiteId=1

|||

Hi Tonate,

I got the solution for this. I proud this is my first blog to provide the answer on internet

I got the same error too:

CREATE FILE encountered operating system error 5A(Access denied.) while attempting to open or create the physical file "C\Program Files\MSSQL Server\MSSQL\Data\<databasename>.mdf'

the solution is:

set the Operating system permission on that .mdf file to full permission to 'Everyone' in new server.

this will helps me to attach the database in other server..

Have a Great Day..

vino...

|||

Well that could be a security issue, its better to give permission to the SQL Server account.

Error: 5123 CREATE FILE encountered operating system error 5A(Access denied.)

HI ,

This is a problem I encountered when I had to detach a database file (type .mdf):

1) I went to the MS SQL Management Server Studi and detached my database file successfully from a connection called Workhorse.

2) I needed to place the .mdf database file into a zip file in order to put it on a remote server. I did this using Shared Portal. This was also successful

3) However when I tried reattaching the database file, I got this error:

CREATE FILE encountered operating system error 5A(Access denied.) while attempting to open or create the physical file "C\Program Files\MSSQL Server\MSSQL\Data\<databasename>.mdf'

Q) The database file and log file (ldf) exist in the correct directory so I don't know what happened. Can any one help?

Thanks much

Tonante

Dear Tonate,

Please, take a look on the following link and might be it will help you :)

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=120536&SiteId=1

|||

Hi Tonate,

I got the solution for this. I proud this is my first blog to provide the answer on internet

I got the same error too:

CREATE FILE encountered operating system error 5A(Access denied.) while attempting to open or create the physical file "C\Program Files\MSSQL Server\MSSQL\Data\<databasename>.mdf'

the solution is:

set the Operating system permission on that .mdf file to full permission to 'Everyone' in new server.

this will helps me to attach the database in other server..

Have a Great Day..

vino...

|||Well that could be a security issue, its better to give permission to the SQL Server account.|||Greetings SQL Server users, I rarely post to forums but think I probably should start doing so. I know this problem was probably solved, but just in case it wasn't, this was my solution to the exact same problem when attempting to do exactly what you tried (detaching, zipping, then re-attaching the database file *.mdf) using SQL Server 2005 with Mgmt Server Studio. First, Stop all SQL services, Secondly, go to the sql folder (default: MSSQL) and right click on it and see if you can change your folder and all subfolder atrributes to NOT read only (unchecked). I noticed that on my server, the log and data files could not be changed. So I immediately went to those files *.ldf and *.mdf and took ownership of both of them (the permissions can easily get wacked). Once I did that, I was able to zip them and move them to safer ground. I then restarted all SQL Services, and was able to re-attach the *.mdf file. If you are like me, you probably log in using a few different usernames and move files around a lot. For some odd reason, our permissions get hosed up from time to time. I hope this helped.

Error: 17805, Severity: 20, State: 3

====================================
Microsoft SQL Server 2000 (8.0.760).
Operating System: Microsoft Windows NT 5.2 (3790).
Platform: NT INTEL X86
====================================
We have got an error [Error: 17805, Severity: 20, State: 3]. It just occur
once last week and i am monitoring server, everything looks fine. What may
have caused this error and solutions
Thanks
ontario, canada
db,
http://support.microsoft.com/kb/818897 Need to install SP4
http://support.microsoft.com/kb/832977 DBCC PSS - Need to install SP4
http://support.microsoft.com/kb/827366 .NET programming problem
There are actually many similar problems focused on invalid or malformed
packets from a client. The following search will show you more notes:
http://search.microsoft.com/results.aspx?siteID=1&q=17805&mkt=&mkt=en-US
You are currently at SQL Server 2000 SP3, so upgrading to SP4 is probably
something you should investigate. (Support for SP3 ended in July 2007.)
RLF
"db" <db@.discussions.microsoft.com> wrote in message
news:3944A9A2-252E-437B-A9BD-E6C31F315B71@.microsoft.com...
> ====================================
> Microsoft SQL Server 2000 (8.0.760).
> Operating System: Microsoft Windows NT 5.2 (3790).
> Platform: NT INTEL X86
> ====================================
> We have got an error [Error: 17805, Severity: 20, State: 3]. It just occur
> once last week and i am monitoring server, everything looks fine. What may
> have caused this error and solutions
> Thanks
> --
> ontario, canada

Error: 17805, Severity: 20, State: 3

====================================
Microsoft SQL Server 2000 (8.0.760).
Operating System: Microsoft Windows NT 5.2 (3790).
Platform: NT INTEL X86
====================================
We have got an error [Error: 17805, Severity: 20, State: 3]. It just occ
ur
once last week and i am monitoring server, everything looks fine. What may
have caused this error and solutions
Thanks
ontario, canadadb,
http://support.microsoft.com/kb/818897 Need to install SP4
http://support.microsoft.com/kb/832977 DBCC PSS - Need to install SP4
http://support.microsoft.com/kb/827366 .NET programming problem
There are actually many similar problems focused on invalid or malformed
packets from a client. The following search will show you more notes:
http://search.microsoft.com/results...&mkt=&mkt=en-US
You are currently at SQL Server 2000 SP3, so upgrading to SP4 is probably
something you should investigate. (Support for SP3 ended in July 2007.)
RLF
"db" <db@.discussions.microsoft.com> wrote in message
news:3944A9A2-252E-437B-A9BD-E6C31F315B71@.microsoft.com...
> ====================================
> Microsoft SQL Server 2000 (8.0.760).
> Operating System: Microsoft Windows NT 5.2 (3790).
> Platform: NT INTEL X86
> ====================================
> We have got an error [Error: 17805, Severity: 20, State: 3]. It just o
ccur
> once last week and i am monitoring server, everything looks fine. What may
> have caused this error and solutions
> Thanks
> --
> ontario, canada

Error: 17805, Severity: 20, State: 3

==================================== Microsoft SQL Server 2000 (8.0.760).
Operating System: Microsoft Windows NT 5.2 (3790).
Platform: NT INTEL X86
==================================== We have got an error [Error: 17805, Severity: 20, State: 3]. It just occur
once last week and i am monitoring server, everything looks fine. What may
have caused this error and solutions
Thanks
--
ontario, canadadb,
http://support.microsoft.com/kb/818897 Need to install SP4
http://support.microsoft.com/kb/832977 DBCC PSS - Need to install SP4
http://support.microsoft.com/kb/827366 .NET programming problem
There are actually many similar problems focused on invalid or malformed
packets from a client. The following search will show you more notes:
http://search.microsoft.com/results.aspx?siteID=1&q=17805&mkt=&mkt=en-US
You are currently at SQL Server 2000 SP3, so upgrading to SP4 is probably
something you should investigate. (Support for SP3 ended in July 2007.)
RLF
"db" <db@.discussions.microsoft.com> wrote in message
news:3944A9A2-252E-437B-A9BD-E6C31F315B71@.microsoft.com...
> ====================================> Microsoft SQL Server 2000 (8.0.760).
> Operating System: Microsoft Windows NT 5.2 (3790).
> Platform: NT INTEL X86
> ====================================> We have got an error [Error: 17805, Severity: 20, State: 3]. It just occur
> once last week and i am monitoring server, everything looks fine. What may
> have caused this error and solutions
> Thanks
> --
> ontario, canada

Error: 17059, Severity: 18, State: 0

What does this error mean? The next message was this:
Operating system error 10055: An operation on a socket could not be
performed because the system lacked sufficient buffer space or because a
queue was full...Please disregard. I found the answer here:
http://support.microsoft.com/kb/811274/en-us
"Ron Hinds" <__ron__dontspamme@.wedontlikespam_garageiq.com> wrote in message
news:OnNi9oxiGHA.4512@.TK2MSFTNGP04.phx.gbl...
> What does this error mean? The next message was this:
> Operating system error 10055: An operation on a socket could not be
> performed because the system lacked sufficient buffer space or because a
> queue was full...
>
>