Could not open File Control Bank (FCB) for invalid file ID

Question

Could not open File Control Bank (FCB) for invalid file ID

WayneS

SSC Guru

Points: 95460
More actions
March 13, 2013 at 10:57 am

#275184

Initial entry in the SQL Error Log:
Error: 5180, Severity: 22, State: 1.
Could not open File Control Bank (FCB) for invalid file ID 2816 in database 'WSS_Content_FirmMySites'. Verify the file location. Execute DBCC CHECKDB.
So, run DBCC CHECKDB WITH ALL_ERRORMSGS, NO_INFOMSGS
Complete, unedited results:
Msg 7987, Level 16, State 1, Line 1
System table pre-checks: Object ID 3 has chain linkage mismatch. (1:223355)->next = (1:223357), but (1:223357)->prev = (1:223356). Check statement terminated due to unrepairable error.
Try DBCC CHECKALLOC
Msg 7987, Level 16, State 1, Line 1
System table pre-checks: Object ID 3 has chain linkage mismatch. (1:223355)->next = (1:223357), but (1:223357)->prev = (1:223356). Check statement terminated due to unrepairable error.
This is a new client, so see when DBCC CHECKDB was last successfully run via DBCC PAGE(dbname, 1,9,3) WITH TABLERESULTS:
2011-10-31 01:10:06.737
Check the previous backup in a parallel database: same errors as above.
Backups older than this have already been deleted.
This database is part of a sharepoint instance.
DBCC CHECKDB did generate a stack dump.
Is there anyway to fix this corruption?
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
Links:
For better assistance in answering your questions
Performance Problems
Common date/time routines
Understanding and Using APPLY Part 1 & Part 2
March 14, 2013 at 4:08 am

This was removed by the editor as SPAM

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

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

SQLRNNR SSC Guru Points: 281334 More actions · Answer 1

Are you asking if there is a way to fix without losing data?

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

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

Restore from last good backup, that's irrepairable.

If there's absolutely no backup whatsoever, export all the documents, lists, etc from sharepoint (not a SQL data export), then drop and recreate the sharepoint site. You'll probably lose some stuff.

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

SQLRNNR SSC Guru Points: 281334 More actions · Answer 3

GilaMonster (3/13/2013)
Restore from last good backup, that's irrepairable.
If there's absolutely no backup whatsoever, export all the documents, lists, etc from sharepoint (not a SQL data export), then drop and recreate the sharepoint site. You'll probably lose some stuff.

I had just been talking to Wayne about the eventuality of most likely having to recreate the sharepoint site.

Have a fun day with this new client, Wayne. :crying:

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events