Event Id 17053 Operating System Error 19
Contents |
useful error message in the Event Log - "Operating System error 19(error not found)" (Event ID 17053), followed by the operating system returned error 21(the device is not ready.) to sql server the SQL Server service coming crashing down. Google was less than helpful;
Operating System Error 19(the Media Is Write Protected.) Encountered
apparently this error message should be self-explanatory!Well, eventually the penny dropped when I tried to create a folder event id 17053 operating system error 21 and couldn't do that either. Something about a write protect issue. So just to be clear..."Operating System error 19(error not found)" means "your hard drive is write protected".Right.Don't ask why my entire E: drive was set as write protected, its a long and painful story. Posted by Ed Jakeman at 12:46 PM Labels: Server 2003, SQL 3 comments: shekharJune 21, 2011 at 11:04 AMvery nice blogReplyDeleteJanice ClementsNovember 28, 2011 at 12:14 PMGood thing you shared that this article. I'm also having that error whenever I deal with SQL. I'm glad you shared the solution.Hulme PC RepairReplyDeleteGAVINJuly 5, 2012 at 1:48 AMThanks mate - spent lots of wasted time on this until I saw your post - for some reason on VM the drive holding the SQL Server logs was write protectedReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Home Tech blog History CV Search This Blog Loading... Labels Acrobat aero Applications asus eee 901 Blogger browsers chrome Citrix disk space EdgeSight email Event Viewer exchange 2007 File Quotas firefox FTP Google Government ie IIS microsoft Microsoft Office netbooks Nominet server Server 2003 Server 2008 Server 2008 R2 SQL ubuntu vista VMware VuGen windows 7 Xenapp XenServer Subscribe Posts Atom Posts Comments Atom Comments Blog Archive ► 2010 (25) ► September (3) ► April (5) ► March (3) ► February (5) ► January (9) ▼ 2009 (38) ► November (5) ► October (1) ► September (1) ► August (9) ▼ July (6) SQL Server - Operating System error 19(error not f... Browser Wars update Firebug Google humour Genius RAW disk scare ► June (1) `
log in tour help Tour Start 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 Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Intermittent Disconnection http://tech.edjakeman.com/2009/07/sql-server-operating-system.html to DB on SAN. Event ID 17053 and 9001 up vote 2 down vote favorite I am getting some strange issues with our MS SQL 2008 database where intermittently we lose connection to the db for 10+ seconds or so. The db is stored on a SAN over fiber. The latest event log error I get is "LogWriter: Operating System error 1 (incorrect function) encountered with an event ID of 17053. Following that error is event ID 9001 http://dba.stackexchange.com/questions/5482/intermittent-disconnection-to-db-on-san-event-id-17053-and-9001 about log for database is not available. I would then see a message stating recovery is completed for database in 12 seconds. Not sure how to approach this and any help or guidance would be much appreciated. Running MS SQL 2008 on Windows 2008 SP1. sql-server-2008 share|improve this question asked Sep 7 '11 at 14:31 Jon 112 3 Do you have a SAN specialist on staff or on call? They'd probably need to review the SAN logs/config. –Aaron Bertrand♦ Sep 7 '11 at 14:45 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote You need to either have a SAN admin look at the system of bring a consultant in to look at it. (Yes I'm a SAN consultant, no that's not why I'm saying this.) share|improve this answer answered Sep 7 '11 at 19:16 mrdenny 24.2k22765 So you all think this error is related to issue accessing the SAN? –Jon Sep 7 '11 at 19:23 1 Yep, sure do. Pretty much any time you see an Operating System error it isn't going to be a SQL Server problem. –mrdenny Sep 7 '11 at 19:35 1 Agree with Denny, 99% likely to be connectivity to the SAN. When you call the SAN guy, remind him to bring replacement cables and just in case an HBA. More than likely someone nudged/tripped over/damaged a cable. –M
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help https://www.experts-exchange.com/questions/27040619/SQL-Server-keeps-losing-drive-letter.html Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor http://serverfault.com/questions/221219/sqlexpress-service-unable-to-start-error-code-17053 Services Groups Website Testing Store Headlines Experts Exchange > Questions > SQL Server keeps losing drive letter Want to Advertise Here? Solved SQL Server keeps losing drive letter Posted operating system on 2011-05-16 MS SQL Server VMware Windows Server 2008 1 Verified Solution 16 Comments 1,507 Views Last Modified: 2012-05-11 Hi This is a virtual server, that until today had no problems I am aware of. I have the OS installed on C and a seperate virtual drive for the actual DB (B:\) Everytime I reboot the DB Drive operating system error is missing its drive letter. Even after I reassign it, I cannot start the SQL service - error in eventlog: Log Name: Application Source: MSSQLSERVER Date: 16/05/2011 14:45:38 Event ID: 17053 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: Saints-SQL.Saints.local Description: FCB::ZeroFile(), GetOverLappedResult(): Operating system error 19(failed to retrieve text for this error. Reason: 15105) encountered. Event Xml:
Start 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 Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SQLExpress service unable to start Error code 17053 up vote 1 down vote favorite A user was instructed by their software support to upgrade a program and install SQLExpress as part of the installation process. Since that time, the service has been able to start, citing error 17053, which appears to be an authentication issue. Here is the error log: 2011-01-11 13:17:45.50 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2) 2011-01-11 13:17:45.50 Server (c) 2005 Microsoft Corporation. 2011-01-11 13:17:45.50 Server All rights reserved. 2011-01-11 13:17:45.50 Server Server process ID is 3332. 2011-01-11 13:17:45.50 Server Authentication mode is WINDOWS-ONLY. 2011-01-11 13:17:45.50 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. 2011-01-11 13:17:45.52 Server This instance of SQL Server last reported using a process ID of 2332 at 11/10/2010 2:15:24 PM (local) 11/10/2010 7:15:24 PM (UTC). This is an informational message only; no user action is required. 2011-01-11 13:17:45.52 Server Error: 17053, Severity: 16, State: 1. 2011-01-11 13:17:45.52 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered. 2011-01-11 13:17:45.52 Server Registry startup parameters: 2011-01-11 13:17:45.52 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf 2011-01-11 13:17:45.52 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG 2011-01-11 13:17:45.52 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf 2011-01-11 13:17:45.52 Server Error: 17113, Severity: 16, State: 1. 2011-01-11 13:17:45.52 Server Error 3(The system cannot