Operating System Error 38 Reached The End Of The File
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: The operating system returned error 38(Reached the end of the file.) to SQL Server during error 823 severity 24 state 2 a read at offset 0x000001f3400000 in file SQL Server > Database Design Question fatal error 823 occurred sql server 2008 0 Sign in to vote I'm getting below error while inserting into a table, Msg 1823, Level 16, State 1, sql server error 38 reached the end of the file 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 operating system error 21(the device is not ready.) encountered 7928, Level 16, State 1, Line 1 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. DBCC results for 'XXXXFactor'. There are 12474 rows in 76 pages for object "XXXXFactor". DBCC execution completed.
Sql Error 824
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 CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. Check DB results: 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 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, Line 1 The database could not be exclusively locked to perform the operation. Msg 7926, Level 16, State 1
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies
Sql Server Error 823 824 And 825
of this site About Us Learn more about Stack Overflow the company Business sql server error number 824 Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask sql error 825 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 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 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 http://stackoverflow.com/questions/5656363/restore-sql-server-database-failed-38reached-the-end-of-the-file 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
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=89075 on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question http://www.rapidprogramming.com/tutorial/HOW-TO-FIX-ERROR-823-IN-MICROSOFT-SQL-SERVER-81 answered! Username: 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 sql server iuseyew Starting Member 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 sql server error 14:24:19.24 server SQL Server is 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: 0BB
cannot perform any I/O (Input/output) operation. Sometimes, the error occurs due to either conflicts of Windows API used by SQL Server or SQL Server database corruption. It creates such a situation where user is unable to use the database. This unavoidable state led to a terrible aftereffect of data loss. To have this lost data back user is advised to use SQL database recovery solutions. For instance, user can also run across an error message similar to the following one in Windows Application Event Log or Microsoft SQL Server ERRORLOG: “2010-03-06 22:41:19.55 spid58 Error: 823, Severity: 24, State: 2. 2010-03-06 22:41:19.55 spid58 The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x000000a72c0000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL10.SQL2008MSSQLDATAmy_db.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.” Whenever, in any program, the above stated error message is encountered, in the ongoing process of modifying or querying the data, error is automatically returned to that program and SQL Server database connection is closed. Causes of the problem: This problem is caused by Windows APIs, which is used by Microsoft SQL Server. These APIs (such as Write File, Read File, WriteFileGather, and ReadFileScatter) perform Input/output operations. After the completion of I/O operations, MS SQL Server examines for associated errors with API calls. When API calls betrays with OS error, user notices this behavior of SQL Server. Here is the possibility that this problem may also occur due to co