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: Could not connect to database

The following error is encountered while trying to Host the site from IIS ..
" The Assembly Version ([ASSEMBLY VERSION]) does not match the Database Version ([DATABASE VERSION]).
"Error: Could not connect to the database specified in the connection string for SqlDataProvider. "

We have 2 different machines, over which we have 2 different SQL Server.
In Web.Config, if we give server=server1 it works well and there is no problem at all...
if we give server=server2, and executehttp://localhost/application, the above mentioned error occurs..

and yes the application is hosted on 3rd machine......

Can anyone throw some light on this regard.
Its urgent.

You're using DotNetNuke, right? Try this search on the Forums to see other threads on this topic:
http://forums.asp.net/search/SearchResults.aspx?q=ASSEMBLY+VERSION+match+DATABASE+VERSION&o=Relevance

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: 17883

Dear All,
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8.Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
--
David Gugick
Imceda Software
www.imceda.com

Error while installing sql server 2005

Need Help. I'm trying to install sql server 2005 on Windows server 2003 and got the following error message "The setup has encountered an unexpected error while setting up reporting service and share point exclusion path. The error is: Fatal error during installation." Not sure what to do next.

Hi,

see the screencast on my site how to configure a site-by-site installation with Reporting Services and Sharepoint

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

You need to have IIS installed on your machine for Reporting Service to get installed.

Regards,

Rajesh

|||

This is answered in Microsoft Knowledge Base article KB920803.

Hope that helps,

Ian

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.