Udostępnij za pośrednictwem

  • Artykuł

MSSQLSERVER_7904

Details

Product Name

SQL Server

Product Version

10.0

Product Build Number

10.00.1281.60

Event ID

7904

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

DBCC2_FS_MISSING_FILE

Message Text

Table error: The filestream file for column ID C_ID, ROWGUID RG_ID in object ID O_ID, index ID I_ID, partition ID PN_ID was not found.

Explanation

A column value of a partition does not have a matching FILESTREAM file in the corresponding FILESTREAM column directory.

User Action

Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.

Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.

Restore from Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

Not applicable. This error cannot be repaired. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS).

Internal-Only

<xmrFileHeader><buildNo>9.00.1281.60</buildNo><component>SQLEngine</component><dsDbName></dsDbName><dsProjectName>SQLServer2005</dsProjectName><exportDate>2005-08-22T14:00:12</exportDate><importDate>2005-08-22T12:43:00</importDate><prodContact>pingwang</prodContact><prodName>SQL Server</prodName><prodVer>9.0</prodVer><sourceFileDepotPath></sourceFileDepotPath><sourceFileExt></sourceFileExt><sourceFileName></sourceFileName><userDefined></userDefined><xmrFilePath>.\sqlXMR.xml</xmrFilePath></xmrFileHeader><resourceString resourceStringGuid="d047920c-f864-4338-b15f-49820886fbc5" resourceStringProxyID="MSSQL_ENG007904"><exportStatus>Do Not Export</exportStatus><importStatus>Unchanged</importStatus><inActive>No</inActive><inserts></inserts><message><cause>In DBCC CHECKDB, a column value of a partition did not find a matching Filestream file in the corresponding Filestream column directory.</cause><causeCorrectiveActionStatus></causeCorrectiveActionStatus><correctiveAction>Restore last known good database from backup or run repair.</correctiveAction><error><exMsgBoxID></exMsgBoxID><exMsgBoxSource></exMsgBoxSource></error><event><eventCategory></eventCategory><eventFacility></eventFacility><eventLanguage></eventLanguage><eventSeverityType></eventSeverityType><eventType></eventType><momEvent>No</momEvent><momOwner></momOwner><winRegEventID>7904</winRegEventID><winRegEventSource>MSSQLSERVER</winRegEventSource></event><msuid></msuid></message><numericID>7904</numericID><owner>syjiang</owner><pssReview><pssComments></pssComments><pssDebugger>No</pssDebugger><pssEngineer></pssEngineer><PSSSupportability>No</PSSSupportability></pssReview><suspect>No</suspect><symbolicName>DBCC2_FS_MISSING_FILE</symbolicName><text>Table error: The FileStream file for column ID %d, ROWGUID %.*ls, in object ID %d, index ID %d, partition ID %I64d was not found.</text><type></type><ueReview><assignedTo></assignedTo><bugID></bugID><bugRequired>No</bugRequired><comments></comments><docStudio><dsTopicId></dsTopicId><export>Yes</export></docStudio><editor></editor><revisedStringText></revisedStringText><workStatus>Not Reviewed</workStatus><writer></writer></ueReview><userDefined><eventLoggingLevel></eventLoggingLevel></userDefined></resourceString>

Possible Causes

This error can be caused by one of the following problems:

  • The corresponding Filestream file was not created when a column value was inserted or updated.

  • The corresponding Filestream file was accidentally deleted during a Filestream DML operation.

  • The corresponding Filestream file was deleted by non-Filestream users. For example, Transactional File System (TxF) was not up when this occurred.