SSAS Error :Error ErrorCode="3238133825" Description="File system error: A FileStore error from WriteFile occurred. Physical file:

SSAS Error :Error ErrorCode="3238133825" Description="File system error: A FileStore error from WriteFile occurred. Physical file: \\?\E:\MSSQL\Log\DbHWE.2.db\Network Equipment.0.dim\5729.H4 OBJ DB ID.ksstore

When you process a dimension by using the Process Update processing option or the Process Default processing option, the string file store (.asstore) is appended instead of being overwritten. This behavior reduces the process time even if no change is made on the string attribute. If the dimension is frequently processed that way, the string file store will become very large. When the string file store reaches 4 GB, you can no longer process the dimension by using the Process Update processing option or the Process Default processing option. You will receive an error message:
“File system error: A FileStore error from WriteFile occurred. Physical file: ....”

If you are doing ProcessUpdate on a regular basis, I would suggest doing processFull now and then. When you process a dimension by using the Process Full processing option, all the data of the dimension will be dropped and reconstructed. The string file store will be smaller.

There is another way also when ever you face this error  you can process the dimension ProcessData Then it will work .

Comments

Post a Comment

Popular posts from this blog

SSAS : A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). + Solution

Problem : have installed Analysis service on my server machine through remote login from my service account. I am able to open Analysis services from there. When I open SSMS from the same service account on my local machine, I am not able to connect to that Analysis service. It is giving me error by saying : "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond 10.245.192.111:2382(System)." Solution : Based on my research, the issue was caused by the Browser Service account was changed to the domain account. In your scenario, you can try to connect to the Analysis Service using <Servername>:2383 instead of instance name. Or you can change the Browser Service account to "Local System".
Read more

SSIS Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces

Image
Problem : When we have Multiple Namespaces in the Xml Source which we need to load the Data from   as we shown below Then we will face a issue in generating XSD for that XML Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces. (Microsoft Visual Studio) Solution : First we need to avoid multiple namespaces to transform your source file to a format that doesn’t refer to the namespaces. SSIS has an XML task that can do the transformation. 1) Add the XML task to an SSIS   Control Flow and edit it. 2) Change the OperationType property value to XSLT, the SourceType to File connection and the Source to your source file that has the problem. 3) Set the SaveOperationResult property to True and expand the OperationResult branch. Set DestinationType to File Connection and the Destination to a new XML file ( ModifiedInput.XML). 4) Add the below script to a new file and save it with an xslt file extension (Input.XSLT) <
Read more