Messaging Gateway agent not starting

I have configured Messaging gateway for connecting Oracle AQ to Websphere MQ. Oracle version is Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production on Linux. I was able to execute all the steps as documented in user's guide without any issues. However now when I try to start the Messaging gateway agent, it gives following error ORA-28575: unable to open RPC connection to external procedure agent.
I have tried changing listener.ora without any luck. Is there any compatibility issue between 64-bit linux and MGW? Enclosed below are the entries from my listener.ora
# Define "where" to listen
# ~~~~~~~~~~~~~~~~~~~~~~~~~~
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = AVAQD))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
(ADDRESS = (PROTOCOL = TCP)(Host = adaq03.oneabbott.com)(Port = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
# Pre-Defined Services
# ~~~~~~~~~~~~~~~~~~~~~~~~~~
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SDU = 1460)
(SID_NAME = AVAQD)
(GLOBAL_DBNAME = AVAQD)
(SERVICE_NAME = AVAQD.world)
(ORACLE_HOME = /ofa/product/10.2.0/DB)
(SID_DESC =
(SID_NAME = mgwextproc)
(ENVS = EXTPROC_DLLS=/oracle_home/lib32/libmgwagent.so, LD_LIBRARY_PATH=/oracle_home/jdk/jre/lib/i386:/oracle_home/jdk/jre/lib/i386/server:/oracle_home/lib32)
(ORACLE_HOME = /ofa/product/10.2.0/DB)
(PROGRAM = /ofa/product/10.2.0/DB/bin/extproc32)
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /ofa/product/10.2.0/DB)
# (ENVS=EXTPROC_DLLS=/ofa/product/10.2.0/DB/lib32/av_extproc_LINUX.so)
(PROGRAM = extproc)
Thanks in advance
Kiran

Hi,
I got this working finally. All of the issues were mainly related to properly setting environment variable LD_LIBRARY_PATH. Oracle Metalink helped in solving those issues so I recommend searching there first if you are getting stuck.
Regards
Kiran

Similar Messages

  • When restarting server after a crash, Messaging bridges are not starting

    Hi,
    We have Messaging bridge configured with Exactly-Once QOS to read messages from IBM Websphere MQ to Weblogic distributed Queue. We are using Weblogic 10gR3.
    1. We killed the weblogic server which was reading message from source destination(IBM MQ). We did this to check whether any message is lost when a server crashes.
    2. Then we restarted the weblogic application server and checked the weblogic messaging bridge status.
    3. The messaging bridge was not started properly and the following Exception was thrown.
    ####<Apr 22, 2010 4:09:11 PM BST> <Error> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-056A9014D88E2BE368B7> <> <12312323333> <BEA-200015> <An error occurred in bridge "BRIDGE" during the transfer of messages (javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
    javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
    at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:941)
    at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:630)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:438)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
    at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
    at $Proxy87.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1427)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    .).>
    ####<Apr 22, 2010 4:09:11 PM BST> <Warning> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948951881> <BEA-200026> <Bridge "BRIDGE" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.bridge.internal.MessagingBridgeException.)>
    ####<Apr 22, 2010 4:09:12 PM BST> <Info> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948952726> <BEA-200020> <Bridge "BRIDGE" is stopped.>
    Please give your suggestions to fix this issue.
    Thanks!
    Edited by: user11340353 on 28-Apr-2010 06:34

    Hi,
    *The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
    *The resource adaptor was started properly.
    *We are using file store. But will it make a difference?
    Thanks!

  • Message server will not start on AIX 6

    I have a standard ECC6 system running the 185 kernel and ORACLE 10.2.0.2 on AIX 6. which is giving me a problem. I also have 2 other systems apparently with the same configuration which operate perfectly.
    The problem I have is that if I stop the system the message server will not start. If I wait until the following day the message server starts pefectly. I have not been able to test stopping the system and waiting an hour or so and then restarting in the same day, so I do not know if the overnight wait is relevant.
    dev_ms contains the following:
    [Thr 01] Fri Jun 19 23:58:54 2009
    [Thr 01] WLM Tag 'HQS/MSG' successfully set for this process
    [Thr 01] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
    systemid   324 (IBM RS/6000 with AIX)
    relno      7000
    patchlevel 0
    patchno    163
    intno      20050900
    make:      multithreaded, ASCII, 64 bit, optimized
    pid        254088
    [Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 254088) [msxxserv_mt. 1835]
    [Thr 01] SigISetDefaultAction : default handling for signal 20
    [Thr 01] ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cp
    p 3227]
    [Thr 01] *** ERROR => NiIBindSocket: SiBind failed for hdl 1 / sock 8
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:3950) [nixxi.cpp    3227]
    [Thr 01] *** ERROR => MsSCommInit: NiBufListen(3950) (rc=NIESERV_USED) [msxxserv
    _mt. 10186]
    [Thr 01] *** ERROR => MsSInit: MsSCommInit (internal) [msxxserv_mt. 1886]
    [Thr 01] *** ERROR => main: MsSInit [msxxserv_mt. 5951]
    [Thr 01] ***LOG Q02=> MsSHalt, MSStop (Msg Server 254088) [msxxserv_mt. 5999]
    Regards,
    Paul Richardson
    Certified Netweaver, Portal and Migration Consultant
    Sandpiper I.T. Ltd

    Hi,
    Thr 01 ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cp p 3227]
    Looks like port 3227 is already used. You can check the ports by netstat -a -n from your command prompts. Also check your settings in /etc/services and /etc/hosts files.
    Check your filewall rules/disable antivirus if any and give a go.
    Hope this helps.
    Manoj

  • Gateway could not start

    we had installed 2005q4m3 sp1 and new gateway.
    I did gateway -i to install and gateway -s to start the gateway and got this error.
    C:\Program Files\SunIdentityManager6\gateway>gateway -i
    06/05/2007 10.54.24.021000 [14356] (../../../../src/wps/agent/logging/WSTrace.cp
    p,150): trace active, level: 4, file: C:/gatewaytrace.txt, maxSize: 500 KB
    06/05/2007 10.54.24.021000 [14356] (../../../../src/wps/agent/logging/WSTrace.cp
    p,108): In WSTrace::init()
    06/05/2007 10.54.24.021000 [14356] (../../../../src/wps/agent/logging/WSTrace.cp
    p,109): Gateway version: 'Sun Java System Identity Manager 6.0 SP1'
    06/05/2007 10.54.24.031000 [14356] (../../../../src/wps/agent/logging/WSTrace.cp
    p,110): OS version: 'Windows Server 2003 Family Service Pack 2 (Build 3790)'
    An error occured when trying to install the service: No error
    C:\Program Files\SunIdentityManager6\gateway>gateway -s
    06/05/2007 10.54.35.087000 [15692] (../../../../src/wps/agent/logging/WSTrace.cp
    p,150): trace active, level: 4, file: C:/gatewaytrace.txt, maxSize: 500 KB
    06/05/2007 10.54.35.087000 [15692] (../../../../src/wps/agent/logging/WSTrace.cp
    p,108): In WSTrace::init()
    06/05/2007 10.54.35.087000 [15692] (../../../../src/wps/agent/logging/WSTrace.cp
    p,109): Gateway version: 'Sun Java System Identity Manager 6.0 SP1'
    06/05/2007 10.54.35.087000 [15692] (../../../../src/wps/agent/logging/WSTrace.cp
    p,110): OS version: 'Windows Server 2003 Family Service Pack 2 (Build 3790)'
    06/05/2007 10.54.35.097000 [15220] (../../../../src/wps/agent/util/ThreadRunner.
    cpp,61): Waiting for request event
    An error occured when trying to start the service: No such file or directory
    Can anybody point me what could be going wrong here?
    Thanks.

    Im using IDM 7.1. The gateway suddenly stopped working. Even after System restart & reinstallation of gateway, it's still not getting started. It there anything that I should do more.

  • Message bean does not start automatically during application server startup

    I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
    Thanks,
    Bill
    #1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
    #1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
    #1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
    #1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
    #1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
    #1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
    #1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
    #1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
    #1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    ... 12 more
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
    Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
    #1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
    #1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                    at java.lang.Class.getDeclaredConstructors0(Native Method)
                    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                    at java.lang.Class.getConstructor0(Class.java:1930)
                    at java.lang.Class.newInstance0(Class.java:278)
                    at java.lang.Class.newInstance(Class.java:261)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                    at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                    at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at javax.security.auth.Subject.doAs(Subject.java:379)
                    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

  • Sql Server Agent not starting automatically in failover in a clustered environment.

    Hi,
    We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
    server. In the Sql Server Configuration manager we find that service of
    the Sql Server(database engine) as got a start mode as manual being
    an instance in the 2 node cluster. When the node in which the service is
    running fails the the Sql Server service gets started in the other node. However
    we find that the  Sql Server Agent service(whose start mode is also in manual)
    does not get started automatically in the other node along with the Sql Server
    service.Why does the cluster service do not start Sql Server agent service as well.
    Should we make the Sql Server agent service start mode to be automatic
    instead of being manual as it is now? Thanking you in advance
    Binny Mathew

    Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
    failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
    leave it as manual
    Satish Kartan www.sqlfood.com
    I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
    online, when a failover happens.
    Satish Kartan www.sqlfood.com

  • Sql server agent not starting

    I installed sql server 2008 r2 sp2
    sql server agent is not allowing me to start it.
    I run SSCM right click agent but start,stop menus are disabled

    i have only one sql instance named SQLEXPRESS
    The SQL Server Agent is installed with the Express Edition of SQL Server, but it's not a Feature of the Express Edition, therefore you can't start the Agent.
    See
    Features Supported by the Editions of SQL Server 2014
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Messages Beta Does Not Start Hidden

    I have selected the box to hide application in System Preferences >> User and Groups >> Messages. However when I log into OS X Lion 10.7.3 the primary messages window pops up. My desire is to have it started but minimized to the dock (similar to Finder). Is there something I'm missing or is there another avenue I can take to accomplish my goal.

    HI,
    I have the System Preferences > General section set to "Restore Windows on Quitting and re-opening apps"
    If I close down all apps before a Restart or Shut Down I expect to have only those App I leave open to be restarted
    At present I am getting my Browser, Mail and Skitch restarting.
    I had also added Messages to the Login list (and chosen to Hide it) but it did not start (It had been off for a while before I tried this.)
    I will try a few things to solve my issue before commenting further.
    9:47 PM      Sunday; April 8, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • Error Message: "Skype can not start because the system is not available"

    Try to reset all Skype settings. Quit Skype or use Windows Task Manager to kill any Skype.exe process. Go to Windows Start and in the Search/Run box type %appdata% and then press Enter or click the OK button. The Windows File Explorer will pop up. There locate a folder named “Skype”. Rename this folder to something different, e.g. Skype_old. Next go to Windows Start and in the Search/Run box type %temp%\skype and then press Enter or click the OK button. Delete the DbTemp folder. Restart Skype. N.B. If needed, you will still be able to re-establish your call and chat history. All data is still saved in the Skype_old folder. 

    Okay!
    I'm newbie here, but it doesn't matter. I dont want to do here anything else, just write off my opinion about the Microsoft's "new" Skype, and I hope they will read...
    This is a cropped image - of course hungarian, because I'm hungarian, but I think many of us could see this as well. How this is possible? "The Skype can not start because the system is not available" *** What kind of system? The Skype was on a P2P system, where is impossible that the system is not available! This is why the skype was much better than the Microsoft's messenger. Then they bought it, and make it wrong...
    I found a solution for this problem, this can happen if my client is not updated. But IT IS!
    How does it works? Can we use the **bleep** Skype how we would like to use? Or this time we need to find an other application (like Viber), and using that while they not buying that as well, just because that is better?
    Edited to conform with the Community Guidelines
    Subject/title edited to better reflect post content.

  • Oracle Workflow Java Activity Agent not starting up

    Hi,
    I am trying to start the Java Activity agent of Oracle workflow.
    As specified in the installation and setup guid I am running the following script (for NT):
    wfjvlsnr user/password@connectString
    The activiy agent does start up but then I get a NullPointerException in the main thread of the Java Activity Agent class.
    Appreciate you help.
    thanks.
    Here is the dump.
    E:\Ora9idb\wf\admin>rem ******************************************************
    E:\Ora9idb\wf\admin>rem $Header: wfjvlsnr.bat 26.5 2001/07/02 09:13:06 smayze
    ship $
    E:\Ora9idb\wf\admin>rem USAGE:
    E:\Ora9idb\wf\admin>rem 1) Workflow Schema User/Password@Database
    E:\Ora9idb\wf\admin>rem 2> "Workflow Schema User Password Database [protocol
    [charset]
    E:\Ora9idb\wf\admin>rem To disable output, use the jrew command instead of jre
    E:\Ora9idb\wf\admin>rem ******************************************************
    E:\Ora9idb\wf\admin>set WF_UN=workflow/workflow@workflow
    E:\Ora9idb\wf\admin>set WF_CHARSET=
    E:\Ora9idb\wf\admin>IF "" NEQ "" set WF_CHARSET=-DCHARSET=
    E:\Ora9idb\wf\admin>set WF_CLASSPATH=;e:\Ora9idb\wf\java;C:\PROGRA~1\Oracle\jr
    1.1.8\lib\rt.jar;e:\Ora9idb\wf\java;e:\Ora9idb\jlib\wfjava.jar;e:\Ora9idb\wf\x
    \java\lib\xmlparserv2.jar;e:\Ora9idb\jlib\wfapi.jar;e:\Ora9idb\jdbc\lib\classe
    11.zip;e:\Ora9idb\jlib\share.jar;e:\Ora9idb\jlib\ewt3.jar;e:\Ora9idb\jlib\ewt3
    ls.jar;e:\Ora9idb\jlib\swingall-1_1_1.jar;
    E:\Ora9idb\wf\admin>"C:\PROGRA~1\Oracle\jre\1.1.8\bin\jre" -classpath ";e:\Ora
    db\wf\java;C:\PROGRA~1\Oracle\jre\1.1.8\lib\rt.jar;e:\Ora9idb\wf\java;e:\Ora9i
    \jlib\wfjava.jar;e:\Ora9idb\wf\xml\java\lib\xmlparserv2.jar;e:\Ora9idb\jlib\wf
    i.jar;e:\Ora9idb\jdbc\lib\classes111.zip;e:\Ora9idb\jlib\share.jar;e:\Ora9idb\
    ib\ewt3.jar;e:\Ora9idb\jlib\ewt3-nls.jar;e:\Ora9idb\jlib\swingall-1_1_1.jar;"
    nojit oracle.apps.fnd.wf.WFFALsnr workflow/workflow@workflow
    Oracle Workflow 2.6.0 JAVA Function Activity Agent
    Connected to workflow@workflow with character set UTF8
    Listening...
    Wed Aug 28 12:14:11 GMT+05:30 2002 Executing TEST_REQ/9996 test.SelectApprover
    PUT APPROVER_NAME=CDOUGLAS
    Wed Aug 28 12:14:11 GMT+05:30 2002 Enqueuing TEST_REQ/9996 test.SelectApprover
    Wed Aug 28 12:14:11 GMT+05:30 2002 Executing TEST_REQ/9997 test.SelectApprover
    PUT APPROVER_NAME=CDOUGLAS
    Wed Aug 28 12:14:11 GMT+05:30 2002 Enqueuing TEST_REQ/9997 test.SelectApprover
    Wed Aug 28 12:14:11 GMT+05:30 2002 Executing TEST_REQ/9998 test.SelectApprover
    PUT APPROVER_NAME=CDOUGLAS
    Wed Aug 28 12:14:11 GMT+05:30 2002 Enqueuing TEST_REQ/9998 test.SelectApprover
    Wed Aug 28 12:14:11 GMT+05:30 2002 Executing TEST_REQ/9999 test.SelectApprover
    PUT APPROVER_NAME=CDOUGLAS
    Wed Aug 28 12:14:11 GMT+05:30 2002 Enqueuing TEST_REQ/9999 test.SelectApprover
    Wed Aug 28 12:14:11 GMT+05:30 2002 Executing TEST_REQ/99910 test.SelectApprove
    PUT APPROVER_NAME=CDOUGLAS
    Wed Aug 28 12:14:12 GMT+05:30 2002 Enqueuing TEST_REQ/99910 test.SelectApprove
    T
    Wed Aug 28 12:14:12 GMT+05:30 2002 Executing WFEVDEME/PO3435 oracle.apps.fnd.w
    XMLGetTagValue
    GET ATTR=REQUESTOR
    GET EVENT=EVENTMESSAGE
    GET TAG=/ORDER/REQUESTOR
    PUT REQUESTOR=BLEWIS
    Wed Aug 28 12:14:12 GMT+05:30 2002 Enqueuing WFEVDEME/PO3435 oracle.apps.fnd.w
    XMLGetTagValue
    Wed Aug 28 12:14:12 GMT+05:30 2002 Executing TEAC_IT1/SYSADMIN JayTestFunction
    PUT TEST_RESULT=JAVA
    Wed Aug 28 12:14:12 GMT+05:30 2002 Enqueuing TEAC_IT1/SYSADMIN JayTestFunction
    Wed Aug 28 12:14:12 GMT+05:30 2002 Executing TEST_REQ/9996 test.ApproveRequisi
    on
    PUT TEST_ATTRIBUTE=This value was set in the Approve Requisition Activity
    Wed Aug 28 12:14:12 GMT+05:30 2002 Enqueuing TEST_REQ/9996 test.ApproveRequisi
    on
    Exception in thread "main" java.lang.NullPointerException:
    at oracle.apps.fnd.wf.WFFALsnr.listen(WFFALsnr.java)
    at oracle.apps.fnd.wf.WFFALsnr.main(WFFALsnr.java)
    E:\Ora9idb\wf\admin>

    Hi,
    I tried to run the same without entering password,but still i am getting error.
    The error description is:
    Oracle Workflow 2.6.3 JAVA Function Activity Agent
    Please Enter Database Password :
    ORA-06401: NETCMN: invalid driver designator
    Unable to connect to nn0734.nucleussoftware.com:1521:asdb
    Accepted arguments:
    java <program> <user> <conStr> [oci8]
    java <program> <user> <conStr> thin
    Where <conStr> is in the form of <host>:<port>:<sid> for thin
    and DB Service name for oci8
    Please Help. Is there any problem with my tnsnames.ora or something else.
    Thanx in advance,
    Sarab

  • Sql 2012 server for SCCM 2012 - Agent not starting

    Hi ,
      In our environment we have a Sql 2012, and it was working fine till now.  but after installation of RDP role and subsequent installation of certificates for remote desktop in the SCCM server ( SQL 2012 is
    installed in it) 
    we are facing the issue - Sql server management studio not connecting ( windows authenticaltion)
    1) A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)A
    2) I tried starting the sql agent service in services.msc  and the below error came 
    The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped. 
    Some services stop automatically if they are not in use by other services or programs.
    3) In the Sql Server configuration manager also tried starting the sql agent but 
    The request failed or the service did not respond in a timely fashion. 
    Consult the event log or other applicable error logs for details.
    The widows event logs show this error
    A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. 
    The TLS protocol defined fatal error code is 20. The Windows SChannel error state is 960.
    We have removed the certificate and the RDP role in that . 
    Can anyone please help on this
    Anand M

    I would check for error messages in the SQL Server ERROLOG file and also Agent's SQLAGENT.OUT file.
    Tibor Karaszi, SQL Server MVP |
    web | blog

  • SQL 2005 Server Agent not starting job

    Apologies if this question has been asked elsewhere on these forums, I've had a search around and have not been able to find something with the same issues.
    Last year I took over management of a SQL server (SQL2005 on a Server 2003 R2 O/S), as part of the expansion of operation the DB server is being used for an agent job was created to take customer information from our web site and, where the customer has
    selected to be contacted, pass those details to our dialler system, so we can rech our customer ideally within 20 minutes of them interacting with the website.
    This job runs daily Monday to Friday from 8am to 4:30pm at 15 minute intervals and once a day at 5pm on Saturday and Sunday(same job with muliple schedules), 3 week ago the Saturday job failed to start, then following week the Sunday job failed to start
    then last weekend the job failed to start on both Saturday and Sunday. There have been no updates or changes made to the job or the server and the job has run for 6 months with this multiple scehduling without any issues at all.
    I have checked through the server event/system/application logs and the SQL logs (that I know of) and can find no evidence of errors that would have an effect on the SQL or SQL Agent operation, I can also find no evidence that the server made an attempt
    to start the job at all, the application log will normally show an event 12288 and 12289 with the source of SQLISPackage for the start and stop of the job. There is no event start notice shown in the application event log on weekend days the job has failed
    to start. I've check the Agent service status, as well as all the other SQL services and they are all running as they should be.
    Does anyone have any ideas where I should be looking next for the cause of this issue or has anyone ever experienced this before and found a cause?
    Many thanks
    Stuart.

    Hi all,
    thank you for your replies, I will try to address the issues/questions you have raised.
    @Satish - The job takes on average 40 seconds to complete, so there would no chance of the previous job run still being active and stopping a new attempt. Also on the days that the job has failed it is the only time that day that the job is run.
    @Sofiya Li - There are no errors to report, the job simply fails to start at all, this is bourne out
    by the 'Job Step Execution History For The Last 7 Days' this shows no that the job ran sucessfully with no fails or retrys, so there are no error messages to post or invesitgate. Running the job manually results in a success (but the job runs every 15 minutes
    anyway during the day without fails), the job uses the same credentials during the daily 15 minutes runs on weekdays as it does on the weekends, also if the website had any issues capturing customer information the missing information would not be in the table
    that the dialling information is drawn from and the job should still start and run even if the website capture is not working(these are seperate jobs), it would just return no information. 
    @Shanky_621 There is normal scheduled maintenance that runs on the DB but this occurs at midnight. The
    logs show that all services were running and nothing was in a wait/held state.
    Thanks again for your suggesions
    Stuart

  • SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)

    I am getting the following message when I start the agent.  I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects.  Just eventually times out after 30 mins.
    FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.

    cat dev_SMDAgent
    trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
    node name   : smdagent
    pid         : 17393
    system name : SMD
    system nr.  : 98
    started at  : Wed Oct  7 08:56:32 2009
    arguments         :
              arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
              arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
              arg[02] : -DSAPINFO=SMD_98_server
              arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
    -> ms host    :
    -> ms port    : 36
    -> OS libs    : /usr/sap/SMD/exe
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SMD/J98/profile/smd.properties
    Instance properties
    -> ms host    :
    -> ms port    : 36
    -> os libs    : /usr/sap/SMD/exe
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    Worker nodes
    -> [00] smdagent             : /usr/sap/SMD/J98/profile/smd.properties
    [Thr 182894174624] Wed Oct  7 08:56:32 2009
    [Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
    [Thr 182894174624] SigISetDefaultAction : default handling for signal 17
    [Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182894174624] CPIC (version=701.2009.01.26)
    [Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
            Java Home: /opt/IBMJava2-amd64-142
    [Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
    JStartupIReadSection: read node properties [smdagent]
    -> node name          : SMDAgent
    -> node type          : server
    -> node id            : 1
    -> node execute       : yes
    -> java path          : /opt/IBMJava2-amd64-142
    -> java parameters    : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
    -> java vm version    : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    -> java vm vendor     : IBM J9 VM (IBM Corporation)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 256M
    -> init heap size     : 256M
    -> root path          : ../SMDAgent
    -> class path         : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> OS libs path       : /usr/sap/SMD/exe
    -> main class         : com.sap.smd.agent.launcher.SMDAgentLauncher
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
    -> parameters         : run jcontrol
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 58981
    -> shutdown timeout   : 20000
    [Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -DP4ClassLoad=P4Connection
    -> arg[  4]: -Xj9
    -> arg[  5]: -Xmn50m
    -> arg[  6]: -Xgcpolicy:gencon
    -> arg[  7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
    -> arg[  8]: -Dapplication.home=/usr/sap/SMD/exe
    -> arg[  9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    -> arg[ 11]: -Dmemory.manager=256M
    -> arg[ 12]: -Xmx256M
    -> arg[ 13]: -Xms256M
    -> arg[ 14]: -DLoadBalanceRestricted=no
    -> arg[ 15]: -Djstartup.mode=JCONTROL
    -> arg[ 16]: -Djstartup.ownProcessId=17393
    -> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
    -> arg[ 18]: -Djstartup.whoami=server
    -> arg[ 19]: -Djstartup.debuggable=yes
    -> arg[ 20]: -DSAPINFO=SMD_98_server
    -> arg[ 21]: -DSAPSTARTUP=1
    -> arg[ 22]: -DSAPSYSTEM=98
    -> arg[ 23]: -DSAPSYSTEMNAME=SMD
    -> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
    -> arg[ 25]: -DSAPDBHOST=
    -> arg[ 26]: -Dj2ee.dbhost=
    [Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
    -> arg[  0]: run
    -> arg[  1]: jcontrol
    [Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1086335328] Wed Oct  7 08:56:35 2009
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1086335328] Wed Oct  7 08:56:38 2009
    [Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
    [Thr 1101334880] Wed Oct  7 08:56:43 2009
    [Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
    [Thr 1101334880] Wed Oct  7 08:56:48 2009
    [Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]

  • OVS-Agent not start..

    Hi guys,
    after a lot of tries to configure OVM Server 3.0.2 with OVM Manager 3.0.2, now ovs-agent on server doesn't start anymore
    here is the log:
    [root@vmoracle ~]# /etc/init.d/ovs-agent restart
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/agtctl", line 25, in ?
    from OVSCluster import server_cluster_online, server_cluster_offline
    File "/opt/ovs-agent-3.0/OVSCluster.py", line 28, in ?
    from OVSPoolFileSystem import (create_dmnfs_device, remove_dmnfs_device,
    File "/opt/ovs-agent-3.0/OVSPoolFileSystem.py", line 316
    raise OSError in ocfs2_file_lookup() if corrupted
    ^
    SyntaxError: invalid syntax
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/agtctl", line 25, in ?
    from OVSCluster import server_cluster_online, server_cluster_offline
    File "/opt/ovs-agent-3.0/OVSCluster.py", line 28, in ?
    from OVSPoolFileSystem import (create_dmnfs_device, remove_dmnfs_device,
    File "/opt/ovs-agent-3.0/OVSPoolFileSystem.py", line 316
    raise OSError in ocfs2_file_lookup() if corrupted
    ^
    SyntaxError: invalid syntax
    [root@vmoracle ~]#
    i've already tried to "zero disk" the mapper, but doesn't work.. last chance is to destroy LUN on the storage and represent to the host, but this is not an elegant solution (but all OVM infrastructure not seems so good compared to XenServer and ESXi)
    Edited by: user8287971 on Nov 28, 2011 4:40 PM

    Mongolian wrote:
    Please tell me what will i do?I would completely reinstall. Looks like your system wasn't installed properly or something went terribly, terribly wrong.

  • 11.1.2.2 RA Framework Agent not starting

    Hopeing someone may have seen this. I have an 11.1.2.2.300 install of RA on a server and the RA Agent does not come up all the way. I get this message in the agent log.
    Thanks for any info.
    til.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line: java.lang.IllegalArgumentException: Invalid cipher text or key argument. ${setupSettings.gsmContextId} [102, 48, 56, 100, 54, 54, 57, 100]
    [2013-05-09T11:26:05.002-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 12] [ecid: 0000JuA7G3VBt11_zto2yW1HYwsB000004,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line: SUCCESS: Fetching OneCrypt key factory impl
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.utils.OneCrypt.decrypt(Unknown Source)
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.utils.OneCrypt.decrypt(Unknown Source)
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.config.impl.ServerConfig.decrypt(Unknown Source)
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.config.impl.XMLConfigHandler.decrypt(Unknown Source)
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.config.impl.XMLConfigReader.getGSMContextID(Unknown Source)
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.config.impl.ServerConfig.init(Unknown Source)
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.config.impl.ServerConfig.<init>(Unknown Source)
    [2013-05-09T11:26:05.003-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.system.Server.initialize(Unknown Source)
    [2013-05-09T11:26:05.004-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.system.Server.initialize(Unknown Source)
    [2013-05-09T11:26:05.004-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.brio.one.system.Server.main(Unknown Source)
    [2013-05-09T11:26:05.004-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at com.sqribe.transformer.SuperServerImpl.main(Unknown Source)
    [2013-05-09T11:26:05.004-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line: Caused by: java.lang.NumberFormatException: For input string: "${"
    [2013-05-09T11:26:05.004-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
    [2013-05-09T11:26:05.004-05:00] [EPMAGENT] [TRACE] [] [oracle.EPMAGENT.com.oracle.cmc.util.StreamRedirect] [tid: 13] [ecid: 0000JuA7G3XBt11_zto2yW1HYwsB000005,0] [SRC_CLASS: com.oracle.cmc.util.StreamRedirect] [SRC_METHOD: run:66] Redirecting Stream Read Line:      at java.lang.Integer.parseInt(Integer.java:449)

    Mady thanks but had already done that as well as other things. Here is the gist of the resolution.
    The problem turned out to be due to a VMWare upgrade. The latest 5.1x of Vmware apparently makes some changes to the RPC services.
    Our system was running ok during the VM upgrade only when we had to do a reconfigure did the RA not come up.
    The RA utilizes RPC,CORBA and RMI so all the stuff VMWare touched.
    We got a Fresh VMWare server to test with and all came up. So had the other RA server re-imaged and RA core came up and working.
    Note it was only the RA Core the RA Framework Agent that was having the problem. Remember that the RA Agent is the traffic cop in the EPM System.
    Cheers,

Maybe you are looking for

  • Touchsmart 600-1120 successfully upgraded to Windows 8 Pro

    I just wanted to report my Touchsmart 600-1120 (BK139AA) was successfully upgraded from Win7 64 bit to Windows 8 Pro 64 bit, and I haven't run into any issues.   Here are the steps I went though. 1. Made disk image backup using Win7 Backup and Restor

  • Table Sequence number

    Hi All, I have a scenario which goes like this: We have a common table(Table1) in our DB which maintains the sequence numbers(we are not using oracle supplied db sequence). For every transaction we are using the current sequence number from the table

  • Posting line item currency different than header curency

    Hi ALL, Is there any way in SAP where I can post line items in a different currency that header currency? for e.g.  Doc header currency - USD Line item 1 Dr A/c -  Amount in USD Line item 2 Cr A/C - Amount in CAD Can you please let me know if it is p

  • Deleted Event Log Alerting Rule Still Generating Thousands of Alerts

    I deleted a rule that is somehow still sending a ton of alerts. ---Deleted Rule ---Deleted agent server from SCOM I cannot find where this is coming from. Any tips guys? Thanks

  • [SOLVED]Can't build perl-text-glob

    Hello. I'm trying to install Clamtk and perl-text-glob is a dependency. Everything works fine until perl-text-glob is trying to build, then I get this error: Starting build()... /tmp/yaourt-tmp-root/aur-perl-text-glob/./PKGBUILD: line 27: cd: /tmp/ya