Jdeveloper 11.1.1.6.2 is "NOT" allowing to configure application server

when configuring application server on local Jdev (11.1.1.6.2) > Build JDEVADF_11.1.1.6.2_GENERIC_120329.1447.6268 on Windows 7
i get below error
===================================================
Dec 29, 2012 12:52:35 AM oracle.security.jps.internal.common.util.XmlSchemaValidationUtil$StrictErrorHandler warning
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: line 3 column 96.
Problem invoking WLST - Traceback (innermost last):
File "C:\oracle\Jdev111162\JDEV_INSTALL\jdeveloper\fadev\bin\FADevExtendDefaultDomain.py", line 583, in ?
File "C:\oracle\Jdev111162\JDEV_INSTALL\jdeveloper\fadev\bin\FADevExtendDefaultDomain.py", line 253, in extendDomain
File "C:\Users\krathanr.ST-IDC\AppData\Local\Temp\WLSTOfflineIni7049264434314395379.py", line 89, in addTemplate
     at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
     at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1538)
     at com.oracle.cie.domain.script.jython.WLScriptContext.addTemplate(WLScriptContext.java:420)
     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:597)
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.ScriptException: unable to parse "template-info.xml" from template jar "C:\oracle\JDEV11~1\JDEV_I~1\jdeveloper\common\templates\applications\oracle.bicomposer.slib_template_11.1.1.jar
===================================================
Please help.
Thanks
KrishnaKumar

Does this happen the first time you start the wls?
Or have you first started the wls and then tried to extent it?
Timo

Similar Messages

InfoSpoke fails with message "Could not open file on application server"

BW Experts,
I created an InfoSpoke that is configured to extract to a flat file. The name of the file is specified using a logical filename. During extraction, the infospoke reports the error message "Could not open file on application server" adnd marks the extraction process as red(failed). I have tried to run the InfoSpoke in background mode and in dialog mode and the same error appears. After i run in dialog mode, i checked SU53 for authorization errors and did not find any. I also tried changing the Logical filename setup in transaction FILE to a more "friendly" directory in which i'm sure i have authorizations (e.g. my UNIX home directory) and im still getting errors.
Can you please share your thoughts on this? Any help will greatly appreciated. I also promise to award points.

Hi Nagesh,
Thanks for helping out.
If i configure the InfoSpoke to download to a file using "File Name" option and also check the "Application server" checkbox, the extract works correctly (extraction to the defualt SAP path and filename=infospoke name). If i configure the InfoSpoke to download to the local workstation, the InfoSpoke also works correctly. It's only when i configure it to download to the application server and use the "Logical filename" option, that i encounter a failed extract.
Here are the messages is the Open Hub Monitor:
(red icon) Request No.147515
0 Data Records
Runtime 1 sec.
(red icon)Run No. 1
0 Data Records
Runtime 1 sec.
Messages for Run
Extraction is running RSBO 305
Could not open file on application server RSBO 214
Request 147515 was terminated before extraction RSBO 326
Request 1475151: Error occured RSBO 322
If i clink on the error message, no messages nor clues are displayed. Note, this is a new InfoSpoke that is currently in the dev system.
Please help.

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

Java.lang.Exception: User : principals=[admin] is not allowed to shutdown the server

Hi,
When i shut down my managed and admin servers through the console i am getting
the following exception.Any one have an idea on this?
Exception :
java.lang.Exception: User : principals=[admin] is not allowed to shutdown the
server.
     at weblogic.server.ServerLifeCycleRuntime.shutdown(ServerLifeCycleRuntime.java:299)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:750)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:732)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:928)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:472)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:200)
     at $Proxy105.shutdown(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.performOnSingle(DoMBeanOperationAction.java:206)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.perform(DoMBeanOperationAction.java:188)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

I have the exact same problem. It is for a WLI 7.0 SP-5 domain. I started admin and managed servers using the startWeblogic and startManagedWebLogic scripts, but trying to stop them from the console is throwing this exception:
java.lang.Exception: User : principals=[admin] is not allowed to shutdown the server.
     at weblogic.server.ServerLifeCycleRuntime.shutdown(ServerLifeCycleRuntime.java:299)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:736)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:718)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:1107)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:472)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:200)
     at $Proxy105.shutdown(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.performOnSingle(DoMBeanOperationAction.java:206)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.perform(DoMBeanOperationAction.java:188)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1094)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:437)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:319)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5626)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3213)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2555)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
