Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 Development Tools
 Fatal error 9001 when connect to SQL from aspx page
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Ask SQLTeam Question

0 Posts

Posted - 04/21/2005 :  08:05:32  Show Profile  Visit AskSQLTeam's Homepage  Reply with Quote
Bill writes "There is a fatal error occurred when a web page tried to get data from SQL server. Also When we look at the database from the enterprise manager, there is no database there. However, I can run the SQL select statement from query analyze and get the data rightaway.

System.Data.SqlClient.SqlException: Warning: Fatal error 9001 occurred at Apr 20 2005 10:26AM

The page uses Microsoft data access block to handle the connection and data retrieve.

Thanks for your help,"

Flowing Fount of Yak Knowledge

3564 Posts

Posted - 04/21/2005 :  16:36:58  Show Profile  Visit jhermiz's Homepage  Reply with Quote
Post your code.

Keeping the web experience alive --
Imperfection living for perfection --
Go to Top of Page

SQL Slashing Gunting Master

3246 Posts

Posted - 04/21/2005 :  18:04:50  Show Profile  Visit AjarnMark's Homepage  Reply with Quote
The sentence: "When we look at the database from the enterprise manager, there is no database there." concerns me greatly. When I Googled the error number, I found one item that suggested it might be a problem with the Log file not being available. Although I can't explain why you would be able to query it from QA if that were the problem. I strongly encourage you to run some diagnostics on your database to ensure its integrity.

Go to Top of Page

Starting Member

1 Posts

Posted - 07/09/2014 :  17:40:11  Show Profile  Reply with Quote

Hi saw your post. Here at Network Solution we had a long day with this issue, and finally we expertise and solved this specific error (Fatal Error 9001) at server configuration level.

Result of our work is a shared server where newly created DB are 9001-free thanks to our config scripts (made in years of expertise), preconfigured with the SessionState DB, the ideal for Windows-IIS-ASP.NET-MSSQL shared hosting!

Please contact me at to see if our solution is applicable in your case to definitely solve the root cause of this annoying issue.

Best Regards,
Marco Marsala

Network Solution srl
I-16121 Genova, Italy

Edited by - networksolution on 07/09/2014 17:41:32
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000