Operating System Error 38 Sql Server
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From fatal error 823 occurred sql server 2008 My Forums Answered by: The operating system returned error sql server error 823 38(Reached the end of the file.) to SQL Server during a read at offset 0x000001f3400000 sql error 824 in file SQL Server > Database Design Question 0 Sign in to vote I'm getting below error while inserting into a table, Msg
Operating System Error 21(the Device Is Not Ready.) Encountered
1823, Level 16, State 1, Line 1 A database snapshot cannot be created because it failed to start. Msg 1823, Level 16, State 2, Line 1 A database snapshot cannot be created because it failed to start. Msg 7928, Level 16, State 1, Line 1 The database sql server error 38 reached the end of the file 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. DBCC results for 'XXXXFactor'. There are 12474 rows in 76 pages for object "XXXXFactor". DBCC execution completed. If DBCC printed error messages, contact your system administrator. Msg 823, Level 24, State 2, Line 1 The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x000001f3400000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\XXXX_data.ndf:MSSQL_DBCC17'. 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 CHEC
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! sql server error 823 824 and 825 We've restricted the ability to create new threads on these forums. SQL
Sql Server Error Number 824
Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username:
Sql Error 825
Password: Save Password Forgot your Password? All Forums General SQL Server Forums Data Corruption Issues ReadFileHdr: Operating system error 38(Reached the Reply to Topic Printer Friendly Author Topic iuseyew Starting Member https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ce7c5726-308e-4986-bf19-ba860ecb01ec/the-operating-system-returned-error-38reached-the-end-of-the-file-to-sql-server-during-a-read-at?forum=databasedesign 4 Posts Posted-09/07/2007: 17:39:46 i believe this is the right thread... i recently had an issue where my xpstar.dll would not register and i read to fix the issue to reapply the SP so i installed SP4 i now am getting this error... please help!2007-09-07 14:24:19.24 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.2007-09-07 14:24:19.24 server SQL Server is http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=89075 starting at priority class 'normal'(4 CPUs detected).2007-09-07 14:24:19.36 server SQL Server configured for thread mode processing.2007-09-07 14:24:19.38 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.2007-09-07 14:24:19.40 server Attempting to initialize Distributed Transaction Coordinator.2007-09-07 14:24:20.44 spid3 Starting up database 'master'.2007-09-07 14:24:20.49 spid3 Error: 823, Severity: 24, State: 5.2007-09-07 14:24:20.49 spid3 ReadFileHdr: Operating system error 38(Reached the end of the file.) encountered.2007-09-07 14:24:20.49 spid3 Error: 5159, Severity: 16, State: 3.2007-09-07 14:24:20.49 spid3 09/07/07 14:24:20 Stack Overflow Dump not possible - Exception c00000fd E at 0x00449CA12007-09-07 14:24:20.49 spid3 Address=449ca1 Exception Code = c00000fd2007-09-07 14:24:20.49 spid3 eax=ba65a0de ebx=00000002 ecx=42ba8740 edx=0bb0a8302007-09-07 14:24:20.49 spid3 esi=00000001 edi=42ba8740 eip=00449ca1 esp=0bb09fc42007-09-07 14:24:20.49 spid3 ebp=0bb0a56c efl=000102122007-09-07 14:24:20.49 spid3 cs=1b ss=23 ds=23 es=23 fs=3b gs=02007-09-07 14:24:20.49 spid3 1: Frame: 0BB0A56C Return Address 00449CA12007-09-07 14:24:20.49 spid3 2: Frame: 0BB0AD88 Return Address 00449E102007-09-07 14:24:20.49 spid3 3: Frame: 0BB0AD9C Return Address 0044A14B2007-09-07 14:24:20.49 spid3 4: Frame: 0BB0ADAC Return Address 0044A17D2007-09-07 14:24:20.49 spid3 5: Frame: 0BB0ADF8 Return Address 0044A19B2007-09-07 14:24:20.49 spid3 6: Frame: 0BB0AE18 Return Address 004CD11C2007-09-07 14:24:20.49 spid3 7: Frame: 0BB0B2A8 Return Address 005ED83E2007-09-07 14:24:20.49 spid3 8: Frame: 0BB0B2FC Return Address 004054732007-09-07 14:24:20.49 spid3 9: Frame: 0BB0B324 Return A
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » http://www.sqlservercentral.com/Forums/Topic903531-266-1.aspx Data Corruption » Operating System error 38 Operating System error 38 Rate Topic http://stackoverflow.com/questions/5656363/restore-sql-server-database-failed-38reached-the-end-of-the-file Display Mode Topic Options Author Message alen teplitskyalen teplitsky Posted Wednesday, April 14, 2010 1:48 PM Ten Centuries Group: General Forum Members Last Login: Wednesday, October 12, 2016 2:14 PM Points: 1,419, Visits: 4,611 we have a process on our SAN where we sync some volumes to other volumes and mount them sql server on another backup SQL server as a backup. for the last few days the backup sql server has been getting this error when we mount one of the databases. we added a new volume and file on sunday night and the first night it sync'd OK, but the last few days we've had problems.we're putting some indexes on it and i thought that maybe it's because sql server error the sync happened during the times i've created new indexes. the production database is up and running with no errors. we have checksum error checking enabled and Netbackup scans every db page that it backs up as wellThe operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000559192000 in file 'c:\mount\disk17\SCS_INDX3.NDF'. 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. [SQLSTATE HY000] (Error 823) During redoing of a logged operation in database 'SCS', an error occurred at log record ID (1538697:147050:15). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database. [SQLSTATE HY000] (Error 3313). The step failed. Post #903531 « Prev Topic | Next Topic » Permissions You cannot post new topics. You cannot post topic replies. You cannot pos
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Restore SQL Server Database - failed: 38(Reached the end of the file.) up vote 5 down vote favorite I am running the following script: RESTORE DATABASE [Name_V2] FROM DISK = N'C:\20100920_Name_V2.bak' WITH MOVE N'Name_V2' TO N'C:\Program Files\...\Name_V2.mdf', MOVE N'Name_V2_log' TO N'C:\Program Files\...\Name_V2_log.ldf', REPLACE, STATS=1, FILE=1, NORECOVERY GO When it runs, I get to 70 percent processed, and I get the following error: Msg 3203, Level 16, State 1, Line 1 Read on "C:\20100920_Name_V2.bak" failed: 38(Reached the end of the file.) Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. I'm not sure what the problem is. Can someone shed some light on it? When I do a RESTORE VERIFYONLY on it, I get the same 'reached end of the file' error. When I do a RESTORE FILELISTONLY FROM DISK, it comes back with the results listing the .mdf and .ldf. Thank you in advance! sql sql-server-2008 share|improve this question edited Apr 14 '11 at 4:57 marc_s 454k938711033 asked Apr 13 '11 at 22:19 TexasT 901317 It turned out to be corrupted somehow. I received another Full Backup (which was also larger in size from the original), and it restored fine using the SSMS UI. Thanks for all the help! –TexasT Apr 15 '11 at 14:00 add a comment| 2 Answers 2 active oldest votes up vote 7 down vote accepted Looks like a corrupted or incomplete backup. See this post on msdn blogs http://social.msdn.microsoft.com/Forums/en/sqldisasterrecovery/thread/b57ae7c2-9f86-48e1-a356-ceb105181bf8 Summary of thread linked.. It appears that the backup file itself is corrupt, or the copy was incomplete. Restore reached the end of the backup file before the database was fully restored. share|improve this answer edited Aug 1 at 18:08