MySQL Start fail

Hi everyone,
I installed MySQL and set up the root password etc, but when I want to start it I get
sudo /etc/rc.d/mysqld start
:: Starting MySQL Server [FAIL]
I found no log file (at least not in /var/logs). The wiki describes such an issue but that solution does not work for me.
Any other suggestion?
Last edited by AlexCogn (2012-10-16 18:31:27)

ackt1c wrote:Your resolving procedure? Have you read about systemd?
As resolving procedure, I did
sudo chown mysql:mysql /var/lib/mysql -R
and I verified that all the folders where owned by 'mysql'.
I use systemd I suppose because I use daemons?
EDIT: after a reboot everything seems to work ...
Last edited by AlexCogn (2012-10-14 10:49:44)

Similar Messages

  • Upgrade phase STARTSAP_NBAS error: SYSTEM START failed

    During an upgrade from BW 3.5 to BI 7.0, I get the following error
    message in phase STARTSAP_NBAS:
    SYSTEM START failed, code -2
    -2: the test rfc did not work.
    Try to log on to the system with user DDIC
    When I try to log on to the system as user DDIC, I get the following
    error message:
    DB-Error -0
    The same thing happens when I try to log on as SAP*. I am certain that
    the password I submit is correct. I have not changed this password at
    any time.
    I have included SAP_BASIS support package 14 into this upgrade, and
    this requires kernel version 133 at least (Note 822379). This kernel
    was copied into the usr\sap\put\exenew directory before the upgrade
    began. However, the system still seems to run on kernel version 111.
    I have tried to put the 133 kernel into
    F:\usr\sap\BWS\SYS\exe\nuc\NTAMD64 so that it is copied into
    F:\usr\sap\BWS\SYS\exe\run during system startup, but then all my work
    processes die. The gateway also seems to be down using this kernel.
    Please help!
    Regards,
    Thomas

    Hi.
    I made a stupid mistake.. the kernel I was using was unicode, but I should use a non-unicode kernel..
    Regards,
    Thomas

  • Java 7 Web start fails to download Java 1.6 version

    Sorry for the almost exact duplication of a previous thread, but that was closed (Java 7 Web start fails to download Java 1.6 version
    When launching an application requiring Java 1.6 with a Java 1.7 web start it fails when it tries to download 1.6 with the following message:
    "Unable to download http://javadl-esd.sun.com/update/1.6.0/1.6.0_29-b11.xml for installation"
    Problem only seems to occur on Windows 7 (64 bit), seems fine on Windows XP.
    Bug has been raised with Oracle by poster Matt Taylor - http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7168311
    Does anybody have any ideas?
    Thanks,
    Lee.

    igor wrote:
    Could you please collect and provide more info.
    In particular:
    0) Explain how exactly you launch JNLP when it does not work.We have a website with a link to a jnlp file. User clicks on the link the jnlp file downloads and installs.
    "install the jnlp from the dos window" - do you mean run "javaws applicationURL"?Yes. But actually that only worked because we had already installed a Java 6 version.
    When it does not work do you use Deployment Toolkit to embed link into web page?
    1) screenshot of the errorHere are links to several screenshots of errors we get:
    http://dl.waterford.org/pics/error_install.png
    http://dl.waterford.org/pics/error2.png
    http://dl.waterford.org/pics/error3.png
    Here is a link to the error in the java webstart failure dialog (details):
    http://dl.waterford.org/pics/errormsg.txt
    2) Enable full trace details (see http://docs.oracle.com/javase/7/docs/webnotes/tsg/TSG-Desktop/html/plugin.html#gcexdf)
    and post trace fileHere is a link to the java console with full trace details:
    http://dl.waterford.org/pics/javaconsole.txt
    3) Install WireShark and see what http requests are made. Please post all request/response pairshttp://dl.waterford.org/pics/packets.pcap
    Edited by: 933472 on May 10, 2012 1:30 PM

  • Please help: opmn start failed

    Hello,
    I have the following problem with the opmn:
    I have installed Oracle 10g Database in HPUX 11.11 from the disc "Database". It works OK, I can start my database instance "orademo" with dbstart and stop it with dbshut. If it is running, I can connect to it without problems.
    Then I have installed Oracle 10g Database Products from the disc "Companion" without problems.
    Then I tried to install Oracle 10g Database Companion Products. The installation seemed to proceed OK except of the following two messages: "File not found ...(emca.1.1.jar)" at approx. 76% of the status bar and "Error invoking target 'nmo nmb'..." at approx. 95%. I have clicked on "Continue" in both cases and the installation went up to the screen, "Configuration Assistants". The first of the two actions, OC4J Configuration Assistant, succeeded. The other one, "Starting HTTP Server", failed. Then I have canceled it, performed the root.sh script, and the last screen, "End of Installation" appeared. When I closed this, I could see the following message in the terminal:
    Exception : class java.sql.SQLException Io exception: The Network Adapter could not establish the connection
    Could not retrive nls_lang from database
    Then I tried to start HTTP server manually but I obtained the following error messages:
    bash-2.05b$ /export/ora10gcomp/opmn/bin/opmnctl startall
    opmnctl: starting opmn and all managed processes...
    Pthread internal error: message: __libc_reinit() failed, file: /ux/core/libs/threadslibs/src/common/pthreads/pthread.c, line: 1155
    Return Pointer is 0xc003a497
    /export/ora10gcomp/opmn/bin/opmnctl[3]: 21149 Quit(coredump)
    Pthread internal error: message: __libc_reinit() failed, file: /ux/core/libs/threadslibs/src/common/pthreads/pthread.c, line: 1155
    Return Pointer is 0xc003a497
    /export/ora10gcomp/opmn/bin/opmnctl[7]: 21150 Quit(coredump)
    Pthread internal error: message: __libc_reinit() failed, file: /ux/core/libs/threadslibs/src/common/pthreads/pthread.c, line: 1155
    Return Pointer is 0xc003a497
    /export/ora10gcomp/opmn/bin/opmnctl[9]: 21152 Quit(coredump)
    opmnctl: opmn start failed
    bash-2.05b$
    Then I checked all Oracle 10g requirements, namely required HPUX patches, unistalled and reinstalled the Oracle 10g Database Companion Products repeatedly, checked the connection to the database by SQL Plus etc. ... but the problem was always the same.
    Note: I installed Oracle 10g (including Database Companion Products) also in Windows XP and in Fedora Core 3 and I never encountered a problem like this. Everything runs correctly in these other operating systems.
    Would somebody help me?
    Thanks in advance!
    Vaclav

    Hi,
    Thanks for the replay. I am doing the installation once again. Now I am not facing OPMN problem.
    Now I am facing some another problem. That DBCA fails to create infrastructre metadata respository database. Why it is happening?
    regards,
    Mat.

  • UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012

    This is kind of long, but here goes...
    We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images.  We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
    thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002  during what appears to be the "Use Toolkit Package" step.  This is after the OS image has already been laid down and after the ConfigMgr
    client has been installed/configured.  The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence.  Error code 0x8007002"  Among other errors...I will post the entire log below...
    After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
    but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure. 
    Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment.  We have a few OSD task sequences built without UDI and those all still work just fine. 
    So, I am at a loss for where the root problem lies.  Any suggestions or assistance would be greatly appreciated.
    Here is the entire SMSTS.log and BDD.log...
    https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
    Thanks
    Richie Tenhet

    your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
    Use Toolkit Package step...
    "Starting Task Sequence Engine . . . "
    "Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
    "Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
    "unknown host (gethostbyname failed)"
    "sending with winhttp failed; 80072ee7"
    "Tried all the available http based locations. SMB based locations will be attempted now."
    "Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
    "Failed to run the action: Use Toolkit Package.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)"
    that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
    around the time of the failure.
    Step by Step Configuration Manager Guides >
    2012 Guides |
    2007 Guides | I'm on Twitter > ncbrady

  • Start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager ...

    Hello Group,
    We are using Weblogic Version 9.2.3 & facing some problem related to 'jackrabbit' not available. I feel we are facing problem similar to the one mentioned in following link
    Re: What causes XAER_RMFAIL : Resource manager is unavailable / unregistered
    Following above post, we tried increased the Initial Capacity of this 'jackrabbit' Resource Adapter to 50. Initially it was 1. Although this doesn't change anything. Although it works fine for a few hours but seems like after server has run for a few hours and served some requests it starts showing this exception.
    Following is our weblogic-ra.xml file.
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <native-libdir></native-libdir>
    <jndi-name>repository</jndi-name>
    <enable-access-outside-app>true</enable-access-outside-app>
    <enable-global-access-to-classes>true</enable-global-access-to-classes>
    <security></security>
    <outbound-resource-adapter>
    <default-connection-properties>
    <pool-params></pool-params>
    <logging></logging>
    </default-connection-properties>
    <connection-definition-group>
    <connection-factory-interface>javax.jcr.Repository</connection-factory-interface>
    <default-connection-properties>
    <pool-params>
         <initial-capacity>50</initial-capacity>
         <max-capacity>100</max-capacity>
    </pool-params>
    <logging></logging>
    <properties>
    <property>
    <name>HomeDir</name>
    <value>jackrabbit-preferences</value>
    </property>
    <property>
    <name>ConfigFile</name>
    <value>jackrabbit-preferences/repository.xml</value>
    </property>
    </properties>
    </default-connection-properties>
    <connection-instance>
    <jndi-name>jackrabbit</jndi-name>
    <connection-properties>
    <pool-params>
         <initial-capacity>50</initial-capacity>
         <max-capacity>250</max-capacity>
    </pool-params>
    <logging></logging>
    <properties>
    <property>
    <name>HomeDir</name>
    <value>jackrabbit-preferences</value>
    </property>
    </properties>
    </connection-properties>
    </connection-instance>
    </connection-definition-group>
    </outbound-resource-adapter>
    </weblogic-connector>
    Also please find below the exception that we see in the logs.
    Caused by: ag.mycompany1.workflow.runtime.DocumentManagementServiceException: null: javax.jcr.RepositoryException: start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager is unavailable
    javax.transaction.xa.XAException: Internal error: XAResource 'jackrabbit' is unavailable
         at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:1143)
         at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:685)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1181)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
         at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
         at weblogic.connector.outbound.ConnectionHandlerBaseImpl.prepareHandle(ConnectionHandlerBaseImpl.java:670)
         at weblogic.connector.outbound.ConnectionHandlerBaseImpl.createConnectionHandle(ConnectionHandlerBaseImpl.java:361)
         at weblogic.connector.outbound.ConnectionInfo.createConnectionHandle(ConnectionInfo.java:411)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:308)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:98)
         at org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:89)
         at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactory.createSession(JcrSessionFactory.java:38)
         at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactoryUtils.getSession(JcrSessionFactoryUtils.java:72)
         at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactory.getSession(JcrSessionFactory.java:33)
         at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.doWithJcrVfs(AbstractJcrDocumentRepositoryService.java:537)
         at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.doWithJcrVfs(AbstractJcrDocumentRepositoryService.java:564)
         at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.retrieveFileContent(AbstractJcrDocumentRepositoryService.java:186)
         at com.mycompany2.infinity.bpm.vfs.impl.AbstractDocumentRepositoryServiceImpl.retrieveFileContent(AbstractDocumentRepositoryServiceImpl.java:46)
         at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl$5.withVfs(DocumentManagementServiceImpl.java:112)
         at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl.adaptVfsCall(DocumentManagementServiceImpl.java:417)
         at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl.retrieveDocumentContent(DocumentManagementServiceImpl.java:108)
         at sun.reflect.GeneratedMethodAccessor826.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at ag.mycompany1.workflow.runtime.beans.interceptors.CallingInterceptor.invoke(CallingInterceptor.java:18)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.POJOExceptionHandler.invoke(POJOExceptionHandler.java:23)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.GuardingInterceptor.invoke(GuardingInterceptor.java:87)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.AbstractLoginInterceptor.performCall(AbstractLoginInterceptor.java:142)
         at ag.mycompany1.workflow.runtime.beans.interceptors.AbstractLoginInterceptor.invoke(AbstractLoginInterceptor.java:80)
         at ag.mycompany1.workflow.runtime.spring.SpringBeanLoginInterceptor.invoke(SpringBeanLoginInterceptor.java:58)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.spring.SpringSessionInterceptor$1.doInConnection(SpringSessionInterceptor.java:104)
         at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:342)
         at ag.mycompany1.workflow.runtime.spring.SpringSessionInterceptor.invoke(SpringSessionInterceptor.java:52)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.spring.SpringConfigurationInterceptor.invoke(SpringConfigurationInterceptor.java:94)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.PropertyLayerProviderInterceptor.invoke(PropertyLayerProviderInterceptor.java:85)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.DebugInterceptor.invoke(DebugInterceptor.java:25)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.spring.SpringTxInterceptor$1.doInTransaction(SpringTxInterceptor.java:62)
         at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
         at ag.mycompany1.workflow.runtime.spring.SpringTxInterceptor.invoke(SpringTxInterceptor.java:47)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.execute(MethodInvocationImpl.java:55)
         at ag.mycompany1.workflow.runtime.beans.InvocationManager.invoke(InvocationManager.java:46)
         at $Proxy175.retrieveDocumentContent(Unknown Source)
         at ag.mycompany1.workflow.runtime.spring.DocumentManagementServiceBean.retrieveDocumentContent(DocumentManagementServiceBean.java:70)
         at sun.reflect.GeneratedMethodAccessor826.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at ag.mycompany1.workflow.runtime.spring.SpringServiceFactory$SpringServiceInvocationHandler.invoke(SpringServiceFactory.java:159)
         at $Proxy175.retrieveDocumentContent(Unknown Source)
         at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.loadPreferences(AbstractDocumentServicePreferencesManager.java:318)
         at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.getPreferences(AbstractDocumentServicePreferencesManager.java:269)
         at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.getPreferencesEditor(AbstractDocumentServicePreferencesManager.java:133)
         at com.mycompany2.infinity.bpm.bcc.configuration.TrafficLightViewPropertyProvider.<init>(TrafficLightViewPropertyProvider.java:85)
         at com.mycompany2.infinity.bpm.bcc.configuration.TrafficLightViewPropertyProvider.getInstance(TrafficLightViewPropertyProvider.java:103)
         at com.mycompany2.sims.workflow.tlv.TrafficLightDataLoader.persistData(TrafficLightDataLoader.java:129)
         at com.mycompany2.sims.workflow.tlv.TrafficLightDataLoader.loadData(TrafficLightDataLoader.java:73)
         at com.mycompany2.sims.workflow.SyncSettingsBean.reload(SyncSettingsBean.java:73)
         at com.mycompany2.sims.workflow.EnterpriseSettings.isWorklistConfigured(EnterpriseSettings.java:143)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.myfaces.el.PropertyResolverImpl.getProperty(PropertyResolverImpl.java:457)
         at org.apache.myfaces.el.PropertyResolverImpl.getValue(PropertyResolverImpl.java:85)
         at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:141)
         at com.sun.el.parser.AstValue.getValue(AstValue.java:96)
         at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:183)
         at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
         at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:233)
         at com.sun.facelets.tag.TagAttribute.getBoolean(TagAttribute.java:79)
         at com.sun.facelets.tag.jstl.core.ChooseWhenHandler.isTestTrue(ChooseWhenHandler.java:49)
         at com.sun.facelets.tag.jstl.core.ChooseHandler.apply(ChooseHandler.java:67)
         at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
         at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
         at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
         at com.sun.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:109)
         at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
         at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
         at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
         at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524)
         at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
         at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
         at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
         at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at ag.mycompany1.web.jsf.common.ExceptionFilter.doFilter(ExceptionFilter.java:45)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:290)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:250)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:207)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:161)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at ag.mycompany1.web.jsf.common.LoginFilter.doFilter(LoginFilter.java:250)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3251)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    : start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager is unavailable
    Any help in this regard is highly appreciated. Thanks.

    Hi,
    Can you please try increase the below MaxXACallMillis setting in Weblogic set 'Maximum Duration of XA Calls' to a bigger value
    MaxXACallMillis: Sets the maximum allowed duration (in milliseconds) of XA calls to XA resources. This setting applies to the entire domain.
    http://docs.oracle.com/cd/E12840_01/wls/docs103/jta/trxcon.html
    The parameter is exposed through administration console: services --> jta --> advanced --> "Maximum Duration of XA Calls:"
    Check the below docs for more information
    WLS 10.3: Intermittent XA error: XAResource.XAER_RMERR (Doc ID 1118264.1)
    Hope it Helps

  • BPMA_ProcessManager service start failed

    EPM Version: 11.1.1.1
    OS: Windows 2003
    Dear all,
    BPMA_ProcessManager service start failed, but the EPM System Diagnostic report is success.
    Which way I can find the error where it is?
    How can I resolve the problem?
    Or load service order is wrong?
    Thx
    Hector

    Windows Event viewer detail:
    Event Type:     Error
    Event Source:     HyS9BPMA_ProcessManager
    Event Category:     None
    Event ID:     0
    Date:          2009-1-16
    Time:          15:53:53
    User:          N/A
    Computer:     ITFARMER-K9EW27
    Description:
    [892] ERROR Can't find the method:com/hyperion/hss/clients/AuthenticationException: Hyperion.NetJNIBridge.Interface.Exceptions.CASSecurityException
    Message: Can't find the method:com/hyperion/hss/clients/Authentication
    Source: NetJNIBridge
    Server stack trace:
    at Hyperion.NetJNIBridge.CASSecurity.GetDataBaseDetails(String& dbType, String& serverName, ValueType& dbPort, String& dbName, String& userName, String& password, String& jdbcUrl)
    at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at Hyperion.NetJNIBridge.Interface.ICASSecurity.GetDataBaseDetails(String& dbType, String& serverName, ValueType& dbPort, String& dbName, String& userName, String& password, String& jdbcUrl)
    at Hyperion.DimensionServer.SessionManager.CasSecurityProvider.GetDataBaseDetails(String& vendor, String& serverName, Int32& dbPort, String& dbName, String& username, String& password, String& jdbcUrl)

  • Mac book pro (2008)will not start up,command-v gives (error) Import:Importer start failed for 89(kr:268435459)invalid destination port)

    will not start up.
    tried Command-v
    message reads
    (error) Import:Importer start failed for 89 (kr:268435459)invalid destination port)

    First, uninstall "SuperTV" (whatever that is) according to the developer's instructions. It isn't working and it's filling the log with noise.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application.
    Step 1
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
    Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged before the boot, while the system was unresponsive or was failing to shut down. Please include the BOOT_TIME message at the end of the log extract.
    Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
    PLEASE DO NOT INDISCRIMINATELY DUMP THOUSANDS OF LINES FROM THE LOG INTO A MESSAGE. If you do that, I will not respond.
    Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
    Step 2
    Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

  • XAResource.XAER_RMFAIL start() failed on resource

    We are getting following error in production system. What may be the cause of this issue?
    com.ekaplus.common.exception.SystemException: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'MyPool_EKA8X_QA': XAER_RMERR : A resource manager error has occured in the transaction branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:729)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1231)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1164)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:285)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:522)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:449)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1599)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1503)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:446)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:403)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364)
         at com.ekaplus.common.db.ContainerConnectionProvider.getConnection(ContainerConnectionProvider.java:79)
         at com.ekaplus.dao.common.ConnectionManager.getDSConnection(ConnectionManager.java:24)
         at com.ekaplus.dao.common.ConnectionManager.getConnection(ConnectionManager.java:14)
         at com.ekaplus.dao.common.JdbcDAO.getConnection(JdbcDAO.java:372)
         at com.ekaplus.asyncAlertReminder.dao.AlertReminderBaseDAO.getConnection(AlertReminderBaseDAO.java:26)
         at com.ekaplus.asyncAlertReminder.dao.AlertEventMasterDAO.findBySearchCriteria(AlertEventMasterDAO.java:265)
         at com.ekaplus.asyncAlertReminder.service.engine.alertprocessor.OperationalAlertProcessorService.initialize(OperationalAlertProcessorService.java:151)
         at com.ekaplus.asyncAlertReminder.service.engine.alertprocessor.AlertListener.onMessage(AlertListener.java:118)
    We have tried following but no resolution could be found with these changes.
    increase MaxXACallMillis value to 600000 on JTA Advanced settings.
    Increase max pool size from 100 to 150.
    Please enable set XA transaction timeout configuration for MyPool data source and let timeout value remain 0.
    Most of the stack traces logged when this exception is raised, point to JMS queue listener making DB calls using XA pool connection. However, JMS transaction factory is non-XA.
    R,
    Vineet

    Hi mates,
    Did you finally manage to solve this issue? We are facing a very similar one, but with a transaction related to SqlJmsProvider. The transactions related to the message polling are very light and shouldn't be expiring.
    Do you have any suggestion about this?
    We have our app (ATG10.0.1deployed in WebLogic10.3.
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider --- java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'ATGProductionDS_SDG': XAER_RMFAIL : Resource manager is unavailable
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider oracle.jdbc.xa.OracleXAException
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.start(DataSource.java:729)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1231)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1164)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:285)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:522)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:449)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1599)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1503)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:446)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.connect(DataSource.java:403)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.flagWithStatement(SqlTopicManager.java:986)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.flagNewEntries(SqlTopicManager.java:872)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.pollForNewEntries(SqlTopicManager.java:816)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlJmsManager.poll(SqlJmsManager.java:1598)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlJmsManager.performScheduledTask(SqlJmsManager.java:908)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.service.scheduler.ScheduledJob.runJobs(ScheduledJob.java:441)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.service.scheduler.Scheduler$2handler.run(Scheduler.java:760)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1604)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1503)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:446)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.connect(DataSource.java:403)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.flagWithStatement(SqlTopicManager.java:986)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.flagNewEntries(SqlTopicManager.java:872)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.pollForNewEntries(SqlTopicManager.java:816)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlJmsManager.poll(SqlJmsManager.java:1598)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlJmsManager.performScheduledTask(SqlJmsManager.java:908)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.service.scheduler.ScheduledJob.runJobs(ScheduledJob.java:441)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.service.scheduler.Scheduler$2handler.run(Scheduler.java:760)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1522)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:446)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.jta.DataSource.connect(DataSource.java:403)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.flagWithStatement(SqlTopicManager.java:986)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.flagNewEntries(SqlTopicManager.java:872)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlTopicManager.pollForNewEntries(SqlTopicManager.java:816)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlJmsManager.poll(SqlJmsManager.java:1598)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.dms.sql.SqlJmsManager.performScheduledTask(SqlJmsManager.java:908)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.service.scheduler.ScheduledJob.runJobs(ScheduledJob.java:441)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider at atg.service.scheduler.Scheduler$2handler.run(Scheduler.java:760)
    **** Error Tue Jun 04 07:29:57 BST 2013 1370327397440 /atg/dynamo/messaging/SqlJmsProvider
    Thank you very much.
    Edited by: 1009736 on 05-Jun-2013 03:11

  • PVC300 "Recording entry 0 start failed" error to NSS3000

    Hi,
    I have 4 cameras setup to record to a NSS3000. 2 x PVC300 and 2 x PVC2300
    I have setup the server on the PVC300's and it will test OK with a message "Mount Succeffully" however if I try to setup a recording to write to it I get the above error: "Recording entry 0 start failed"
    If I try with a motion event it fails with a "Samba Mount Failed" error.
    I can get the motion event writing OK to a FTP server on the same NSS3000 but not to CIFS.
    Both PVC2300's connect fine to the same NSS300 using the smae credentials and same share (different folder)
    All devices are on the same LAN connected via a 3560 switch
    the PVC300's have firmware 1.0.1.13
    the PVC2300's have firmware 1.1.2.6
    I have searched this community and cannot find anything similar, so thought it best to post this as a new thread.  Hope this is correct.

    Hi,
    I have 4 cameras setup to record to a NSS3000. 2 x PVC300 and 2 x PVC2300
    I have setup the server on the PVC300's and it will test OK with a message "Mount Succeffully" however if I try to setup a recording to write to it I get the above error: "Recording entry 0 start failed"
    If I try with a motion event it fails with a "Samba Mount Failed" error.
    I can get the motion event writing OK to a FTP server on the same NSS3000 but not to CIFS.
    Both PVC2300's connect fine to the same NSS300 using the smae credentials and same share (different folder)
    All devices are on the same LAN connected via a 3560 switch
    the PVC300's have firmware 1.0.1.13
    the PVC2300's have firmware 1.1.2.6
    I have searched this community and cannot find anything similar, so thought it best to post this as a new thread.  Hope this is correct.

  • Java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'myDomain': XAER_RMFAIL : Resource manager is unavailable

    Hi All,
    I am facing below issue without any change in the config from weblogic
    Managed servers are coming up and running without any issue
    But when we are doing any operation from application then its failing
    java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'myDomain': XAER_RMFAIL : Resource manager is unavailable
    Regards
    Lokesh

    Hi,
    Can you please try increase the below MaxXACallMillis setting in Weblogic set 'Maximum Duration of XA Calls' to a bigger value
    MaxXACallMillis: Sets the maximum allowed duration (in milliseconds) of XA calls to XA resources. This setting applies to the entire domain.
    http://docs.oracle.com/cd/E12840_01/wls/docs103/jta/trxcon.html
    The parameter is exposed through administration console: services --> jta --> advanced --> "Maximum Duration of XA Calls:"
    Check the below docs for more information
    WLS 10.3: Intermittent XA error: XAResource.XAER_RMERR (Doc ID 1118264.1)
    Hope it Helps

  • SMC 4.0 db-start failed

    Dear All ,
    I try install smc 4.0 on another sun box ,the reason for test CCR problem from on t2000 box ,I use same file which use for install smc on t2000 , but on step es-setup i got the problem (db-start failed).Here the log installation :
    Initiating setup for Sun Management Center Agent Component.
    This part of the setup process does the Sun Management Center Agent Component setup.
    Started /opt/SUNWsymon/lib/sbin/sm_setup_agent.sh at Thu Nov 8 20:16:52 BNT 2007.
    Running on SunOS sun240 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V240.
    Copying snmpd.conf file into /var/opt/SUNWsymon/cfg
    Server component also installed locally.
    Using this machine as the Sun Management Center server.
    ---------------------------- WARNING ---------------------------
    It appears that agent.snmpPort 161 is already in use.
    Sun Management Center 4.0 agent may not be able to run due to this conflict.
    There are two ways to correct this conflict:
    1. Reconfigure the port that Sun Management Center 4.0 uses.
    2. Stop the process that is using the port.
    Press RETURN to force default port.
    Enter port you would like to use [ 1100 to 65535 ]: 1161
    Updating /var/opt/SUNWsymon/cfg/domain-config.x with new port number.
    Generating agent security keys.
    PKCS11 Utilities package(SUNWcsl) was found.
    Encrypted SNMP Communication is supported.
    Setup of Agent component is successful.
    Starting Sun Management Center database setup...
    verifyDatabaseDown: instance is not executing
    Database consistency information missing.
    Configuring database initialization parameter file
    Stopping metadata component
    Successfully disabled service sunmc-metadata
    Stopping cfgserver component
    Successfully disabled service sunmc-cfgserver
    Stopping topology component
    Successfully disabled service sunmc-topology
    Stopping event component
    Successfully disabled service sunmc-event
    Stopping grouping service
    Successfully disabled service sunmc-grouping
    Stopping trap component
    Successfully disabled service sunmc-trap
    Stopping java server
    Successfully disabled service sunmc-javaserver
    Stopping webserver
    Successfully disabled service sunmc-webserver
    Stopping agent component
    Successfully disabled service sunmc-agent
    Stopping platform component
    Successfully disabled service sunmc-platform
    verifyDatabaseDown: instance is not executing
    Failed to enable service sunmc-database
    Database setup failed : db-start failed
    Updating registry...
    As database is not setup, Marking server setup as failed in Registry.
    None of the base layers are setup.
    No Addon is setup.
    Following Addons are not yet setup: Advanced System Monitoring,ELP Config-Reader Monitoring,Desktop,Service Availability Manager,Sun Fire Entry-Level Midrange System,Performance Reporting Manager,Solaris Container Manager,System Reliability Manager,Workgroup Server
    Could not finish requested task.
    I am already uninstall(use uninstall script ) and reinstall back , but the result is same , Does any one know how to solve this problem ?
    Regards
    hadi

    Greetings,
    I've not been able to resolve the topology issues, the recommended fixes have not resolved my issues. Upon un-installaing and re-installing multiple times I'm still not able to get the topology component to initialize correctly. The Management Center does display in the Applications listing in the Java Web Console (3.0.2) however clicking on it and displaying the main page for the Management Center 4.0 displays just a few items in the left nav, and none of the 'Discover Systems' requests make it in the queue or work at all. None of the other Management modules are displayed either. The web start console refuses to connect to the server as well, replying with a 'Server communication error, the server version may be incompatible' error.
    I've noticed quite a bit of sql errors in the install, I've not seen anything in the release notes or forums regarding this issue either. Any help on this would be greatly appreciated! SMA and snmpdx are both disabled as well as dmi services.
    The server is x86 Dell 2950, Entire install of Solaris 10 U3 11/06. Agent, Server, and Console components are installed and setup.
    */etc/project:*
    system:0::::
    user.root:1::::
    noproject:2::::
    default:3::::project.max-shm-memory=(priv,5368708912,deny)
    group.staff:10::::
    from */var/adm/messages:*
    Dec 19 12:19:21 dvall topology[963]: [ID 840589 daemon.alert] syslog Dec 19 12:19:21 topology parsing error in file://localhost/topology-license-d.x;flags=ro(13):
    Dec 19 12:19:21 dvall topology[963]: [ID 259113 daemon.alert] syslog Dec 19 12:19:21 topology *** aborting execution ***
    install log:
    Started ./es-inst at Wed Dec 19 11:50:19 PST 2007.
    Running on SunOS dvall 5.10 Generic_125101-07 i86pc i386 i86pc.
    This script installs Sun (TM) Sun Management Center 4.0
    Installation files source directory: /root/src/SunMC/disk1/image/SunOS/i386
    Copying required XML APIs from /root/src/SunMC/disk1/sbin/bin/i386-sun-solaris10 to /var/run/tmp/SunMCInstall/XML/APIs
    Enter the directory in which you want to install: [ /opt ] /opt/SunMC/
    Installation destination directory: /opt/SunMC
    Select the Sun Management Center 4.0 components to install:
    3 component(s) are available for your selection:
    Do you want to install the Server component (y|n|q) y
    Note: The Agent component will be installed automatically.
    Do you want to install the Console component (y|n|q) y
    Looking for valid JDK.
    Found incomplete installation of : "1.6.0_03-b05"
    SYMON_JAVAHOME is set to: /usr/java
    JDK version is: "1.6.0_03-b05"
    JDK check OK.
    Looking for Tomcat Webserver.
    Webserver check OK.
    You must agree to the above license agreement to proceed with installation.
    Do you agree (y|n|q) y
    Sun Management Center 4.0 can be installed in the following languages:
    Traditional Chinese
    Simplified Chinese
    French
    Japanese
    Korean
    English is installed by default.
    Are other languages required (y|n|q) n
    Reading Add-On products from image. Please wait...
    This can take approximately 3 minutes to complete.
    Found: Sun Management Center Integration for Unicenter TNG
    Found: Advanced System Monitoring
    Found: System Reliability Manager
    Found: Generic X86/X64 Config Reader
    Found: Solaris Container Manager
    Found: Service Availability Manager
    Found: Performance Reporting Manager
    Checking for applicable products. Please wait...
    This can take approximately 2 minutes to complete.
    Unable to find package directory for SUNWeshsm
    Component script found: check-remote-install.sh
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
    Return value: 1
    Component script found: check-remote-install.sh
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
    Return value: 1
    Component script found: check_TNG_Server.sh
    check if TNG Server is installed.
    Cannot install the Unicenter TNG addon Server component. CA-TNG is not installed, you should install CA-TNG first.
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check_TNG_Server.sh
    Return value: 2
    Script returned 2. Skipping this component.
    Component script found: gca-check.sh
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/X86ConfigReader/Solaris_10/Basic//gca-check.sh
    Return value: 1
    The Sun Management Center 4.0 Production environment will be installed.
    The following Add-On Products are applicable for installation.
    Advanced System Monitoring
    Service Availability Manager
    Performance Reporting Manager
    Solaris Container Manager
    System Reliability Manager
    Sun Management Center Integration for Unicenter TNG
    Generic X86/X64 Config Reader
    Do you want to select all the products (y|n|q) n
    Select the products you want to install:
    Advanced System Monitoring (y|n|q) y
    Service Availability Manager (y|n|q) y
    Performance Reporting Manager (y|n|q) y
    Solaris Container Manager (y|n|q) y
    System Reliability Manager (y|n|q) y
    Sun Management Center Integration for Unicenter TNG (y|n|q) n
    Generic X86/X64 Config Reader (y|n|q) y
    The following Add-On Products will be installed:
    Advanced System Monitoring
    Service Availability Manager
    Performance Reporting Manager
    Solaris Container Manager
    System Reliability Manager
    Generic X86/X64 Config Reader
    Do you want to proceed (y|n|q) y
    The following Add-On products are covered under license agreement:
    You must agree to the above license agreement to proceed with installation.
    Do you agree (y|n|q) y
    Disk Space Checking....
    Installing the components...
    Installing... PRODUCT.PE COMPONENT.AGENT
    Processing package instance <SUNWescom> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Common Components(i386) 4.0,REV=2.10.2007.10.23
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    Installing Sun Management Center Common Components as <SUNWescom>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    2426 blocks
    ## Executing postinstall script.
    Installation of <SUNWescom> was successful.
    Processing package instance <SUNWenesi> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center script localization messages(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    1 package pathname is already properly installed.
    Installing Sun Management Center script localization messages as <SUNWenesi>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    683 blocks
    Installation of <SUNWenesi> was successful.
    Processing package instance <SUNWesagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Agent(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Agent as <SUNWesagt>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    24750 blocks
    ## Executing postinstall script.
    Installation of <SUNWesagt> was successful.
    Processing package instance <SUNWesmib> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Mib Instance Module(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Mib Instance Module as <SUNWesmib>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    281 blocks
    Installation of <SUNWesmib> was successful.
    Processing package instance <SUNWesken> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Kernel Reader Module(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center Kernel Reader Module as <SUNWesken>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    399 blocks
    Installation of <SUNWesken> was successful.
    Processing package instance <SUNWesmod> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Agent Modules(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    9 package pathnames are already properly installed.
    Installing Sun Management Center Agent Modules as <SUNWesmod>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    235 blocks
    Installation of <SUNWesmod> was successful.
    Processing package instance <SUNWesae> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Agent System Files(i386) 4.0,REV=2.10.2007.10.15
    Using </> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    9 package pathnames are already properly installed.
    Installing Sun Management Center Agent System Files as <SUNWesae>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    28 blocks
    ## Executing postinstall script.
    Installation of <SUNWesae> was successful.
    Processing package instance <SUNWesaem> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Event Module for Agent(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    9 package pathnames are already properly installed.
    Installing Sun Management Center Event Module for Agent as <SUNWesaem>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    186 blocks
    Installation of <SUNWesaem> was successful.
    Processing package instance <SUNWesgui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center GUI Installation(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    7 package pathnames are already properly installed.
    Installing Sun Management Center GUI Installation as <SUNWesgui>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    6250 blocks
    Installation of <SUNWesgui> was successful.
    Processing package instance <SUNWsuagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Dynamic Agent Update Agent Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    6 package pathnames are already properly installed.
    Installing Sun Management Center Dynamic Agent Update Agent Components as <SUNWsuagt>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    152 blocks
    Installation of <SUNWsuagt> was successful.
    Processing package instance <SUNWesval> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Validation Tool Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Validation Tool Components as <SUNWesval>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    220 blocks
    Installation of <SUNWesval> was successful.
    Processing package instance <SUNWesaxp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Java API for XML Processing (JAXP) v1.1.3(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Java API for XML Processing (JAXP) v1.1.3 as <SUNWesaxp>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    2362 blocks
    Installation of <SUNWesaxp> was successful.
    Processing package instance <SUNWesmcp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Module Configuration Propagation(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    8 package pathnames are already properly installed.
    Installing Sun Management Center Module Configuration Propagation as <SUNWesmcp>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    249 blocks
    Installation of <SUNWesmcp> was successful.
    Processing package instance <SUNWeslac> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Local Access(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Local Access as <SUNWeslac>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    14 blocks
    Installation of <SUNWeslac> was successful.
    Processing package instance <SUNWesafm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center FMA Service Module for Agent(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center FMA Service Module for Agent as <SUNWesafm>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    92 blocks
    Installation of <SUNWesafm> was successful.
    Package SUNWservicetagr is already installed on this system.
    Validating the Registry entry.
    Package SUNWservicetagu is already installed on this system.
    Validating the Registry entry.
    Package SUNWstosreg is already installed on this system.
    Validating the Registry entry.
    Installing... PRODUCT.PE COMPONENT.CONSOLE
    Package SUNWescom is already installed on this system.
    Validating the Registry entry.
    Package SUNWenesi is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWescon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Console(i386) 4.0,REV=2.9.2007.10.16
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Console as <SUNWescon>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    6638 blocks
    Installation of <SUNWescon> was successful.
    Processing package instance <SUNWesjp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Additional Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Additional Components as <SUNWesjp>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    5819 blocks
    Installation of <SUNWesjp> was successful.
    Package SUNWesaxp is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesclt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Client API(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Client API as <SUNWesclt>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    1609 blocks
    Installation of <SUNWesclt> was successful.
    Processing package instance <SUNWesjrm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Client API support classes(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Client API support classes as <SUNWesjrm>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    663 blocks
    Installation of <SUNWesjrm> was successful.
    Processing package instance <SUNWenesf> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Console properties(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Console properties as <SUNWenesf>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    557 blocks
    ## Executing postinstall script.
    Installation of <SUNWenesf> was successful.
    Package SUNWesgui is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesasc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Advanced Services Console(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Advanced Services Console as <SUNWesasc>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    156 blocks
    Installation of <SUNWesasc> was successful.
    Processing package instance <SUNWescix> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Import/Export(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Import/Export as <SUNWescix>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    156 blocks
    Installation of <SUNWescix> was successful.
    Processing package instance <SUNWsucon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Dynamic Agent Update Console Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Dynamic Agent Update Console Components as <SUNWsucon>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    27 blocks
    Installation of <SUNWsucon> was successful.
    Processing package instance <SUNWescli> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Command Line Interface(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center Command Line Interface as <SUNWescli>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    862 blocks
    Installation of <SUNWescli> was successful.
    Processing package instance <SUNWesclb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Command Line Interface For BatchMode(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Command Line Interface For BatchMode as <SUNWesclb>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    155 blocks
    Installation of <SUNWesclb> was successful.
    Package SUNWesval is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesmc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center MCP Console(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center MCP Console as <SUNWesmc>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    200 blocks
    Installation of <SUNWesmc> was successful.
    Processing package instance <SUNWescdv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Console Dataview(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Console Dataview as <SUNWescdv>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    354 blocks
    Installation of <SUNWescdv> was successful.
    Installing... PRODUCT.PE COMPONENT.SERVER
    Package SUNWescom is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesbui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Web Console(sparc) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Web Console as <SUNWesbui>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    7789 blocks
    Installation of <SUNWesbui> was successful.
    Processing package instance <SUNWesbuh> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Help(sparc) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Help as <SUNWesbuh>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    498 blocks
    Installation of <SUNWesbuh> was successful.
    Package SUNWenesi is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesdb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Database(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Database as <SUNWesdb>
    ## Executing preinstall script.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Group smcdbg created
    User smcdbu created
    ## Installing part 1 of 1.
    /opt/SunMC/SUNWsymon/base <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/bin <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/bin/i386-sun-solaris2.10 <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/lib <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/lib/i386-sun-solaris2.10 <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/lib/sbin <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/sbin <conflicting pathname not installed>
    928 blocks
    Installation of <SUNWesdb> was successful.
    Package SUNWesagt is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWessrv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Server(i386) 4.0,REV=2.9.2007.10.16
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    12 package pathnames are already properly installed.
    Installing Sun Management Center Server as <SUNWessrv>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    10640 blocks
    [ verifying class <preserve> ]
    Installation of <SUNWessrv> was successful.
    Processing package instance <SUNWessa> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Server/Agent(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    10 package pathnames are already properly installed.
    Installing Sun Management Center Server/Agent as <SUNWessa>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    2218 blocks
    Installation of <SUNWessa> was successful.
    Package SUNWesjp is already installed on this system.
    Validating the Registry entry.
    Package SUNWesaxp is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesse> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Server System Files(i386) 4.0,REV=2.10.2007.10.15
    Using </> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center Server System Files as <SUNWesse>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    36 blocks
    ## Executing postinstall script.
    Installation of <SUNWesse> was successful.
    Package SUNWesclt is already installed on this system.
    Validating the Registry entry.
    Package SUNWesjrm is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWmeta> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Metadata Agent(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Metadata Agent as <SUNWmeta>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    38 blocks
    Installation of <SUNWmeta> was successful.
    Package SUNWenesf is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesmdr> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center MDR for Basic Pack(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center MDR for Basic Pack as <SUNWesmdr>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    246 blocks
    Installation of <SUNWesmdr> was successful.
    Package SUNWesgui is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesweb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Web Console(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management C

  • "TrackedMessages_Copy_BizTalkMsgBoxDb" started failing (could not produce a query plan)

    I'm running Biztalk 2010 / SQL 2008R2
    Suddenly the job "TrackedMessages_Copy_BizTalkMsgBoxDb" that runs every minute has started failing. The message is:
    "Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.

    Hi,
    No one has changed any Biztalk SP, I'm sure. I Think this is a data problem. We have a copy of our complete environment taken every 14 Days, used as a test and verification environment. It is now a little more than a week old, and there the job works
    just fine.
    One data difference between the production and the verification environment is that the table "BizTalkdMsgBoxDb.dbo.TrackingMessageReferences"
    is empty in verification, but holds a record in production, could that have to do with it?
    I had  50 "Orphaned DTA Instances" which I removed through the Biztalk Terminator. It made no difference to the problem, still the same error.
    //Haglund_A

  • OPMN start failed - but I can see opmn -d running via ps -ef

    I am trying to figure out why I keep getting the message OPMN start failed when trying to start OPMN. The thing I don't understand is why I can see the processes opmn -d running when I look via ps -ef.
    If I run the opmnctl startall command once more then everything comes up and no error messages.
    Any Ideas?

    I had the same isssue.
    Unix Solaris 10, Oracle Application Server 10gr2
    After starting the infrastructure database and listener the issuing of opmctl startall (starting HTTP Server, OID, OC4J_SECURITY) failed with opmnctl: opmn start failed from time to time.
    In addition, when starting the application server processes (Forms Container...) the processes will rereive a timeout and die later.
    Reading the server logs (e.g. $ORACLE_HOME/dcm/logs/emd_logs/log.xml) on the infrastructure but also on the application server delivered :
    oracle.ias.repository.schema.SchemaDescription: Unable to establish connection to the Oracle Internet Directory Sever
    I came to the impression that the database listener process potentially was not yet fully initialized to receive requests
    from the upstarting infrastructure processes due to the fact that the commands will get issued in a startup-script.
    Solution : after starting the listener (before starting up the infrastructure processes) I entered sleep 10 (wait 10 seconds) in the startup-script, the problem is gone by now...

  • "opmn start failed" after starting infrastrucure as root

    Infrastructure installed and functioning properly until one day I tried to make a startup script to start the infrastructure automaticly every time I restart the computer. After that I cannot start any opmn process.
    After turning the opmn log level to 6, I get this output:
    oracle@infra:~> opmnctl startall
    opmnctl: starting opmn and all managed processes...
    Loading Module libopmnohs callback functions
    Module libopmnohs: loaded callback function opmnModInitialize
    Module libopmnohs: unable to load callback function opmnModSetNumProcs
    Module libopmnohs: unable to load callback function opmnModParse
    Module libopmnohs: unable to load callback function opmnModHelp
    Module libopmnohs: unable to load callback function opmnModDepend
    Module libopmnohs: loaded callback function opmnModStart
    Module libopmnohs: unable to load callback function opmnModReady
    Module libopmnohs: loaded callback function opmnModNotify
    Module libopmnohs: loaded callback function opmnModRestart
    Module libopmnohs: loaded callback function opmnModStop
    Module libopmnohs: loaded callback function opmnModPing
    Module libopmnohs: loaded callback function opmnModProcRestore
    Module libopmnohs: loaded callback function opmnModProcComp
    Module libopmnohs: unable to load callback function opmnModReqComp
    Module libopmnohs: unable to load callback function opmnModInfo
    Module libopmnohs: unable to load callback function opmnModCron
    Module libopmnohs: loaded callback function opmnModTerminate
    and the same errors for every other component
    opmnctl: opmn start failed
    The startup script I wrote:
    #!/bin/bash
    . /etc/rc.status
    rc_reset
    su oracle
    ORACLE_HOME=/opt/oracle/OraInfra
    export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/dcm/bin:$ORACLE_HOME/webcache/bin:$ORACLE_HOME/opmn/bin
    export ORACLE_SID=iasdb
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
    export DISPLAY=10.1.1.201:0.0
    export INFRA=infra.zvs.com.mk
    case "$1" in
    start)
         echo
         echo Starting Listener
         echo -----------------
         $ORACLE_HOME/bin/lsnrctl start
         echo
         $ORACLE_HOME/dbstart
         echo echo Starting all opmnctl controlled processes
         echo -----------------------------------------
         $ORACLE_HOME/opmn/bin/opmnctl startall
         echo
         echo Checking status of app server instances
         echo --------------------------------------Â
         echo Getting status for $INFRA
         $ORACLE_HOME/dcm/bin/dcmctl getState -v -i $INFRA
         echo Starting the EM website
         echo -----------------------
         #$ORACLE_HOME/bin/emctl start oms
         $ORACLE_HOME/bin/emctl start em
    stop)
         echo Stopping the EM website
         $ORACLE_HOME/bin/emctl stop em
         echo Completed
         echo Starting all opmnctl controlled processes
         $ORACLE_HOME/opmn/bin/opmnctl stopall
         $ORACLE_HOME/dbstop
    esac
    rc_exit
    Please help, Borut

    I didn't started any component as root, but I can't finish installing AS 10.1.4.0.1 on Solaris 10 (x86). Tried many times, reinstalling everything, including the OS.
    When I change the log level from 4 to 9, I can see the exact same error messages as you do.
    But the only failing component to me is HTTP_Server.
    No logs under $OH/opmn/log or $OH/Apache/Apache/logs.
    OID and OC4J_SECURITY components are just fine.
    Any help or suggestion would be appreciated.
    Thanks in advance.

Maybe you are looking for

  • 10.4.11 clients failing after login to 10.5.8 server

    I am going crazy trying to setup our xserver this year. I had it running last year without any problems. This year, the 10.4.11 clients keep losing connection to the server after login. After login, the Home folder is there, then gone. You can see it

  • Small thin white line

    I've got an issue I just noticed in the top left corner of my screen. There's a thin white line that doesn't extend the entire screen right by the apple menu. Screenshot: http://www.equals5.com/downloads/imac-screenshot.png It stays there even when I

  • Internal Error 2318

    Hi All, I hope I can find an answer for the problem I have with updating/installing Java 7 (JRE) update 67 32 bit on Windows 8.1 x64 bit system. The 64 bit Java 7 update 67 installs fine. In the past there were no issues with updating JRE 32 bit to n

  • Using java 'classname' vs. appletviewer 'html-filename'

    I have made an applet that I view with appletviewer but I want to use buffered writer in my applet to write to an html file on the server. That way the user can see the results of his/her selections from the applet by clicking on a link from the appl

  • How to export versions, not masters

    I imported 700 photos from an SD card to Aperture then selected them all and had Aperture optimize them, which it did very well. I now have 1400 files -- one master and one version for each photo. I would like to export only the optimized photos, so