SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 getting 823 error when logging in to sql server
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

iamsqldba
Starting Member

1 Posts

Posted - 03/31/2013 :  21:58:43  Show Profile  Reply with Quote
hi,
I am getting the follwing error when i try to login to the sql server
Warning: Fatal error 823 occurred at <datetime stamp>. Note the error and time, and contact your system administrator.(Microsoft SQL Server, Error: 21).
In the error log:


2013-03-30 22:49:03.88 spid58 The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x000000001be000 in file 'G:\SqlData\master.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.
2013-03-30 22:49:05.38 spid57 Error: 823, Severity: 24, State: 2.
2013-03-30 22:49:05.38 spid57 The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x000000001be000 in file 'G:\SqlData\master.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.
2013-03-30 22:49:06.28 spid20s Error occurred while attempting to drop worktable with partition ID 423521814315008.
2

prett
Posting Yak Master

USA
197 Posts

Posted - 03/31/2013 :  22:44:26  Show Profile  Visit prett's Homepage  Reply with Quote
Most possible reasons for the error:

1. The linked server database is stopped.
2. The linked server database is occupied with other stuff (reindexing, backup).
3. The linked server is down (power off).
4. The linked server is busy with other stuff (defragmenting).
5. A cable to the linked server is dropped (replug all cables).
6. A router/switch/hub is faulty or not working.
7. Too much data is passed on the network.
Go to Top of Page

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 04/01/2013 :  18:49:43  Show Profile  Visit russell's Homepage  Reply with Quote
No.

Most possible causes are:

1. Corruption in master.mdf
2. I/O errors while accessing the G: drive.

The error message shows the appropriate next course of action:
Complete a full database consistency check (DBCC CHECKDB)

Also check the event logs for correlated errors

EDIT
Also prett, if you're going to plagerize other people's posts at least give them credit or a link rather than claiming it as your own.

Edited by - russell on 04/01/2013 18:56:19
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

India
52317 Posts

Posted - 04/02/2013 :  01:28:17  Show Profile  Reply with Quote
Here you go with original post having the suggestion

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=66058

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/
https://www.facebook.com/VmBlogs
Go to Top of Page

prett
Posting Yak Master

USA
197 Posts

Posted - 04/17/2013 :  06:42:11  Show Profile  Visit prett's Homepage  Reply with Quote
quote:
Originally posted by russell

No.

Most possible causes are:

1. Corruption in master.mdf
2. I/O errors while accessing the G: drive.

The error message shows the appropriate next course of action:
Complete a full database consistency check (DBCC CHECKDB)

Also check the event logs for correlated errors

EDIT
Also prett, if you're going to plagerize other people's posts at least give them credit or a link rather than claiming it as your own.



Hi Russell,

Thanks for the suggestion. But I am not taking any credit. I am only try to solve the users issues. Here is Reference link:
http://social.msdn.microsoft.com/Forums/en-US/biztalkgeneral/thread/4193ec51-07dd-41b5-8dd0-8a5e33ea7d0b
Go to Top of Page

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 04/17/2013 :  12:28:07  Show Profile  Visit russell's Homepage  Reply with Quote
So you copied what someone else copied, and it is still the wrong answer for this situation.
Go to Top of Page

prett
Posting Yak Master

USA
197 Posts

Posted - 04/18/2013 :  00:47:49  Show Profile  Visit prett's Homepage  Reply with Quote
quote:
Originally posted by russell

So you copied what someone else copied, and it is still the wrong answer for this situation.



Hi Russell,

I don't understand what problem you have. You have a problem because I am googling the error or you have a problem because I am answering the questions.

And I think, The answer is correct or incorrect, this right only for who ask the question.

Till the user don't satisfied with the answer or solve the issue, the answer cannot be correct even it is given by me or by you.

And If I am giving the wrong answers then why the users are appreciating my post.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.11 seconds. Powered By: Snitz Forums 2000