Metadata Manager Repository Configuration Error

I'm trying to install XI 3.1 Metadata Manager FP1, and run into the following error:
"Metadata Management Repository Configuration
Metadata Management Repository configuration failed with the following error.
The plugin CrystalEnterprise.MM.Repository does not exist in the CMS (FWM 0217)
IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
InfoObject CrystalEnterprise.MM.Repository was not found.
Unable to initialize Metadata Management Core.
Utility failed with code 3.
You need to re-run the installer again."
I ran it again and got the same error. I have a SQL Server database set up, ODBC connections test successfully. Anyone know how to resolve this issue?

I ran into the same error, and a colleague was able to figure it out. I thought I'd share that in case someone else runs into this.
We have two CMS servers. When I was installing MM's CMS components on the first server, it failed late in the install because it couldn't find an object that was installed earlier. It must have been accessing the second server, even though I entered "localhost" as the CMS location. By disabling and stopping the second server in the CMC, I was able to complete the install.
Regards,
Sean

Similar Messages

Metadata Manager Repository configuration failed

Hello,
I am tring to install Metadata Manager. I am running BOE XI 3.1 SP2 FP2.5. I am installing "SBOP Metadata Management XI 3.1 (12.1) on Windows". My database is a local install of MS SQL Server 2005.
I get all the way through the install process and the following error message pops up:
Metadata Management Repository configuration failed with the following error.
The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
SQLSTATE=08S01, SQLCODE=0.
Utility failed with code 4.
You need to re-run the installer again.
Once I click the "OK" button, the install reverses and uninstalls everything.
Any help would be greatly appreciated.
Thank you,
Scott

how are you specifying the SQL Server 2005 server name in the repository configuration screen ?
are you able to ping the machine where SQL Server is running ?
you have to give the Machine Name or IP address in the Repository connection screen, don't give machine\instanceName

Repository configuration error

