MSSQLSERVER_7905
Details
Product Name |
SQL Server |
Product Version |
10.0 |
Product Build Number |
10.00.1281.60 |
Event ID |
7905 |
Event Source |
MSSQLSERVER |
Component |
SQLEngine |
Symbolic Name |
DBCC2_FS_INVALID_ROWSET_DIRECTORY |
Message Text |
Database error: The directory 'DIRECTORY' is not a valid Filestream directory. |
Explanation
The name of a rowset directory is the partition ID of the partition, except for the special rowset directory names such as 'ghost'. If a rowset directory name cannot be converted to a partition ID, the directory is not a valid rowset 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="cf19fbbb-7158-45f2-8778-8f3cad7f574a" resourceStringProxyID="MSSQL_ENG007905"><exportStatus>Do Not Export</exportStatus><importStatus>Unchanged</importStatus><inActive>No</inActive><inserts></inserts><message><cause>This error happens when an invalid Filestream directory was found during DBCC CHECKDB. Except some special rowset directory name (for example, 'ghost'), the name of a rowset directory is the partition ID of the partition. If a rowset directory name can not be converted to a partition ID, the directory is an invalid rowset 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>7905</winRegEventID><winRegEventSource>MSSQLSERVER</winRegEventSource></event><msuid></msuid></message><numericID>7905</numericID><owner>syjiang</owner><pssReview><pssComments></pssComments><pssDebugger>No</pssDebugger><pssEngineer></pssEngineer><PSSSupportability>No</PSSSupportability></pssReview><suspect>No</suspect><symbolicName>DBCC2_FS_INVALID_ROWSET_DIRECTORY</symbolicName><text>Database error: The directory "%.*ls" is not a valid FileStream directory.</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 directory was not created from the Filestream manager.
The hard disk was corrupted.