Fatal error 9001 on shared SQL Server 2008
- by user643192
I've asked this same question on StackOverflow, but I might actually have a better chance for an answer here so am posting here as well.
I know this question has been asked here before, but none of the suggestions have worked for me.
I have an ASP.NET MVC (v. 3) website on a shared server. The website was working fine for a few weeks now, until I started getting a Fatal Error 9001 error straight after login.
Because this is a shared server, there are only very limited things I can do with the database (and I don't know that much about databases anyway). The help desk insist that there is nothing wrong with their server. I got various suggestions from them:
Upgrading to the business plan because I am out of space (first suggestion)
Even though the .mdb file is small, the .ldb can grow very quickly. The .ldb file is probably taking up all the space. I have 100MB available, the database size is 16.5MB. Can the .ldb file take up the remaining space? On querying this with the helpdesk, they admitted that my entire db is only 25MB.
There is something wrong with my SQL queries and I should check the website. I'm using EF with linq to SQL. Everything was working fine until now... Can there be something that goes wrong in the queries that causes this sort of error?
There is nothing wrong to be seen in the db logs, so this error cannot possibly have happened. I should log it next time it happens and contact again.
I found some posts suggesting that restoring a DB backup can get rid of the issue. I do not have a recent backup, and can't take a new one because of a fatal error 9001 occurring.
Since this is a shared server I have about 0 authority to execute anything against the DB (think CHECKDB, truncating the log, etc.). So I am at my wits end pretty much.
What else can I do/try to get my website moving again?