Hello,
Does anyone know what might be causing the following exception? We're getting this thrown as soon as we try to establish a connection with the following line of code:
repositoryManager = RepositoryManagerFactory.connect();
I greatly appreciate any insight.
The source of this error is com.bea.content.RepositoryRuntimeException: Repository configuration error. at com.bea.content.manager.internal.RepositoryManagerImpl.getRepositoryOps()Lcom.bea.content.manager.RepositoryOps;(RepositoryManagerImpl.java:159) at com.bea.content.manager.internal.RepositoryManagerImpl.connect()[Lcom.bea.content.manager.RepositorySession;(RepositoryManagerImpl.java:107) at com.bea.content.manager.RepositoryManagerFactory.connect()Lcom.bea.content.manager.RepositoryManager;(RepositoryManagerFactory.java:36) at com.radian.portal.portalContent.PortalContent.Initialize()V(PortalContent.java:461) at com.radian.portal.portalContent.PortalContent.()V(PortalContent.java:55) at com.radian.portal.portalContent.GetSnippetTag.doStartTag()I(GetSnippetTag.java:25) at jsp_servlet._portlets._divisions.__showsnippet._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(showSnippet.jsp:10) at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(JspBase.java:33) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:971) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:402) at weblogic.servlet.internal.TailFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.documentum.eip.integration.bea.BeaRequestParameterFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(BeaRequestParameterFilter.java:37) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PortalServletFilter.java:313) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PageFlowJspFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at weblogic.servlet.internal.RequestDispatcherImpl.include(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Z)V(RequestDispatcherImpl.java:613) at weblogic.servlet.internal.RequestDispatcherImpl.include(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(RequestDispatcherImpl.java:400) at weblogic.servlet.jsp.PageContextImpl.include(Ljava.lang.String;)V(PageContextImpl.java:154) at jsp_servlet._portlets._divisions.__snippetexample._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(snippetExample.jsp:19) at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(JspBase.java:33) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:971) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:402) at weblogic.servlet.internal.TailFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.documentum.eip.integration.bea.BeaRequestParameterFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(BeaRequestParameterFilter.java:37) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PortalServletFilter.java:313) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PageFlowJspFilter.java:101) Caused by: javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: remaining name: /app/ejb/content.jar#RepositoryOpsEJB/local-home]; Link Remaining Name: 'java:app/ejb/content.jar#RepositoryOpsEJB/local-home' at weblogic.jndi.internal.WLNamingManager.getObjectInstance(Ljava.lang.Object;Ljavax.naming.Name;Ljavax.naming.Context;Ljava.util.Hashtable;)Ljava.lang.Object;(WLNamingManager.java:98) at weblogic.jndi.internal.ServerNamingNode.resolveObject(Ljava.lang.String;Ljava.lang.Object;ILjava.util.Hashtable;)Ljava.lang.Object;(ServerNamingNode.java:265) at weblogic.jndi.internal.BasicNamingNode.resolveObject(Ljava.lang.String;Ljava.lang.Object;Ljava.util.Hashtable;)Ljava.lang.Object;(BasicNamingNode.java:732) at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava.lang.String;Ljava.util.Hashtable;)Ljava.lang.Object;(BasicNamingNode.java:191) at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava.lang.String;Ljava.util.Hashtable;)Ljava.lang.Object;(BasicNamingNode.java:196) at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava.lang.String;Ljava.util.Hashtable;)Ljava.lang.Object;(BasicNamingNode.java:196) at weblogic.jndi.internal.WLEventContextImpl.lookup(Ljavax.naming.Name;Ljava.lang.String;)Ljava.lang.Object;(WLEventContextImpl.java:237) at weblogic.jndi.internal.WLContextImpl.lookup(Ljava.lang.String;)Ljava.lang.Object;(WLContextImpl.java:336) at javax.naming.InitialContext.lookup(Ljava.lang.String;)Ljava.lang.Object;(InitialContext.java:347) at com.bea.p13n.util.JndiHelper.lookupNarrow(Ljava.lang.String;Ljava.lang.Class;)Ljava.lang.Object;(JndiHelper.java:83) at com.bea.content.manager.internal.RepositoryManagerImpl.getRepositoryOps()Lcom.bea.content.manager.RepositoryOps;(RepositoryManagerImpl.java:152) at com.bea.content.manager.internal.RepositoryManagerImpl.connect()[Lcom.bea.content.manager.RepositorySession;(RepositoryManagerImpl.java:107) at com.bea.content.manager.RepositoryManagerFactory.connect()Lcom.bea.content.manager.RepositoryManager;(RepositoryManagerFactory.java:36) at com.radian.portal.portalContent.PortalContent.Initialize()V(PortalContent.java:461) at com.radian.portal.portalContent.PortalContent.()V(PortalContent.java:55) at com.radian.portal.portalContent.GetSnippetTag.doStartTag()I(GetSnippetTag.java:25) at jsp_servlet._portlets._divisions.__showsnippet._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(showSnippet.jsp:10) at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(JspBase.java:33) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:971) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:402) at weblogic.servlet.internal.TailFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.documentum.eip.integration.bea.BeaRequestParameterFilter.doFilter(Ljavax.servlet.Servlet Request;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(BeaRequestParameterFilter.java:37) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PortalServletFilter.java:313) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PageFlowJspFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at weblogic.servlet.internal.RequestDispatcherImpl.include(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Z)V(RequestDispatcherImpl.java:613) at weblogic.servlet.internal.RequestDispatcherImpl.include(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(RequestDispatcherImpl.java:400) at weblogic.servlet.jsp.PageContextImpl.include(Ljava.lang.String;)V(PageContextImpl.java:154) at jsp_servlet._portlets._divisions.__snippetexample._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(snippetExample.jsp:19)

If it is urgent ... http://metalink.oracle.com

BI Metadata Repository Configuration Error

Hello gurus.
Maybe somebody can tell how to solve this problem.
When try to create BI Metadata Repository (see note 1049784) an error received:
Configuration Error: Missing attribute: cacheid_lock, configuration node = component-config, location = config://local/cm/repository_managers/bw_metadata
The same error received on BI Document Repository activation.
So, where could find this cacheid_lock attribute?
EP7 SP15
Thanks.

SPS 16 solved this problem.
Edited by: Gunars Blumbahs on Jul 26, 2008 2:22 PM

Managed system configuration error

Dear Expert,
While doing managed system configuration step-"Check Configuration" for my solman (7.1)system itself, I am getting attached error.
Please Advice .
Thanks
Chander

Dear Oliver ,
I have downloaded the Patch 183 (SAPHOSTAGENT183_183-20005735.SAR).
Refering below link for upgrade http://help.sap.com/saphelp_nw73ehp1/helpdata/en/39/a1f623bae74a2784f88282c8652070/content.htm
But after uncaring of Patch 183 ,I am not getting below files in new patch level .
sapstartsrv.exe
saposcol.exe
saphostctrl.exe
saphostexec.exe
According to link the last file will be used in upgrade
saphostexec.exe -upgrade
but this is not present in new patch level 183.
Thanks
Chander

