Error 9001 Sql Server 2005
Contents |
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 sql server error 9001 tempdb Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges sql server fatal error 9001 Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a microsoft sql server error 9001 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 Diagnosing Microsoft SQL Server error 9001: The log for the database is
Fatal Error 9001 Occurred Sql Server
not available up vote 15 down vote favorite 2 Over the weekend a website I run stopped functioning, recording the following error in the Event Viewer each time a request is made to the website: Event ID: 9001 The log for database 'database name' is not available. Check the event log for related error messages. Resolve any errors and restart the database. The website is hosted on a dedicated server, so I am able to RDP warning fatal error 9001 occurred sql server into the server and poke around. The LDF file for the database exists in the C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA folder, but attempting to do any work with the database from Management Studio results in a dialog box reporting the same error - 9001: The log for database is not available... This is the first time I've received this error, and I've been hosting this site (and others) on this dedicated web server for over two years now. It is my understanding that this error indicates a corrupt log file. I was able to get the website back online by Detaching the database and then restoring a backup from a couple days ago, but my concern is that this error is indicative of a more sinister problem, namely a hard drive failure. I emailed support at the web hosting company and this was their reply: There doesn't appear to be any other indications of the cause in the Event Log, so it's possible that the log was corrupted. Currently the memory's resources is at 87%, which also may have an impact but is unlikely. Can the log just "become corrupted?" My question: What are the next steps I should take to diagnose this problem? How can I determine if this is, indeed, a hardware problem? And if it is, are there any options beyond replacing the disk? Thanks sql-server
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's sqlserver 9001 On Home » SQL Server 2008 » SQL Server 2008 Administration
The Log For Database Tempdb Is Not Available Error 9001
» Log not available error 9001 19 posts,Page 1 of 212»» Log not available error 9001
The Log For Database Is Not Available. Check The Event Log For Related Error Messages
Rate Topic Display Mode Topic Options Author Message shaun.stuartshaun.stuart Posted Monday, December 20, 2010 7:31 AM SSCommitted Group: General Forum Members Last Login: Friday, October 7, 2016 8:42 http://serverfault.com/questions/238394/diagnosing-microsoft-sql-server-error-9001-the-log-for-the-database-is-not-avai/238398 AM Points: 1,949, Visits: 837 Came in to work this morning to face a bunch of alerts 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 http://www.sqlservercentral.com/Forums/Topic1037190-1550-1.aspx 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 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 http://dba.stackexchange.com/questions/34061/error-9001-severity-21-state-1-the-log-for-database-db-name-is-not-availab Learn more about Stack Overflow the company Business Learn more about hiring developers or http://www.dnnsoftware.com/forums/threadid/463118/scope/posts/sql-exception-fatal-error-9001 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: error 9001 Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error 9001, Severity: 21, 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 fatal error 9001 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 (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
Marketing Community Engagement Ideas Answers Discussions Groups Wikis Events Mobile ReadyEvoq Intranet Governance Employee Portal Collaboration Gamification User Profiles Personalization Document Management Analytics IntegrationsEvoq: CMS FeaturesEvoq OnDemandProduct DemosCompare ProductsCompare DNN Platform to Evoq Solutions Customer EngagementMarketing & ECommerceCustomer SupportProduct DevelopmentMember EngagementEmployee IntranetOur Customers Learn More Test DrivesSchedule A DemoWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesVideosEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes Partners DNN Partners Partner Directory Become a DNN Partner Community Participate Community Exchange Community Voice Community Showcase Community Forums Working Groups Members Module ContestLearn Project History Documentation Center Community Blog Video Library Wiki Development Online Help RoadmapConnect DNN MVP Community Leaderboard Community Newsletters Community Events Community HangoutDownload DNN Forge Language Packs Manuals Nightly BuildsSecurity Policies Security Center Blog About Leadership Management InvestorsNews Press Releases News Coverage Press KitCareersContact DNN Download DNN Platform Whitepapers Manuals Support Store DNN Modules DNN Themes Store Blog Evoq Preferred Services Login REGISTERBecome a DNNizen > Submit DNN Products Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website Performance Evoq Engage Overview Community Management Gamification Advocate Marketing Community Engagement Mobile Ready Evoq Intranet Governance Employee Portal Collaboration Gamification User Profiles Personalization Document Management Analytics Integrations Evoq: CMS Features Evoq OnDemand Product Demos Compare Products Compare DNN Platform to Evoq Solutions Customer Engagement Marketing & ECommerce Customer Support Product Development Member Engagement Employee Intra