SQL Server service won't start due to the mssqlsystemresource database files not accessible

Question

SQL Server service won't start due to the mssqlsystemresource database files not accessible

skelboo

Old Hand

Points: 300
More actions
June 9, 2011 at 7:33 am

#142731

Hi,
I have the following problem. We have a Production running SQL Server 2005 SP2 and it's replicated to the DR via SRDF replication. The issue is that I have split the SRDF link, then patched the Production with SP3 and then established the link for replication. Now when I want to patch the DR to SP3, SQL Server doesn't startup. Mind you, due to time constraints I couldn't patch DR at the same time as Prod. The error I'm getting is as follows:
The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
FCB::Open: Operating system error 2[error not found] occurred while creating or opening file 'E:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\mssqlsystemresource.mdf'. Diagnose and correct the operating system error, and retry the operation.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Does the file exist? Does SQL have permission to that folder?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

skelboo Old Hand Points: 300 More actions · Answer 2

Hi,

Yes the file does exist and SQL does have permissions there. And I can't even get to back and restore this database because it's not vissible.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

You can't back it up or restore it anyway. It's a hidden DB.

What does the SQL error log say?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Brandie Tarvin SSC Guru Points: 173068 More actions · Answer 4

Silly question that may not have anything to do with anything... Are you sure that the drive / folder in question has enough disk space for that database to even open up? That may cause it to "not be found."

Though, truthfully, you need to answer Gail's question before chasing down the wild goose I just set loose in your path.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.