MAnaged system configuration error in solution manager

Hi,
While doing managed system configuration getting the error, below versions are using.
MDM 7.1 SP10 Import server and Solution manager 7.1 SP10.
Can anyone help me?.
Regards
Chandra

Two cases you have
1) Satellite system
Re-install The DIA agent and give correct (port numbers )SLD details
Once you re-install the DIA agent, run Rz70 from satellite system
data will pull from satellite system to central SLD.
2)Run SLD check from Solman system , check its successful or not
Go to LMDB and check satellite system
After re-Synchronize technical system from SLD
Thanks ,
Rahul yedapally

Managed System Configuration Error for MDM 7.1 SP09

Greetings, Needed your expert advise. We are getting an error while configuring our MDM Servers (Version 7.1.08.196) in Solution Manager. As suggested in SAP Note 1798643 , I have manually filled the required details and transferred through sldreg.exe to SLD. Now when i try to perform Managed System Configuration, it is throwing the below error. The definition of Technical System '~MDM' is not correct: '~MDM': No Path found in Installed Technical System 'SID~MDM~'. I'm not sure how to manually update the Install Path for our MDM Servers. Since, the data to LMDB is automatically supplied, I might not be able to manually edit anything. Could you please advise if there is any step to solve this issue. Thanks, Haseeb Ahmed.

Dear ,
Haseeb,
I had the exact same problem with MDM managed system setup . I was on MDM 7.1 SP10.
1940337 - RCA template for Solution Manager 7.10 SP10
This note should resolve your problem. This note has the updated template for MDM.
It did for mine
Thanks
Amit

Metadata Management Setup connection error

I'm trying to install BO Metadata Management (3.0) over a BO XI R3.1, to try it's features and testing.
After the setup launch of "Metadata Management" I fill my credentials to log on to BO CMS, but the setup fails with "Test connection failed" error, without giving any further error details. The BO is functioning, I can logon with the same credentials to CMC, InfoView and so on.
As a result the setup program aborts.
Can anyone give some help on installing Metadata Management with BO XI R3.1, or had the same error?
Thanks in advance.

It seems that I am facing the same problem when I am trying to install BOMM XI 3.1 (12.1) on top of BOE XI 3.1 SP3.? I am sure that the connection information is correct. Who can help out here?
MKA

BOMM - metadata manager repository sql to fetch where object is used in rep

Hi,
We've been using BOMM for a few months and would now like to make our own reporting on the BOMM repository. Most information we're capable of retrieving, but not wether a certain universe object is used in the select-clause or where-clause of a reportquery. The information must be stored somewhere, because the mm explorer is can give us that information.
Can someone tell me where this information is stored and how we can get it out?
I thought it was stored in the table MMD_Query, with query_type_cd = sqls or sqlw. But the table only contains the full sql (sqlf), universe contexts (unvc) and join statements (sqlj).
Thanks in advance for the help. Regards
Guy
Ps: My excuses for the crossposting, but I was advised to put this question in this forum.

