Metadata Manager Problem error issue

Asked By 980 points N/A Posted on -
qa-featured

Hi all,

I have a system failure. My SAS services failed. The system was restarted in order to see if all the services are up and running. When all thing was checked, I encountered this message that read as Errors in the metadata manager, SAS Service The database ‘CAYA_DataWarehouse_Dev’ not found on the server”.

It seems that the database was no longer found. I checked on the directories and folder the database still exist. What I'm pointing out now is, how could I restart the SAS service that fails to run? Should I reinstall SAS on this machine, or I might restore my backup of the database? I cannot figure out if the services that went down or my database is corrupted that is why it could no longer be found, even though physically the file is there in the folder.

Could somebody help me solve my issue?

 

Microsoft Visual Studio

The database ‘CAYA_DataWarehouse_Dev’ not found on the server”.

Thanks.

SHARE
Best Answer by Riley weaver
Answered By 0 points N/A #124847

Metadata Manager Problem error issue

qa-featured

Hi there,

I have read your question about getting problems in SAS server error during your working, I think that it is a case of data folder that contains MOLAP data getting corrupted. To resolve this, issue your StopAnalysis Services service. Ensure that you do have a source deployment file for database that got corrupted. Drop the database files from dataDir folder and then Start Analysis Services service launch database from source files and Process database.

Thanks.

Best Answer
Best Answer
Answered By 10 points N/A #124848

Metadata Manager Problem error issue

qa-featured

Hello,

The whole process is some kind of experts work. If you really want to understand this whole thing, than you must have to try this whole procedure with a machine which have a SASS installed and also a MSSQL server too. Now I am telling this thing in brief. You have to manually insert the CAYA_DataWarehouse_Dev file in the parameters files. Then you have to find out an integration service deployment manifest from deployment folder. Now you have to install that and then the parameters will be ready to go. Now reboot and the problem will be solved. For more study I am giving this link. I am sure who know a little about this matters can solve this kind of problem.

http://blogs.opera.com/news/

Thank you,

Riley weaver

Related Questions