Ms Sql Server Error 913
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Error 913 could not find database id Error 913 could not find database id Rate Topic Display Mode Topic Options Author Message Keith ThomasKeith Thomas Posted Friday, August 31, 2007 8:09 AM Grasshopper Group: General Forum Members Last Login: Thursday, February 5, 2015 9:43 AM Points: 11, Visits: 52 Yesterday, the SQL server went down hard and now after restarting, two of my databases are unaccessible. From Enterprise manager, when I drill down, I receive this error after expanding the database:Error 913 Could not find database ID 21. Database may not be activated yet or may be in transition. Also, I do not see in the logs where the two databases were ever recovered. Post #395560 Adam AngeliniAdam Angelini Posted Friday, August 31, 2007 10:31 AM Ten Centuries Group: General Forum Members Last Login: Wednesday, June 29, 2016 3:47 PM Points: 1,200, Visits: 1,177 chances are master database has the wrong ID's in the sysdatabases table. sounds like they are not connected. to verify this, try to move the mdf and ldf files to a different location. if it lets you move them, they are not attached. If they are not attached, then you can do a drop database statement on the 2 databases, move the mdf and ldf files back, then reattach the databases and all should be well. Post #395622 ALZDBAALZDBA Posted Friday, August 31, 2007 12:36 PM SSCertifiable Group: General Forum Members Last Login: Friday, September 30, 2016 3:27 AM Points: 6,822, Visits: 8,829 - check your sqlserver errorlog file to find out what's going on ! (yourserverdrive:\mssql\log\errorlog = to be opened with notepad) JohanDon't drive faster than your guardian angel can fly ...but keeping both feet on the ground won't get you anywhere - How to post Performance Problems- How to post data/code to get the best help- How to prevent a sore throat after hours of presenting ppt ?"press F1 for solution", "press shift+F1 for urgent solution" Need a bit of Powershell? How about thisWho am I ? Sometimes this is me but most of the time this is me Post #395659 Keith ThomasKeith Thomas Posted Friday, August 31, 2007 12:59 PM Grasshopper Group: General Forum Members Last Login: Thursday, February 5, 2015 9:43 AM Points: 11, Visits: 52 I just fixed the problem, the server was set to use Windows NT Fibers so it was starting in fiber mode instead
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 MSSQLSERVER Will Not Start - Event ID 913 and 1814 up vote 0 down vote favorite I need some serious help. I have a major database server http://www.sqlservercentral.com/Forums/Topic395560-5-1.aspx down and am scratching my head at how to fix it. The server was hit by rolling black outs last week in Dallas and sense then, Microsoft SQL 2005 SP2 will not start up. I am getting the following errors (both when starting the service and while trying to execute mssqlsrv.exe -c -f -m: Event Type: Error Event Source: MSSQLSERVER Event ID: 913 Could not find database ID 3. Database may not be activated yet or may be in transition. Reissue the query once http://serverfault.com/questions/232406/mssqlserver-will-not-start-event-id-913-and-1814 the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. and... Event Type: Information Event Source: MSSQLSERVER Event ID: 1814 Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. I have tried to rename the tempdb.mdf to tempdb.old with no success. I have checked and have 193 GB of free hard drive space. What else might cause this problem? Could the server need a chkdsk ran on it or do I need to be looking at some area of the database server? Any help is greatly appreciated. Thank you in advance. sql-server windows-service startup share|improve this question asked Feb 7 '11 at 23:01 ThaKidd KG5ORD 234616 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted Database ID 3 is the model database. Without it the SQL Server won't start. Open a cmdshell and navigate to the C:\program files\microsoft sql server\mssql\binn\ folder (or where ever the .exe files are stored). Run "SQLSERVR.exe -c -m" This will run the SQL Server within
/ SQL Server / Errors / Error: 913, Severity: 16, State: 1 Error: 913, Severity: 16, State: 1 Robert Fertig April 8, 2016 Errors Leave a comment 145 Views Share Facebook Twitter Google + Stumbleupon LinkedIn Pinterest Related Articles SQL Server Error 10060 April 13, 2016 A network-related or instance-specific error occurred April 13, 2016 Azure SQL failed to export the database to storage account April 12, 2016 [Total: 1 Average: 5/5] Error: 913, Severity: 16, State: 1. Message Could not find database ID X. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. Fix Select from sys.databases Check default database for logins Check if your database is attached or online. Receive UpdatesNo spam guarantee. Error: 913 Error: 913 Severity: 16 State: 1 Severity: 16 State: 1 2016-04-08 +Robert Fertig Share Facebook Twitter Google + Stumbleupon LinkedIn Pinterest Tags Error: 913 Error: 913 Severity: 16 State: 1 Severity: 16 State: 1 Previous Error: 14151, Severity: 18, State: 1 Next Azure SQL failed to export the database to storage account Check Also Error: 14151, Severity: 18, State: 1 [Total: 1 Average: 5/5] Error: 14151, Severity: 18, State: 1. Message Replication-Replication Distribution Subsystem: … Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website six × 6 = Advertisement PopularRecentCommentsTags Configure MSDTC on Windows Server 2012 Cluster July 31, 2013 3,507 SQL Server Move TempDB to different drive October 3, 2013 1,159 Repair a corrupt SQL Server Installation August 23, 2013 926 Create SSIS with dynamic variable connections August 29, 2013 889 Change Jobs Owner to sa for all SQL Server Agent Job March 21, 2014 826 SQL Server Error 10060 April 13, 2016 A network-related or instance-specific error occurred April 13, 2016 Azure SQL failed to export the database to storage account April 12, 2016 Error: 913, Severity: 16, State: 1 April 8, 2016 Error: 14151, Severity: 18, State: 1 April 8, 2016 Anjan Kant: nicely explained, how to implemen