You might have better luck in the (somewhat misnamed) [Data Integration and Data Quality Management|Data Services and Data Quality; forum:
This forum is dedicated to topics related to SAP BusinessObjects Data Services (Data Integrator, Data Quality Management, Text Data Processing), SAP BusinessObjects Information Steward (Metadata Management, Data Insight), SAP BusinessObjects Rapid Marts and SAP BusinessObjects Data Federator.
(emphasis added)
Regards,
Sean

Sap solution manager optimizer configuration error

Dear Receipient
I have installed solution manager 4.0, patch is updated upto the level of optimizer configuration. I have configured sap router on the same solution manager machine.
now i am in solution manager optimizer configuration in that i am doing it with an user of having sap_all rights
in t code sm59 -> sap-oss connection test is good
now through t code solution_manager i have created an new active solution of sandbox land scape and through t code smsy i have created an logical component of sap ecc and i have added the user basis which iam using for soman optimizer configuration thru t code aisuser
but now if i go to t code solution_manager if i click on sandbox landscape -> change management -> support packs -> then click on maintenance optimizer it shows as no system
and also in product version also no available its showing
i dont know where i went wrong in my solman optimizer configuration
pls help me
regards
senthil

Hi,
Please follow the SAP Tutor to setup maintenance optimizer:
http://service.sap.com/solman-mopz
-> "SAP Tutor on Maintenance Optimizer " under the section
"Additional information on Maintenance Optimizer"
Best regards,
Warren

OWB Repository Configuration Error

Hi All,
I am getting the following error when i try to configure the OWB repository.
java.sql.SQLEXCEPTION - ORA - 22905 cannot access rows from a non-nested table item. ORA - 06512: at line 17.
Please help me out in this regard as it is urgent.
I got the error when the configuration was 94 % complete. :(
Thanks and Regards,
Soma

If it is urgent ... http://metalink.oracle.com

Errors in the metadata manager

Hi Experts,
Periodically we're seeing Error Event ID's 18 and 19 on our SSAS server (SQL Server 2008 R2) hosting SCSM Data Warehouse DB's.
The cube's appear to be processing OK from what I can tell, but everything I can find online relating to these errors indicates some corruption in the Data directory. We get these errors in two different, separate SCSM environments (SCSM 2012 SP1 UR4).
Has anyone ever experienced these Errors before?
Below are the details for these Errors.
Log Name:      Application
Source:        MSSQLServerOLAPService
Date:          1/9/2014 3:07:12 AM
Event ID:      19
Task Category: (289)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SCSMP06SQL.wcbbc.wcbmain.com
Description:
Errors in the metadata manager. An error occurred when loading the ReviewActivityCreatedByUser partition, from the file, '\\?\H:\OLAP\Data\DWASDataBase2.0.db\SystemCenterChangeAndActivityManagementCube.0.cub\ReviewActivityCreatedByUser.0.det\ReviewActivityCreatedByUser.223.prt.xml'.
Log Name:      Application
Source:        MSSQLServerOLAPService
Date:          1/9/2014 3:33:08 AM
Event ID:      18
Task Category: (289)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SCSMP06SQL.wcbbc.wcbmain.com
Description:
Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\H:\OLAP\Data\DWASDataBase2.0.db\SystemCenterWorkItemsCube.0.cub\BillableTimeBilledByUser.1830.det.xml'.

Hi David,
Did you end up resolving this? I've just come across the same error this morning (different cube reference though) and am beginning to look at the issue.
Cheers,
Lain

Syntax error in program CL_AC_METRIC_REPOSITORY=======CP When going to managed system configuration in solman 7.1

Dear SAP Gurus,
Good Morning.
I'm getting error in managed system configuration in solman 7.1. Error is like
The system preparation and Basic configuration in working fine, but when we are going to click the managed system configuration Error getting like this.
Solution Manager Version : 7.1
SP Level : SP5
Thanks in Advance.
Regrads,
Kumar BN

Hello Kumar,
I would suggest moving this discussion to this space in SCN: http://scn.sap.com/community/it-management/alm/solution-manager
That will help get you a quicker response.
Thank you,
Kristen

Metadata Management Custom Reports

Does anyone know where there is documentation on configuration or usage of the Metadata reports available in Information Steward?
I am prompted for login credentials to the repository but nothing that I try works. To make things worse, it seems to cause Tomcat to shut down.
In the versions of Metadata Management used with Business Objects XI3.1, you had to go to the reports to configure the JDBC connections for the reports. I can't find any documentation on where the reports are stored much less on how to configure the connection to the Metadata Management repository database.
I am running Information Steward 4.2sp2 hosted on Information Platform Services 4.1sp3.

hi Phani,
use catalog manger to get report in CSV or Excel report Open Catalog -->Tools--->Create Report
Select a type to report for a request /dashboard
Refer 10th Step :http://www.rittmanmead.com/2010/01/18/obiee-10g-web-catalog-best-practices/
thanks,
Saichand.v
Edited by: Saichand Varanasi on Oct 8, 2010 4:25 PM

Repository Connection Error

Hi All,
Recently we upgraded OS from Windows 32 Bit to Linux 64 Bit and we installed OWB 11g R2 and we exporeted metadata of OWB 11g R1 and imported to OWB 11g R2. Every thing is working fine.
But weekly twice we are facing issue as follows: When we are trying to redeploy the few objects at Control Centre Manager:
REPOSITORY CONNECTION ERROR:+
The connection to the Repository was Lost, becasue of the following Database Error : Closed Connection+
Exit OWB without coming+
Let us know how can we avoid the above error?
Regards,
Ava

Good afternoon,
What is the exact version of the database that you're trying OWB on?
If it's a 10gR2 database, at present there is no production OWB version that is certified to work on that.
Cheers, Patrick

Metadata Manager Repository Configuration Error

Similar Messages

Maybe you are looking for