How to fix the error in the identifier of the metadata manager size of the missing error in SSAS?

I have this error, which appears from time to time, the error is as follows:

Error -1055653635: Errors in the metadata manager. The dimension with identifier <>, Name of <> referenced by the <> cube does not exist. Error -1055653859: Errors in the metadata manager. An error occurred while loading the Blah cube from the file "\? \ W: \ OLAP \ Data \ BlahBlah Cubes.0.db \ Blah.8.cub.xml".

To begin with, a measurement that, in his opinion, is missing, exists in the SSAS database on the server. The size identifiers seem to correspond to both the cube and the size, so its not the same as the identifier, it has been renamed and now they don't match. Sometimes this can be fixed by effectively removing two cubes that use the same size, and then if you redeploy one of them, the first one can redeploy, but not the second. An unexpected bit is the reason the error repeats when it was previously resolved by deleting the database and restarting it. Is there any specific way to use this dimension that is likely to lead to a confusing metadata manager (?)

+4
source share
3 answers

I would move your SSAS database location to a local drive. From MSDN: "Any UNC path to a network share or any high latency remote storage solution results in an unsupported installation."

http://msdn.microsoft.com/en-us/library/cc280587.aspx

0
source

I don’t know if this is the main reason, but I recreated the same error every time I process the cube.

Let me start the story, I worked on optimizing the cubes, because our reports are slower. I found out that there is a Customer dimension that is actually bigger than the Deprecated Dimension fact, so I created a new customer size, " client1 ", which has customers equal to reality. Thus, I enabled my optimization . Then there were four more cubes for which I must create a completely new client size specific to these cubes. Thus, I created the second dimension of customer customer2 "for another cube, thought about processing it and the boom, I got this error" metadata manager error: \ somelocation ... \\ customer1.dim.0.xml error ". I am very careful read this error message and I thought why his throwing error for dimension β€œ customer1 ” when I try to process dimension β€œ customer2 .” then the processed dimension is β€œ client1 ” and it is processed. Then I processed my second dimension β€œ customer2 " and received it.

I was delighted, but also puzzled and confused that how this happens is interconnected or the MS SSAS document says that you need to follow the sequence for processing. Therefore, to check this, I created another 1 size " customer3 " and then repeated the same steps above. try to process this dimension first, get the error, and then process the first dimension " customer1 ", then process the size " customer3 ", and again I got the error, but for the dimension " customer2 ", and then processed the size " client2 ", after which " Client3 "processed successfully. and now every time I have it processed , I have to follow the sequences . hope this helps.

Hello,

Avi

0
source

I had the same problem. It turns out that the directory in which he complained had empty XML files.

That was my fault:

Errors in the metadata manager. An error occurred while creating an instance of the metadata object from the file, \? \ R: \ ANALYSIS \ Warehouse.0.db \ Role.5.role.xml

When I went to \? \ R: \ ANALYSIS \ Warehouse.0.db \, I found that the Role.5.role.xml file was 0KB. I deleted the file (moved well to be safe), redeployed the solution, and the error went away :)

0
source

All Articles