Operating System Error 38 Error Not Found
Contents |
360 games PC games error 823 severity 24 state 2 Windows games Windows phone games Entertainment All Entertainment fatal error 823 occurred sql server 2008 Movies & TV Music Business & Education Business Students & educators operating system error 21(the device is not ready.) encountered Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet sql error 824 Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Sql Server Error 38 Reached The End Of The File
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
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
Sql Server Error 823 824 And 825
Author Message alen teplitskyalen teplitsky Posted Wednesday, April 14, 2010 1:48 PM Ten Centuries Group: General sql server error number 824 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 sql error 825 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 https://support.microsoft.com/en-us/kb/2015755 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 http://www.sqlservercentral.com/Forums/Topic903531-266-1.aspx 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 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
down 2 of the disks were off in the Bios. Weadded the 3 disks to a different serveridentical http://www.bigresource.com/MS_SQL-Operating-system-error-38-Reached-the-end-of-the-file-on-file-C-Datamyfile_log-LDF-H9c7zbBJ.html in brand and architecture, the raid controller was able to reconfigure the virtual drive H:. All files were there, we installed sql server 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) sql server 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 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 sql server error 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. 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 ?