the mssqlsystemrsource database is a read only database holding system metadata and Microsoft don't want anyone to touch it, it cannot even be backed up via sql, hence it is...

run sp_spaceused whilst connected to the database, the value for reserved will closely approximate to the size of the backup, unless you have a LOT of active, uncommited transactions in...

error 112 = you have run out of space on the disk

based on all the tables being about that size, I agree with you, you'll be glad to hear.

not my post btw 🙂

processmon output can be filtered, its hard to explain so a google on how to use processmon got this:

http://blogs.technet.com/b/askperf/archive/2007/06/01/troubleshooting-with-process-monitor.aspx

you can also search the output for the string mssqlsytemresource.ldf

If this proves...

Its interesting this editorial was first written in 2007, pre the credit crunch.

I wonder if the promotion of risk would be so enthusiastic now we know just how much risk...

yes, I guess mdb could mean mdf.

please post enough of the errorlog to show the errors you get on startup.

why do you say that grant?

by mdb do you mean msdb?

If the msdb database is corrupted SQL should still start, but SQLAgent won't. MSDB should be recovered from backup

http://msdn.microsoft.com/en-us/library/ms190749(v=sql.100).aspx

presuming this is in fact sql 2000 database?

If all the tables have only about 13 pages not too concerned as the tables are too small to benefit from defragmentation, and...

something is preventing the installer accessing that file, only running processmon is going to tell you exactly what is happening.

goggling forescout it sounds like some sort of security tool monitoring...

you say you checked the permissions, did you make any changes and add the permissions I suggested above, this definitely sounds like a permissions error.

Please ensure the account you are...

I highlighted MS11-049 as it is an important security update and should be applied to all SQL servers.

there is by the way a post SP3 version of this patch...

Another thing... if you are not concerned about which SP you apply (you say you are happy to try SP3) then go for the latest service pack which is SP4,...

I have resolved this error in the past by explicitly granting the sql server service account full control on the mssql directory (i.e the resource database files are in the...