Skip to main content

Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space.

I am working on SQL Server 2005 for quite sometime now. For past couple of weeks I am facing a strange error often but not always!!

Refer the screenshot below to know the actual error:


Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)

My system configuration:

I am using Windows XP Media center edition with SP2 and 1 GB RAM. I have SQL Server 2005 (version 9.00.1399.00)

What's the solution?

I came across this KB article - http://support.microsoft.com/kb/899436. As per the KB article it looks like this error occurs because of a ACL issue here.

If it's an ACL issue I presume that SQL 2005 should not work for me always. I am wondering how it works for me once I restart my laptop couple of times.

Bottomline is I haven't yet found a solution for this. If at all you have run into this issu,e and have solved it, do write back to me.

Comments

Krishnan Sriram said…
Check if .MDF and .LDF files are in correct location.
Check to see if both the above mentioned files have read/write permissions. If the files are just read-only, kindly provide write permissions too

I had the same issue and by looking into the properties of .MDF and .LDF, I was surprised to see that they were read-only (don;t know how this happened). But on correction, things were back to normal. Hope this helps
Anonymous said…
had this issue today

managed t solve it;

apparently something had a hold of the MSDB file which was locking it from use

if you go to computer managementyou will see an option for sql2005 i simply stopped the service for the instance i was trying to connect to then restated it

this will of kicked any connections to the MSDB file which allowed me access once again
Anonymous said…
Reloading SQL also works. I had to do that using Express.
ksnkarthik said…
Had this issue today.

When I restarted all the services of SQL Server manually and the things are back to normal.

Thanks for the posting.
Anonymous said…
My problem was that the MSDBData.mdf file was compresses for some reason...
Anonymous said…
ksnkarthik thnxxxxxx
when i restarted the services the sql services the things are back to normal..
thank u very much.......

Popular posts from this blog

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul

AWS fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

While using AWS and trying to copy a file from a S3 bucket to my EC2 instance ended up with this error message. Command Used: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ Error: fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request The error goes off if we add the region information to the command statement. I am using Asia Pacific (Mumbai) so used ap-south-1 as the region name. Modified Command: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ --region ap-south-1

[Non Tech] Want to know the recipe for Omelette :)

Fed up with Bread - Jam and Curd Rice, today i wanted to eat Omelette. Interesting part is I wanted to cook it myself :) So in the first picture you see all the items which are needed for preparing an Omelette. When I had a closer look at the eggs I see that almost all the eggs are broken. But believe me when I bought it couple of days back it was in perfect condition! I was wondering whether the eggs have become rotten or pretty old to consume! I tried taking an egg and break it but couldn't break it at all :) Since I have kept in the freezer all the eggs have frozen and looked like a iron ball :) After trying for few minutes of trying i removed the shell of the egg and then kept that iron ball :) into a bowl and placed it within Oven. I heated it for 1 minute and checked. It melted only to a limit. So i just set it for another 2 minutes and checked it later. It has melted but the part of the egg white has become a Omelette :( I didn't leave it there. I took the bowl out of