<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Data Corruption
»
Help Please - DBCC Check Failed-The operating...
Help Please - DBCC Check Failed-The operating system returned error 87
Rate Topic
Display Mode
Topic Options
Author
Message
JC-3113
JC-3113
Posted Monday, March 11, 2013 8:54 AM
SSC-Addicted
Group: General Forum Members
Last Login: 2 days ago @ 8:43 AM
Points: 442,
Visits: 620
Hi folks
came in today and found this error on one of my databases.
Would appreciate any assistance on this as I have not seen this type of error before
If you could lend me your expertise in this i would greatly appreciate it:
Event Error:
The operating system returned error 87(The parameter is incorrect.)
to SQL Server during a write at offset 0x000001cdc58000 in file 'K:\MSSQL\UserDB\Data\SP04_WSS_Content.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.
Thanks
Jim
use [sp04_wss_content];
dbcc checkdb;
go
Changed database context to 'SP04_WSS_Content'.
Msg 823, Level 24, State 3, Server NSAB-SS80-SQL-N, Line 4
The operating system returned error 87(The parameter is incorrect.) to SQL Server during a write at offset 0x000001cdc58000 in file
'K:\MSSQL\UserDB\Data\SP04_WSS_Content.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.
Msg 1823, Level 16, State 2, Server NSAB-SS80-SQL-N, Line 4
A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Server NSAB-SS80-SQL-N, Line 4
The database snapshot for online checks could not be created.
Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or
alternate streams. Attempting to get exclusive access to run checks offline.
Msg 5030, Level 16, State 12, Server NSAB-SS80-SQL-N, Line 4
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Server NSAB-SS80-SQL-N, Line 4
Post #1429314
opc.three
opc.three
Posted Monday, March 11, 2013 1:52 PM
SSCertifiable
Group: General Forum Members
Last Login: Today @ 1:46 PM
Points: 6,730,
Visits: 11,783
JC-3113 (3/11/2013)
Hi folks
came in today and found this error on one of my databases.
Would appreciate any assistance on this as I have not seen this type of error before
If you could lend me your expertise in this i would greatly appreciate it:
Event Error:
The operating system returned error 87(The parameter is incorrect.)
to SQL Server during a write at offset 0x000001cdc58000 in file 'K:\MSSQL\UserDB\Data\SP04_WSS_Content.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.
Thanks
Jim
use [sp04_wss_content];
dbcc checkdb;
go
Changed database context to 'SP04_WSS_Content'.
Msg 823, Level 24, State 3, Server NSAB-SS80-SQL-N, Line 4
The operating system returned error 87(The parameter is incorrect.) to SQL Server during a write at offset 0x000001cdc58000 in file
'K:\MSSQL\UserDB\Data\SP04_WSS_Content.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.
Msg 1823, Level 16, State 2, Server NSAB-SS80-SQL-N, Line 4
A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Server NSAB-SS80-SQL-N, Line 4
The database snapshot for online checks could not be created.
Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or
alternate streams. Attempting to get exclusive access to run checks offline.
Msg 5030, Level 16, State 12, Server NSAB-SS80-SQL-N, Line 4
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Server NSAB-SS80-SQL-N, Line 4
Error 823
means SQL Server had trouble accessing the database file on disk. If you cannot run CHECKDB it may be a sign of an impending crash of your I/O subsytem. Do you have a current backup of this database. Can you take a new FULL backup of this database? Enlist the help of your hardware team (if you have one) and look for other messages in the Windows Event log and SQL Server Error log denoting issues with the I/O subsystem right away.
From the database side, try restoring a current database backup to another machine and checking for corruption there, i.e. run
DBCC CHECKDB(sp04_wss_content) WITH NO_INFOMSGS
on the restored copy and post the entire result here.
__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Believe you can and you're halfway there.
--Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler
--Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them.
--Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples.
--Giordy
Post #1429469
JC-3113
JC-3113
Posted Monday, March 11, 2013 2:51 PM
SSC-Addicted
Group: General Forum Members
Last Login: 2 days ago @ 8:43 AM
Points: 442,
Visits: 620
Hi opc.three
Well, i started to back up all the databases since i did not get any backups since sat. I am using SSMS and if the DBCC CHECKDB fails on any database, the backups do not run, since i do that first.
I know, pretty poor. I am going to have to address this, but anyway i was backing up existing databases and started getting the same problem on two other databases. I found this error also
"A system assertion check has failed. "
Not good according to Gail. Lots of dump files and "BugCheck Dump" files. Not good also.
Anyway as I was doing a check on the third database, the server crashed.
After it came back up and I started the services, I ran a check again on the bad databases.
To my surprise, all the databases that showed a problem, passed the check and I was able to get full backups. So I am not sure what the cause is at this time.
I am trying to get an Admin to get me a ticket with MS to see if they can shed some light on issues we had.
Thanks
Jim
Post #1429483
opc.three
opc.three
Posted Monday, March 11, 2013 4:13 PM
SSCertifiable
Group: General Forum Members
Last Login: Today @ 1:46 PM
Points: 6,730,
Visits: 11,783
Gail looked to be offline so I jumped in. Hopefully she'll drop by and help shed some additional light on the situation.
__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Believe you can and you're halfway there.
--Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler
--Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them.
--Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples.
--Giordy
Post #1429524
Lynn Pettis
Lynn Pettis
Posted Monday, March 11, 2013 5:27 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 4:37 PM
Points: 21,627,
Visits: 27,480
Does that particular database have an database snapshot currently defined? Just a guess here.
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #1429544
kyleheath33
kyleheath33
Posted Tuesday, March 12, 2013 9:00 AM
SSC Veteran
Group: General Forum Members
Last Login: Thursday, May 16, 2013 4:28 AM
Points: 200,
Visits: 727
Could be an issue with the DBCC snapshot.. the only thing I could remember was this post a while ago:
http://www.sqlservercentral.com/Forums/Topic450261-146-2.aspx#bm477512
Would make sense if your DBCC came back after a server restart after a crash
Post #1429878
JC-3113
JC-3113
Posted Tuesday, March 12, 2013 9:16 AM
SSC-Addicted
Group: General Forum Members
Last Login: 2 days ago @ 8:43 AM
Points: 442,
Visits: 620
Thanks kyleheath33
from what I was told from a sysadmin
this sql server is a virtual machine on vmware
i do not know that much abour vmware
anyway apparently, the vmware console or master pink screened and took down all the clients
of which my server is one, so thus the crash yesterday
that does not explain why i was getting corruption notices starting on last sat though unless that master was going south at that time.
Jim
Post #1429891
kyleheath33
kyleheath33
Posted Tuesday, March 12, 2013 9:31 AM
SSC Veteran
Group: General Forum Members
Last Login: Thursday, May 16, 2013 4:28 AM
Points: 200,
Visits: 727
From my post I meant that it would make sense for the DBCC to come back clean after a reboot as the SQL restart (server crash) would have cleared the hidden previous snapshot which was causing the issue, this is all just suggestion and would keep going with the MS ticket.
Post #1429902
JC-3113
JC-3113
Posted Tuesday, March 12, 2013 11:49 AM
SSC-Addicted
Group: General Forum Members
Last Login: 2 days ago @ 8:43 AM
Points: 442,
Visits: 620
Hi Lynn
i am not using snapshots that I am aware of
Jim
Post #1430012
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