I upgraded from WLI7.0 SP-1 to SP-5, and since then I am getting this error.
Please help!

Could not start Sun Java Application Server

Hi ,
I have been using JSC for a while, now and then it reports an error " could not start sun java application server...". Does any one know why it s not able to start java application server..
Before you say anything, I have tried
1. use netstat to find any port conflicts.
2. Tried to start application server manually
3. shut down and start studio creator and then try running the project
4. shut down and start PC
unfortunately none of them helped
Only reinstalling resolved the problem. But I cant keep reinstalling very often.
Does any one know the permanent solution for this problem.
Cheers
kush

Sometimes it appears this is a timeout issue because it's taking too long to come up. As Jonathan says, undeploy can help with this (along with his other suggestions).
How many deployed projects do you see (in the server navigator you can open up the deployed server and see what's out there)?
I periodically undeploy "junk" projects that I'm not really using because they slow down the server startup (same thing happens I believe for tomcat... when the server starts it has to load them all and it takes awhile). You can undeploy from within the server navigator by drilling into the server nav and right clicking on the deployed app and choosing undeploy... or you can use the server admin tool.
hth,
v

Java is not active in the application server

Hi Experts
We recently installed CRM 5.0. Everything seems to have installed without any issues.
However, we are having a few issues the Java Virtual Machine (VMC).
When trying to access the VMC through ABAP side of CRM (SM53), it gives and error message that "Java is not active in the application server".
Eventhough everything seems to have been installed.
Any ideas on how to activate java.
Any help would be really appreciated.
Thanks
Imran Khan

Hi Daniele:
There are indeed only 3 parameter additions
vmcj/enable = on
vmcj/option/ps = 512M
vmcj/option/maxJavaHeap = 200M
The 4th one is just explanation for calculating sizes.
My VMC is active with only the above three settings.
Also make sure that the SP level for both the JAVA components and ABAP components is the same. i.e. they are both running on the latest version. The latest update was released in Late April.
If the SPs are from differnt releases, the VMC will not work.
Also, go into the server and have a look at the parameter file to make sure that settings are actually there. i have found out that settings in RZ10 and the real parameter settings can be different. Just make sure that the settings you want the system to take are indeed in the real parameter file.
I am not sure what else you can do...but rest assured that the thing works with the above mentioned settings.
Imran

Client with IP address is not allowed to access the server

While trying to connect to the SQL Database on Windows Azure via SQL Server Data Tools 2012 (from local), it gives me a message "Client with IP address 'X.X.X.X' is not allowed to access the server". And in the message it also gives you the direction
on how to fix this.
So, going back to the Windows Azure Management Portal, I have included the current IP address in to the existing firewall rule. I tried to connect to the sql database on azure via SSDT it worked properly.
Next day.. when I open the tool and trying to connect, it gave the same error, so I checked in the portal and this time it was showing different IP, then I added this IP to the firewall list, and I was able to connect.
Question: Is this a normal behaviour for adding IP each day to the firewall rule? (OR, I am using the "Free Trial" subscription, is this the issue?), or is there anything more I need to do to avoid adding the IP each day?
Please let me know.
Thank you.

Hello,
To workaround your requirement, you can try to use the New- SqlAzureFirewallRule command line in PowerShell to configure the firewall rule allow your current IP automatically.
Reference:
Update Azure DB Firewall Rules with PowerShell
http://social.msdn.microsoft.com/Forums/windowsazure/en-us/67540278-1f54-491b-9dd2-73587cf51cef/configure-allowed-ip-addresses?forum=ssdsgetstarted
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

JDeveloper 10.1.3 BPEL plugin - can NOT connect to BPEL PM server

I can use the JDeveloper BPEL Designer 10.1.2.1.0 to create a simpel BPEL Process that I deploy to the BPELM PM with the following WSDL:
http://kmandrup-dk:9700/orabpel/default/BPELProcess1/1.0/BPELProcess1?wsdl
I can then use JDeveloper 10.1.3 to hook up to this WSDL
I would however prefer to use the BPEL plugin from within JDev 10.1.3 to create the BPEL process and deploy it directly. However I can't figure out how to establish a connection to the BPEL PM. Should I instead install a UDDI registry in my application server and then register the web service there? Seems like a "twisted" workaround!
In JDev 10.1.2 connections view, there is a node called BPEL Process Manager Server where one can create connections to BPELM PMSs
In Jdev 10.1.3 there is an App Server node and an Integration Server node, but the Integration Server node seems only able to refer to the App Server connections.
How does one achieve a direct BPEL PM Server connection in 10.1.3 similar to the effect of 10.1.2.
When I create a new BPEL Process Project I get an error, That the WSDL for the service created is not valid, due to being unable to acces a BPEL PMS :( What to do?
It also complains that it is unable to create the test suites :(
Is something missing in my BPEL plugin install perhaps???
Thanx in advance for any help!

Does the 10.1.3 J-Developer have the BPEL plugin in it? I didn't think this was avail. Unless you are on a beta version, I would bet you don't have the full deal like you think.

Client-cert auth impl in web.xml does not work in Oracle Application Server

Hi,
I am new to implementing security features on the web applications.. I have developed a new web service using jdev1012 and deployed in OAS 10.1.2. Its working fine according to the business requirements, but I am in need of implementing client-cert authentication to enable the web service available to only those who have client certificate.
My server details are:
Oracle Application Server 10g Release 2 (10.1.2)
Server certificate is in place and SSL mode have been already enabled.. able to access my web service through https://<mydomain.com>/myws/TreqWS as well able to see the WSDL file through https://<mydomain.com>/myws/TreqWS?WSDL.
I tried to include the following in my web.xml file as part of implementing CLIENT-CERT authentication.
<security-constraint>
<display-name>SecurityConstraint</display-name>
<web-resource-collection>
<web-resource-name>WSCollection</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>CLIENT-CERT</auth-method>
<realm-name>WSCollection</realm-name> 
</login-config>
It is not woking as expected, though I have restarted my oc4j container after including this content to the web.xml file. i.e, I am able to invoke the web service though my sample java client program, though I donot have client certificate/keystore.
I believe I am missing something..Can anyone help me in this regard to implement CLIENT-CERT authentication successfully?
Thanks,
Ms

I am having the same problem with doc and xsl. I have added this
<mime-mapping>
<extension>xls</extension>
<mime-type>application/vnd.ms-excel</mime-type>
</mime-mapping>
<mime-mapping>
<extension>doc</extension>
<mime-type>application/msword</mime-type>
</mime-mapping>
to my web.xml. I even restarted the server. I still see doc and xsl in binary.
Is there some other setting that needs to take place?
I am using WL6.1 with fixpack 1.
I can see the doc and excel files in the browser if I don't go through the weblogic
server. That just confirms it's not my browser.
Kumar Allamraju <[email protected]> wrote:
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
It works fine for me in 6.1 SP1.
 
If the following doesn't work , can you
 try application/winword instead of application/msword?
--
 Kumar
Siming Mu wrote:
<blockquote TYPE=CITE>Hi,
I setup in my web.xml a mime mapping as follows,
<mime-mapping>
 <extension>doc</extension><mime-type>application/msword</mime-type>
 </mime-mapping>
When I specify a test.doc url, the doc file appears in my browser
as
binary data
 instead of download.
Please reference change request 055002, which decribes this problem.
According
 to edocs, it has been fixed in wls6.1sp1.
But I am seeing it fixed. Am I doing anything wrong? Thanks.
Siming</blockquote>
</html>

File not getting Saved on Application Server

Hello All,
We created a file in "Automatic Payment Transactions (F110 Transaction)" and are able to save the text file on Local drive. But for our e-banking requirement we need to store this file on our application server. The configuration settings in OBPM4 are already done and now system is picking the default application server path while saving file in "Payment Medium - > DME Administration" transaction. The problem is - although the system is picking the required path of application server but file is not getting saved. The error coming is: File <path> could not be opened (Message Number: FZ231).
We have checked for 777 authorisations (OS authorisations) for the folder.
Please suggest that what can be done to resolve th issue.
Regards,

What exactly we need to check in Payment program? We are not able to save the file on application server. There is no problem while saving the same in local drive.
Regards,

Form is not submitting through Oracle Application Server

Hi Experts,
We are creating one Java Application and deploy this java application on Oracle Application Server Enterprise Manager release 2 through War File.
Now, There one Form on submitting calls procedure with some 42 parameter in that 20 are Oracle Types and remaining are simple varchar or number. when going to submit this form is not raise any database error or server error , but data is saved into database.
We creating error log on database side as well as on Server side but we did not found any error.
We are confused because remaining all form working fine as they call with same as procedure, only difference is that this form calls procedure which having 42 parameter with 20 Type and remaining simple varcahr or number. Other Forms procedure also having Oracle Types as a parameter.
Could any of one help me out, Please ?

The form HTML is incorrect.
<form id="form1" name="form1" method="post" action"registration.php">
you're missing a = after action

Webservice not created in oracle application server after deployment

Hi,
I just tried to deploy fulfillmentESB project(SOADemo Projects) from Jdev to Oracle App server control. But there was no webservice created in Oracle application server control under webservices link....plz help me...
Actually the steps which i had followed to deploy that fulfillment project are:
* right-click fulfillmentESB
* select Register with ESB, Integration connection
after which the fulfillment webservice can be seen in ESB control as well as application server control. But i could not able to see webservice created in application server control.
Also i tried deploying the fulfillmentESB using EAR file - no use
So kindly give me some steps to solve this issue...
-Indhu

I can see you also posted in the (proper) SOA Suite forum.
Please do not cross-post unless you really have to (for example when in the other forum no one seems to have the answer).
Jan Kettenis

Process Chain to do nothing if file does not exist in the application serve

Hi All,
We have a process chain that flows to different data targets daily if files delivered in the application server.
Process chain does works fine. But my question is do we have anyway to stop the process chain or do not run process chain if it does not find the file available any days during this time range instead of failing.*
Is there any settings to enable the check if file available then run or else do not run at all. Please help!!!
Thanks,

Follow the function modules listed in :
http://wiki.sdn.sap.com/wiki/display/ABAP/Workingwithfiles
with these function modules - you can get a list of files available in the application server directory.
Pseudo code :
1. Generate the automated fiel name you want
2. Get the list of files in the directory
3. Search the list of files to see if your file exists
4. If the file exists then load the file , else load an empty file .
The code is unfortunately in a different BW system that I do not have access to at this moment... but then the procedre is the same as detailed above.

Local user not allowed in OS X server

After installing OS X Server 3.03, I now notice when I am logged into the Mac Mini hosting the server, I am not allowed to log in as a local user. This change in user permissions completely defeats the reason for me to have the server running, namely the ability to log into the machine from within my home or outside via VPN. Why am I not allowed to log in on the local network and is there a way to change something so I can?

I'm not sure I understand what this means:
when I am logged into the Mac Mini hosting the server, I am not allowed to log in as a local user
Please clarify.

Standalone Installer Not allowing install of Remote Server Admin Tools

I am trying to download the Windows 10 Technical Preview Remote Server Administration Tools since I need a way to quickly access Active Directory for my company. However whenever I attempt to download the file WindowsTH-KB2693643-x64.msu I
get an this error message:
Windows Update Standalone Installer: The update is not applicable to your computer.
I do have a 64 bit OS as well as Windows 10 Technical Preview 9926 currently running. So I am not sure as to the reason that I am getting this error. Any tips or clues would greatly help and be appreciated.

Hi Magan P,
Do you have any update about this issue?
What’s the result when you download the latest RSAT tool?
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Jdeveloper 11.1.1.6.2 is "NOT" allowing to configure application server

Similar Messages

Maybe you are looking for