Microsoft Sql Server Error 9001
Contents |
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners fatal error 9001 occurred sql server ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 the log for database is not available sql server Documentation APIs and reference Dev centers Samples Retired content We’re sorry. The content you
Error 9001 Severity 21 State 4
requested has been removed. You’ll be auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and
Event Id 9001 Group Policy
Languages Mobile and Embedded Development .NET Development Office development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This error 9001 severity 21 state 1 tempdb documentation is archived and is not being maintained. MSSQLSERVER_9001 Other Versions SQL Server 2014 SQL Server 2012 Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2). Details Product Name SQL Server Event ID 9001 Event Source MSSQLSERVER Component SQLEngine Symbolic Name LOG_NOT_AVAIL Message Text The log for database '%.*ls' is not available. Check the event log for related error messages. Resolve any errors and restart the database. Explanation The database log was taken offline. Usually this signifies a catastrophic failure that requires the database to restart. User Action Diagnose other errors and restart the instance of SQL Server if it has not already restarted itself. Community Additions Show: Inherited Protected Print Export (0) Print Export (
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2008 » SQL
Sql Server Error 9001 The Log For Database 'tempdb' Is Not Available
Server 2008 Administration » Log not available error 9001 19 posts,Page 1 of sql autoclose 212»» Log not available error 9001 Rate Topic Display Mode Topic Options Author Message shaun.stuartshaun.stuart Posted Monday, December 20, system.data.sqlclient.sqlexception: warning: fatal error 9001 2010 7:31 AM SSCommitted Group: General Forum Members Last Login: Friday, October 7, 2016 8:42 AM Points: 1,953, Visits: 837 Came in to work this morning to face a bunch of alerts https://msdn.microsoft.com/en-us/library/cc645864.aspx for severity 21 errors."DESCRIPTION: The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database."Hmm.. The drive the log is on was available and logs for other DB were on it. Plenty of space left. Window Application event log showed no errors other than the one listed above. Windows System log showed http://www.sqlservercentral.com/Forums/Topic1037190-1550-1.aspx no errors. I ran dbcc checkdb on the database and the only error reported was that the log was not available.I took the database offline, then brought it online again and all seems good now. DBCC Checkdb gives no errors. DBCC loginfo(0) gives info, so I'm assuming the log is available. Now just trying to figure out what happened.Took a closer look at the SQL error log and I see this:12/20/2010 02:30:01,spid20s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.12/20/2010 02:30:01,spid20s,Unknown,Error: 9001
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 http://dba.stackexchange.com/questions/34061/error-9001-severity-21-state-1-the-log-for-database-db-name-is-not-availab 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 Error 9001, Severity: 21, error 9001 State: 1 The log for database 'DB_NAME' is not available [closed] up vote 3 down vote favorite I have a SQL Server 2008 R2. I got a mail that the backup had failed, I opened the SQL log viewer and started browsing. And i found these two errors a bunch of times. error 1: Date 31-01-2013 13:20:30 Log SQL Server (Current - 01-02-2013 05:13:00) Source spid20s Message Error: 9001, Severity: 21, State: 1. error 2: Date 31-01-2013 13:20:30 Log sql server error SQL Server (Current - 01-02-2013 05:13:00) Source spid20s Message The log for database 'DB_NAME' is not available. Check the event log for related error messages. Resolve any errors and restart the database. After a little googling, I had read a few times that the errors indicated that the DB or log file maybe corrupt. I read that I could confirm it, by running a DBCC CHECKDB 'DB_NAME', so i did, and here are the last to lines of the output: CHECKDB found 0 allocation errors and 0 consistency errors in database 'DB_NAME'. DBCC execution completed. If DBCC printed error messages, contact your system administrator. The output shows that the DB isn't corrupt. But can the log file still be corrupt? I also read that one solution might be run something called "Emergency Mode Repair" to fix the corrupt files. But some users did NOT recommend it. Could another solution be to delete the log file completely and then create a new?. sql sql-server-2008-r2 backup logs share|improve this question asked Feb 4 '13 at 13:20 Arviddk 933310 closed as off-topic by Martin Smith, RolandoMySQLDBA, Marian, Michael - sqlbot, Erwin Brandstetter Dec 26 '13 at 16:59 This question does not appear to belong here. Either it's not database-related or it otherwise conflicts with the scope of our site. See What topics can I ask about here?, What types of questions should I avoid asking? or this blog post fo