Udostępnij za pośrednictwem


MSSQLSERVER_7908

Details

Product Name

SQL Server

Product Version

10.0

Product Build Number

10.00.1281.60

Event ID

7908

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

DBCC2_FS_INVALID_COLUMN_LEVEL_FILE

Message Text

Table error: The file 'FILE' in partition ID PN_ID is not a valid Filestream file.

Explanation

The name of a FILESTREAM file in a column directory is a ROWGUID. If a file name in a column directory cannot be converted to a ROWGUID, the file is not a valid file.

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="470045b0-ebe9-44a7-b456-480e7a516a2c" resourceStringProxyID="MSSQL_ENG007908"><exportStatus>Do Not Export</exportStatus><importStatus>Unchanged</importStatus><inActive>No</inActive><inserts></inserts><message><cause>This error happens when an invalid file was found in column directory during DBCC CHECKDB. The name of a Filestream file in a column directory is a ROWGUID. If a file name in a column directory can not be converted to a ROWGUID, the file is an invalid file.</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>7908</winRegEventID><winRegEventSource>MSSQLSERVER</winRegEventSource></event><msuid></msuid></message><numericID>7908</numericID><owner>syjiang</owner><pssReview><pssComments></pssComments><pssDebugger>No</pssDebugger><pssEngineer></pssEngineer><PSSSupportability>No</PSSSupportability></pssReview><suspect>No</suspect><symbolicName>DBCC2_FS_INVALID_COLUMN_LEVEL_FILE</symbolicName><text>Table error: The file "%.*ls" in the partition ID %I64d is not a valid FileStream file.</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 file was not created from the Filestream manager.

  • The hard disk was corrupted.