File system error: A FileStore error from WriteFile occurred

Question

Error:   Code: 0x00000000
   Source: SRC Process dimensions Error:
   Description: File system error: A FileStore error from WriteFile occurred. Physical file: \\?\<pathto filename> attribute.asstore. Logical file: . .
Errors in the OLAP storage engine: An error occurred while the <attribute id> attr
ibute' attribute of the <dimensionname> dimension from the '<database>' database was being processed.
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
End Error

I encountered this while incrementally processing a dimension via AMO script in SSIS.  Does anyone have ideas on what this error means and ways to avoid?

Answer 1

I unprocessed and reprocessed to resolve this.

Answer 2

What do you mean by "Unprocess a cube"?

How did you unprocess a cube?

Thanks.

Chris

Answer 3

Description: File system error: A FileStore error from WriteFile occurred. Physical file: \\?\<pathto filename> attribute.asstore. Logical file: . .

Yikes.  This has happened to me a few times within the cubes and dimensions.  I also get the writefile error, which appears to be a bad reference to a file that no longer exists.  I tried to use other processing methods ot process the dimension that was broken, and now I don't even get the errror anymore.  Now the processing dialog box just hangs, saying that it is building a processing schedule.  I do not want to unprocess the dimension, because I will have to reprocess the entire database.  Does anyone have a clue as to how to avoid this, or why it happens?  How could one fix it without unprocessing?

Thank,

Sally

 

 

Answer 4

That's a while ago. My problem was actually caused by the size of a dimension that I was processing.

It was just too big. Later I reduced the size, and the error disappeared.

 

Thanks anyway.

 

Chris

Answer 5

I have been experimenting with large dimensions (or at least what we consider to be large - ~100mm members), and have learned the string store (filename ends in .asstore) cannot exceed 4 gig.  Is this the same thing you have run into, or have you found another limitation?

 

John

Answer 6

I cannot seem to get rid of this error.  My specific error message is:  "File system error: A FileStore error from WriteFile occurred. Physical file:  \\?\I:\[Custom Temp Directory]\MSMDCacheRowset_6648_308_3gz8as.tmp.  Logical file: . ."  The error occurs when trying to do a full process of a 5 million record dimension with ~130 attributes.  I am trying to process this on a 8 GB RAM, 4 core, 32-bit Windows Server Enterpise box running SQL Server 2005 Standard.  I have successfully processed this dimension before, but now it is failing regardless of the following troubleshooting efforts:

1. unprocess and re-process trying alternative processing types
2. modify memory parameters with Analysis Services:  Memory \ TotalMemoryLimit to 95 from 80, confirm 3GB switch activated in boot.ini
3. try removing unneeded dimension attributes (I had successfully processed with 180 columns, now it's failing even with 130 attributes)
4. modify processing dimension property to BY TABLE from BY ATTRIBUTE (research indicates that the BY TABLE has resulted in FileStore error for others and is harder on a system memory-wise, so this change was quickly reversed)
5. materialize underlying view in DSV that serves as source for dimension
6. again try to unprocess and re-process
7. try setting the MemoryLimitEnabledProperty in msmdsrv.ini to 0 per Chris Webb forum post
8. generate create script of dimension and recreate with new name and try to process that dimension
9. restart server
10. switch from MOLAP to ROLAP - this worked when processing the dimension but failed with the same error when processing the cube during the dimAccount processing

The only option I know of that's left is to fix the hardware (get bigger, better and 64-bit), but that's not a feasible short-term solution.  Can anyone offer alternative things to try?