Operating System Error 38reached The End Of The File
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My sql server error 38 reached the end of the file Forums Answered by: The operating system returned error 38(Reached complete a full database consistency check (dbcc checkdb) the end of the file.) to SQL Server during a read at offset 0x000001f3400000 in
How To Run Dbcc Checkdb
file SQL Server > Database Design Question 0 Sign in to vote I'm getting below error while inserting into a table, Msg 1823,
System Error: 38 Mysql
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 snapshot for dbcc checkdb repair 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 CHECKDB). This error can
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 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 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 http://stackoverflow.com/questions/5656363/restore-sql-server-database-failed-38reached-the-end-of-the-file 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 TheGameiswar 10.3k4942 answered Apr 13 '11 at 22:30 dnewcome 1,6751311 1 The lesson here is: always verify your backups! –pdwalker Jul 19 '11 at 18:31 add a c
down 2 of the disks were off in the Bios. Weadded the 3 disks to a different serveridentical in brand and architecture, the raid controller was able to http://www.bigresource.com/MS_SQL-Operating-system-error-38-Reached-the-end-of-the-file-on-file-C-Datamyfile_log-LDF-H9c7zbBJ.html reconfigure the virtual drive H:. All files were there, we installed sql server http://www.sqlservercentral.com/Forums/Topic903531-266-1.aspx 2005 on the new server, but when we tried to attach the database we got the error below: TITLE: Microsoft SQL Server Management Studio ------------------------------ Attach database failed for Server 'myserver'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ The dbcc checkdb operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000000af0000 in file 'C:Datamylog_log.LDF'. 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 the end of caused by many factors; for more information, see SQL Server Books Online. Operating system error 38(Reached the end of the file.) on file "C:Datamylog_log.LDF" during ReadFileHdr. Could not open new database 'mydb'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 823) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=823&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Itried the following steps but it always failed: - create a new db with the same name of the lost db; - put the db in emergency mode; - stop sql service and replace the mdf file; - start sql service; - Run Dbcc checkdb('mydb') we got the error below: Msg 945, Level 14, State 2, Line 1 Database 'ism0506' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. Any HELP please ? Thanks, Tarek Ghazali Sql Server MVP View 5 Replies Similar Messages: ReadFileHdr: Operating System Error 38(Reached The Cannot Attach Mdf: Create File Encountered Operating System Error 5 While Attempting To Open The Physical File... SQL 2012 :: Unable To Open Physical File - Operating System Error 5 DB Engine :: Unable To Open Physical File - Operating System Error
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Data Corruption » Operating System error 38 Operating System error 38 Rate Topic 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 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 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 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