SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Fehler in Metadaten-Manager in SSAS-Projekt


Fehler in Metadaten-Manager in SSAS-Projekt

Author
Message
christoph.meyer
christoph.meyer
SSC-Enthusiastic
SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)

Group: General Forum Members
Points: 140 Visits: 117
Hi allerseits,

wir sind seit Ende letzter Woche mit einem hässlichen Fehler konfrontiert und wissen aktuell keinen Ausweg.

Wenn man das SSAS-Projekt in Visual Studio 2010 öffnen möchte, kommt folgender Fehler:

Fehler im Metadaten-Manager. Die Dimension mit der ID 'Dim Produktgruppe' und dem Namen 'Dim Produktgruppe', auf die der T04_PlUmsatzSonneBP-Cube verweist, ist nicht vorhanden.
Fehler im Metadaten-Manager. Fehler beim Laden von 'T04_PlUmsatzSonneBP' (cube) aus der Datei '\\?\C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data\OLAP.0.db\T04_PlUmsatzSonneBP.8.cub.xml'.


Auch die Verbindung im Management-Studio wird mit einer Fehlermeldung quittiert.

Eine Rücksicherung der Dateien aus dem Ordner "C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data\OLAP.0.db" von vorangegangenen Tagen brachte keinen Erfolg... es kommen immer wieder ähnliche Fehler.

Zu diesem Thema konnte ich folgendes in einem Blog finden: Klick. Allerdings bezieht sich das auf den SQL-Server 2008 (R2), und nicht auf den 2012er. Generell hätte seine Lösung auch bei uns funktioniert, allerdings haben wir kein "Offline-Projekt", welches wir neu deployen könnten. Der Grund hierfür ist, dass wir aktuell ein neues Reporting- und Planungswerkzeug integrieren, welches es quasi verbietet, offline-SSAS-Projekte aus Visual Studio zu deployen (sonst würden wir die durch diese Software automatisch erzeugten Cubes und sogenannten CheckOut-Dimensionen zerstören).

Jetzt stehen wir da, und wissen nicht, wie wir das SSAS-Projekt wieder "zum Leben erwecken" können. Die Datei, die in der Fehlermeldung angemeckert wird, wird aus einem Backup des Verzeichnisses auch automatisch nach Dienststart des Analysis-Service gelöscht (Zusammen mit ca. 1400 weiteren Dateien!!).

#############################

Hi everybody,

since last week, we are faced with an "ugly" error message when opening an SSAS-Project in Visual Studio 2010:


Errors in the metadata manager. The dimension with ID of ‘Dim Produktgruppe’, referenced by the ‘T04_PlUmsatzSonneBP’ cube, does not exist.
Errors in the metadata manager. An error occurred when loading the T04_PlUmsatzSonneBP cube, from the file, ‘\\?\C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data\OLAP.0.db\T04_PlUmsatzSonneBP.8.cub.xml’.


Same or equal error message when trying to connect with Microsoft Management Studio.

We restored a backup of the folder, which was a few days older, but this did not solve the problem. The error-message still raises up. There is a blog, where such behaviour was previously mentioned on sql server 2008 (R2) here: Click

But the given solution does not work in our environment, because we do not have an offline SSAS-Project (offline-development is not allowed because of a new tool for reporting and planning-purpose which creates its own cubes and dimensions out of the tool. So a deployment could lead to deleting their data!)

So, what else could we do to restore the SSAS-Project? By the way, about 1400 files are automatically deleted from the mentionend "OLAP.0.db"-folder when starting the Analysis Service after a restore of the corrupted data!?
christoph.meyer
christoph.meyer
SSC-Enthusiastic
SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)

Group: General Forum Members
Points: 140 Visits: 117
Hi,

after some try an error, we could restore the complete SSAS-World Smile

All we had to do is a complete file-restore of the folder "\C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data" and not only the containing OLAP.0.db one. :-).

For the restore, we went back to a date before the error was logged the first time in "C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log\msmdsrv.log".
christoph.meyer
christoph.meyer
SSC-Enthusiastic
SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)

Group: General Forum Members
Points: 140 Visits: 117
Hi,

after 2 weeks of developing, again we had the Metadata-Error when connecting to SSAS with Management Studio or Visual Studio. This time, we looked at the log-file and the first time it happened, was while we had a workshop for our new 3rd-party planning-tool and no BI-developer was changing anything at this time or recently before the error.

So, again we restored the file-backup and everything worked fine again.

But this is everything but a stable development environment! SP1 is installed already, but no cumulative patch.

Any hints from the community? The key-user-tests for the new software will start in may.... Wink
christoph.meyer
christoph.meyer
SSC-Enthusiastic
SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)

Group: General Forum Members
Points: 140 Visits: 117
So, next crash happened.

This time, it was not the test-server, but the productive one Angry ... and this time really nobody has made any changes to the olap-solution before!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search