Error starting Admin Server in a OSB Cluster installation

Greetings
I have an environment with two osb nodes in cluster, when I start the Admin server the server start succesfully and the osb servers also works fine, but I got the following messages starting the admin server:
<Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: SFTP Transport Provider, EJBComponent: sftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.sftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
I am worried because I see in the deployment screen that the applications File Transport Provider, SFTP Transport Provider, Ftp Transport Provider and Email Transport Provider are not running.
How can I solve this issue?
My installation is osb 11.1.1.6 and my operating system is solaris 11 (64 bits)
Thanks!

Hi Charan,
if your ManagedServers are not in Configured for MSI Mode (Managed Server Indepence Mode) then you wont be able to start your Servers until the AdminServer is Already Running. I can see that the Exception u pasted that...your AdminServer is not reachable....It may be due to AdminServer Vs ManagedServer BOX Network Issue or Your AdminServer might be down when u tried to start the ManagedServer.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

Similar Messages

  • Error while starting Admin Server

    Hello Everyone,
    I am trying to start Admin server and getting this error:
    <Jan 6, 2012 12:08:11 PM> <INFO> <NodeManager> <Server output log file is 'E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\servers\AdminServer\logs\AdminServer.out'>
    <Jan 6, 2012 12:08:12 PM PST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Jan 6, 2012 12:08:12 PM PST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Jan 6, 2012 12:08:14 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 19.1-b02 from Sun Microsystems Inc.>
    <Jan 6, 2012 12:08:15 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
    <Jan 6, 2012 12:08:18 PM PST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\config\config.xml - Invalid xsi:type qname: 'ext:oam-servlet-authentication-filter-ia-providerType' in element realm@http://xmlns.oracle.com/weblogic/domain>
    <Jan 6, 2012 12:08:18 PM PST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\config\config.xml - E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\<unknown>:14:9: error: failed to load java type corresponding to t=oam-servlet-authentication-filter-ia-providerType@http://xmlns.oracle.com/weblogic/security/extension>
    <Jan 6, 2012 12:08:18 PM PST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\config\config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false>
    <Jan 6, 2012 12:08:18 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jan 6, 2012 12:08:18 PM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jan 6, 2012 12:08:18 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Jan 6, 2012 12:08:18 PM> <FINEST> <NodeManager> <Waiting for the process to die: 1648>
    <Jan 6, 2012 12:08:18 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jan 6, 2012 12:08:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Please suggest.
    Thanks,
    PS

    dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>jsf#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <module-type>war</module-type>
    <source-path>E:\App\Oracle\Middleware\wlserver_10.3/common/deployable-libraries/jsf-1.2.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>jstl#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <module-type>war</module-type>
    <source-path>E:\App\Oracle\Middleware\wlserver_10.3/common/deployable-libraries/jstl-1.2.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>UIX#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.uix_11.1.1/uix11.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>ohw-rcf#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.help_5.0/ohw-rcf.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>ohw-uix#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.help_5.0/ohw-uix.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.pwdgen#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.pwdgen_11.1.1/pwdgen.jar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.rules#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.rules_11.1.1/rules.jar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.webcenter.composer#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,oim_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/webcenter/modules/oracle.webcenter.framework_11.1.1/oracle.webcenter.composer.war</source-path>
    <deployment-order>300</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.webcenter.skin#[email protected]</name>
    <target>AdminServer,oim_server1</target>
    <module-type>ear</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/webcenter/modules/oracle.portlet.server_11.1.1/oracle.webcenter.skin.ear</source-path>
    <deployment-order>300</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.workflow.wc#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.workflow_11.1.1/oracle.soa.workflow.wc.jar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.idm.uishell#[email protected]</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,oaam_server_server1,oim_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_IDM1/modules/oracle.idm.uishell_11.1.1/oracle.idm.uishell.war</source-path>
    <deployment-order>300</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <library>
    <name>oracle.soa.rules_editor_dc.webapp#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.rules_editor_dc.webapp_11.1.1/oracle.soa.rules_editor_dc.webapp.war</source-path>
    <deployment-order>306</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.rules_dict_dc.webapp#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.rules_dict_dc.webapp_11.1.1/oracle.soa.rules_dict_dc.webapp.war</source-path>
    <deployment-order>306</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.bpm.mgmt#[email protected]</name>
    <target>AdminServer</target>
    <source-path>E:/App/Oracle/Middleware/oracle_common/bpm/modules/oracle.bpm.mgmt_11.1.1/oracle.bpm.bpmn-em-tools.jar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>emai</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emai.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.oaam.libs#[email protected]</name>
    <target>oam_server1</target>
    <module-type>ear</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_IDM1/oaam/oaam_libs/ear/oaam_native_lib.ear</source-path>
    <deployment-order>400</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <library>
    <name>oracle.security.apm.core.model#[email protected]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_IDM1/apm/modules/oracle.security.apm_11.1.1/oracle.security.apm.core.model.ear</source-path>
    <deployment-order>311</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <library>
    <name>oracle.security.apm.core.view#[email protected]</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_IDM1/apm/modules/oracle.security.apm_11.1.1/oracle.security.apm.core.view.war</source-path>
    <deployment-order>311</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <library>
    <name>oracle.sdp.messaging#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/communications/modules/oracle.sdp.messaging_11.1.1/sdpmessaging.jar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.sdp.client#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/communications/modules/oracle.sdp.client_11.1.1/sdpclient.jar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>emas</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emas.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>emcore</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emcore.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.bpel#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.bpel_11.1.1/oracle.soa.bpel.jar</source-path>
    <deployment-order>301</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.worklist#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.worklist_11.1.1/oracle.soa.worklist.jar</source-path>
    <deployment-order>302</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.workflow#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.workflow_11.1.1/oracle.soa.workflow.jar</source-path>
    <deployment-order>303</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.mediator#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.mediator_11.1.1/oracle.soa.mediator.jar</source-path>
    <deployment-order>304</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.composer.webapp#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.composer.webapp_11.1.1/oracle.soa.composer.webapp.war</source-path>
    <deployment-order>306</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.ext#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.ext_11.1.1/oracle.soa.ext.jar</source-path>
    <deployment-order>307</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.b2b#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar</source-path>
    <deployment-order>308</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.soa.worklist.webapp#[email protected]</name>
    <target>AdminServer,soa_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.worklist.webapp_11.1.1/oracle.soa.worklist.webapp.war</source-path>
    <deployment-order>309</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </library>
    <library>
    <name>oracle.oaam.extensions#[email protected]</name>
    <target>oaam_admin_server1,oaam_server_server1</target>
    <module-type>war</module-type>
    <source-path>E:/App/Oracle/Middleware/Oracle_IDM1/oaam/oaam_extensions/generic/oracle.oaam.extensions.war</source-path>
    <deployment-order>400</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <machine>
    <name>LocalMachine</name>
    <node-manager>
    <name>LocalMachine</name>
    <listen-address>localhost</listen-address>
    </node-manager>
    </machine>
    <jms-server>
    <name>UMSJMSServer</name>
    <target>soa_server1</target>
    <persistent-store>UMSJMSFileStore</persistent-store>
    </jms-server>
    <jms-server>
    <name>SOAJMSServer</name>
    <target>soa_server1</target>
    <persistent-store>SOAJMSFileStore</persistent-store>
    </jms-server>
    <jms-server>
    <name>OIMJMSServer</name>
    <target>oim_server1</target>
    <persistent-store>OIMJMSFileStore</persistent-store>
    <temporary-template-resource xsi:nil="true"></temporary-template-resource>
    <temporary-template-name xsi:nil="true"></temporary-template-name>
    </jms-server>
    <self-tuning>
    <max-threads-constraint>
    <name>MaxThreadsConstraint-0</name>
    <target>oim_server1</target>
    <count>20</count>
    </max-threads-constraint>
    <max-threads-constraint>
    <name>MaxThreadsConstraint-1</name>
    <target>oim_server1</target>
    <count>80</count>
    </max-threads-constraint>
    <work-manager>
    <name>wm/SOAWorkManager</name>
    <target>soa_server1</target>
    </work-manager>
    <work-manager>
    <name>OIMUIWorkManager</name>
    <target>oim_server1</target>
    <max-threads-constraint>MaxThreadsConstraint-0</max-threads-constraint>
    </work-manager>
    <work-manager>
    <name>OIMMDBWorkManager</name>
    <target>oim_server1</target>
    <max-threads-constraint>MaxThreadsConstraint-1</max-threads-constraint>
    </work-manager>
    </self-tuning>
    <shutdown-class>
    <name>JOC-Shutdown</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.ias.cache.Shutdown</class-name>
    </shutdown-class>
    <shutdown-class>
    <name>DMSShutdown</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.dms.wls.DMSShutdown</class-name>
    </shutdown-class>
    <startup-class>
    <name>JRF Startup Class</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>110</deployment-order>
    <class-name>oracle.jrf.wls.JRFStartup</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <startup-class>
    <name>JPS Startup Class</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>115</deployment-order>
    <class-name>oracle.security.jps.wls.JpsWlsStartupClass</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <startup-class>
    <name>ODL-Startup</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>145</deployment-order>
    <class-name>oracle.core.ojdl.weblogic.ODLConfiguration</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <startup-class>
    <name>Audit Loader Startup Class</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.security.audit.ajl.loader.JEEAuditLoader</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>false</load-before-app-deployments>
    </startup-class>
    <startup-class>
    <name>AWT Application Context Startup Class</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.jrf.AppContextStartup</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <startup-class>
    <name>JMX Framework Startup Class</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.as.jmx.framework.wls.spi.StartupListener</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <startup-class>
    <name>JOC-Startup</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.ias.cache.Startup</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <startup-class>
    <name>DMS-Startup</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.dms.wls.DMSStartup</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <startup-class>
    <name>OWSM Startup class</name>
    <notes>This class will seed the OWSM data in repository</notes>
    <target>soa_server1,oaam_server_server1,oim_server1</target>
    <deployment-order>150</deployment-order>
    <class-name>oracle.wsm.policymanager.util.PolicyManagerStartup</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    </startup-class>
    <startup-class>
    <name>SOAStartupClass</name>
    <target>soa_server1</target>
    <deployment-order>1000</deployment-order>
    <class-name>oracle.bpel.services.common.util.GenerateBPMCryptoKey</class-name>
    <failure-is-fatal>false</failure-is-fatal>
    <load-before-app-deployments>true</load-before-app-deployments>
    <load-before-app-activation>true</load-before-app-activation>
    </startup-class>
    <file-store>
    <name>UMSJMSFileStore</name>
    <directory>UMSJMSFileStore</directory>
    <target>soa_server1</target>
    </file-store>
    <file-store>
    <name>SOAJMSFileStore</name>
    <directory>SOAJMSFileStore</directory>
    <target>soa_server1</target>
    </file-store>
    <file-store>
    <name>OIMJMSFileStore</name>
    <directory>OIMJMSFileStore</directory>
    <target>oim_server1</target>
    </file-store>
    <jms-system-resource>
    <name>UMSJMSSystemResource</name>
    <target>soa_server1</target>
    <sub-deployment>
    <name>UMSJMSSubDeployment</name>
    <target>UMSJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/UMSJMSSystemResource-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>SOAJMSModule</name>
    <target>soa_server1</target>
    <sub-deployment>
    <name>SOASubDeployment</name>
    <target>SOAJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/soajmsmodule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>OIMJMSModule</name>
    <target>oim_server1</target>
    <sub-deployment>
    <name>OIMSubDeployment</name>
    <target>OIMJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/OIMJMSModule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <wldf-system-resource>
    <name>Module-FMWDFW</name>
    <target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
    <descriptor-file-name>diagnostics/Module-FMWDFW-2818.xml</descriptor-file-name>
    <description>Creates FMWDFW incidents based on unchecked Exceptions and critical errors</description>
    </wldf-system-resource>
    <jdbc-system-resource>
    <name>mds-owsm</name>
    <target>AdminServer,soa_server1,oaam_server_server1,oim_server1</target>
    <descriptor-file-name>jdbc/mds-owsm-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>oamDS</name>
    <target>AdminServer,oam_server1</target>
    <descriptor-file-name>jdbc/oam-db-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>OraSDPMDataSource</name>
    <target>soa_server1</target>
    <descriptor-file-name>jdbc/OraSDPMDataSource-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>mds-ApplicationMDSDB</name>
    <target>AdminServer</target>
    <descriptor-file-name>jdbc/apm-server-mds-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>apm-DBDS</name>
    <target>AdminServer</target>
    <descriptor-file-name>jdbc/apm-server-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>OAAM_ADMIN_DS</name>
    <target>oaam_admin_server1</target>
    <descriptor-file-name>jdbc/OAAM_ADMIN_DS-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>mds-oaam</name>
    <target>AdminServer,oaam_admin_server1</target>
    <descriptor-file-name>jdbc/OAAM_ADMIN_MDS_DS-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>SOADataSource</name>
    <target>soa_server1</target>
    <descriptor-file-name>jdbc/SOADataSource-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>EDNDataSource</name>
    <target>soa_server1</target>
    <descriptor-file-name>jdbc/EDNDataSource-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>EDNLocalTxDataSource</name>
    <target>soa_server1</target>
    <descriptor-file-name>jdbc/EDNLocalTxDataSource-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>SOALocalTxDataSource</name>
    <target>soa_server1</target>
    <descriptor-file-name>jdbc/SOALocalTxDataSource-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>mds-soa</name>
    <target>AdminServer,soa_server1</target>
    <descriptor-file-name>jdbc/mds-soa-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>OAAM_SERVER_DS</name>
    <target>oaam_server_server1</target>
    <descriptor-file-name>jdbc/OAAM_SERVER_DS-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>oimOperationsDB</name>
    <target>soa_server1,oim_server1</target>
    <descriptor-file-name>jdbc/oimOperationsDB-0237-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>mds-oim</name>
    <target>oim_server1</target>
    <descriptor-file-name>jdbc/oimMDS-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>oimJMSStoreDS</name>
    <target>oim_server1</target>
    <descriptor-file-name>jdbc/oimJMSStoreDS-0269-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    </domain>

  • Unable to Start Admin server Java Lang NoClassFound Exception Error

    Hello,
              I am getting java lang NoClassFoundException error while starting the admin server. Its a new installation, i am trying to start from domain_home\bin\Startweblogic.cmd
    Please let me know if you have any solution on that. I am using 11.1.1.6.
    Regards,
    Vivek

    Hello Vivek
    Could you provided us the full stack of the NoClassFound error in order to know which class is missed.
    And also:
    Please let me know if you have any solution on that. I am using 11.1.1.6.
    of which product ?? Forms Reports Services, SOA, UCM etc
    What it's you Windows version, architecture, java version ??
    Do you have other Oracle product installed in that computer ??
    Regards
    Carlos

  • Errors while starting admin server using WLST and NodeManager

    Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
    thanks
    manohar
    C:\oracle\Middleware\wlserver_10.3\server\bin>
    C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
    Connecting to Node Manager ...
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
    loading of the trusted certificate list raised a certificate parsing exception
    PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
    \,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
    arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
    0.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
    of the trusted certificate list raised a certificate parsing exception PKIX: Un
    supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 123, in nmConnect
    File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing nmConnect : Cannot connect to Node
    Manager. : I/O error while reading domain directory
    Use dumpStack() to view the full stacktrace
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline> dumpStack()
    This Exception occurred at Tue May 03 10:45:03 EDT 2011.
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:299)
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:312)
    at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
    a:248)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:199)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:205)
    at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
    java:52)
    at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
    eManagerService.java:179)
    at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
    rService.java:173)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyObject.invoke(Unknown Source)
    at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
    at org.python.pycode._pyx2.call_function(<iostream>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.pycode._pyx16.f$0(<console>:1)
    at org.python.pycode._pyx16.call_function(<console>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.core.Py.exec(Unknown Source)
    at org.python.util.PythonInterpreter.exec(Unknown Source)
    at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.WLST.main(WLST.java:29)
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    wls:/offline>
    wls:/offline>

    Hi manohar,
    Please try the following article... (With Node Manager Communication type as "Plain" because it looks like you are getting PKIX security certificate chain message ) Just to isolate the issue
    Topic: Start AdminServer And NodeManager Using WLST
    http://middlewaremagic.com/weblogic/?p=6580
    Thanks
    Ravish Mody

  • Failed to start  "admin server" and "BI publisher" :  Reason java.io.IOException openWallet

    Hello,
    I need your help to fix a critical problem to start Admin server and BI server :
    # ...domains/bifoundation_domain/bin/startWebLogic.sh ....
    Failed with
    17-Mar-2015 17:17:33 oracle.security.jps.internal.credstore.ssp.CsfWalletManager openWallet
    WARNING: Opening of wallet based credential store failed. Reason java.io.IOException
    Best Regards
    Djams
    More détails  in ...  /logs/AdminServer.log :
    ####<17-Mar-2015 17:14:16 o'clock CET> <Notice> <Log Management> <srver3.domaine.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (sel
    f-tuning)'> <> <> <> <1426608856985> <BEA-170019> <The server log file /servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminSe
    rver.log is opened. All server side log events will be written to this file.>
    ####<17-Mar-2015 17:14:16 o'clock CET> <Info> <Log Management> <srver3.domaine.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-
    tuning)'> <> <> <> <1426608856998> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Diagnostics> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
    t (self-tuning)'> <<WLS Kernel>> <> <> <1426608857142> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857307> <BEA-002622> <The protocol "t3" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857308> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857309> <BEA-002622> <The protocol "http" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857309> <BEA-002622> <The protocol "https" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857311> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857313> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857314> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857316> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857323> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857324> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857333> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857333> <BEA-002622> <The protocol "admin" is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1426608857334> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <RJVM> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self
    -tuning)'> <<WLS Kernel>> <> <> <1426608857380> <BEA-000570> <Network Configuration for Channel "AdminServer"
    Listen Address          :7001
    Public Address          N/A
    Http Enabled            true
    Tunneling Enabled       false
    Outbound Enabled        false
    Admin Traffic Enabled   true>
    #####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857449> <BEA-002609> <Channel Service initialized.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857487> <BEA-000415> <System has file descriptor limits of - soft: 4,096, hard: 4,096>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857488> <BEA-000416> <Using effective file descriptor limit of: 4,096 open sockets/files.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857489> <BEA-000406> <PosixSocketMuxer was built on Apr 24 2007 16:05:00>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857518> <BEA-000436> <Allocating 4 reader threads.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857521> <BEA-000446> <Native IO Enabled.>
    ####<17-Mar-2015 17:14:17 o'clock CET> <Info> <IIOP> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857866> <BEA-002014> <IIOP subsystem enabled.>
    ####<17-Mar-2015 17:14:22 o'clock CET> <Error> <Security> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608862432> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException>
    ####<17-Mar-2015 17:14:22 o'clock CET> <Critical> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862434> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: oracle.security.jps.JpsRuntimeException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
            at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:170)
            at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
            at java.lang.Class.newInstance0(Class.java:355)
            at java.lang.Class.newInstance(Class.java:308)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: oracle.security.jps.JpsException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
    Caused By: oracle.security.jps.JpsException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
            at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2984)
            at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
            at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
            at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
            at java.lang.Class.newInstance0(Class.java:355)
            at java.lang.Class.newInstance(Class.java:308)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
            at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:184)
            at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:358)
            at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:176)
            at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:160)
            at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:118)
            at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:56)
            at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
            at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
            at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
            at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
            at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
            at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2956)
            at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2950)
            at java.security.AccessController.doPrivileged(Native Method)
            at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2950)
            at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
            at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
            at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
            at java.lang.Class.newInstance0(Class.java:355)
            at java.lang.Class.newInstance(Class.java:308)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<17-Mar-2015 17:14:22 o'clock CET> <Notice> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862461> <BEA-000365> <Server state changed to FAILED>
    ####<17-Mar-2015 17:14:22 o'clock CET> <Error> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862461> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<17-Mar-2015 17:14:22 o'clock CET> <Notice> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862462> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<17-Mar-2015 17:14:22 o'clock CET> <Info> <WebLo

    Hello Djam,
    Please review the following:
    The FMW WebLogic Server (WLS) installation has been configured to use a non-default Java temporary files directory,
    i.e. the following has been set in the WebLogic startup or setDomainEnv.sh script:
    EXTRA_JAVA_PROPERTIES="-Djava.io.tmpdir=/appl/oracle/temp_java_files ${EXTRA_JAVA_PROPERTIES}"
    Reference: How to Change the WebLogic Server Location for Temporary Files (Doc ID 1336002.1)
    When the Middleware home was restored the directory specified by java.io.tmpdir parameter was missing,
    Therefore an IOException occurred when opening the wallet and WLS was unable to initialize the OPSS successfully.
    To resolve the issue re-create the directory specified by the java.io.tmp dir parameter, and make sure the owner and group access are the same as for the FMW installation.
    Unable Start AdminServer: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException (Doc ID 1923395.1)
    Bogdan

  • Urgent: Can not start admin server

    I installed Sun One directory server 5.1 on Solaris 8 01/01 version patched with Solaris 8 patch cluster.
    In installation, there is error message
    Can't start Admin server [home/iplanet/servers/start-admin > /var/tmp/aaax0aOBb 2>&1] (error: No such file or directory)
    idskture only shows one ERROR message:
    ERROR : Patch 111085-02 (SunOS 5.8: /usr/bin/login patch) is required but not installed.
    But it seems fine since I reinstalled Solaris 8 01/01 release and install 5.1sp2 and with the same error message running idsktune, the installation of 5.1 but works fine.
    Do you have any idea why the installation fail before I reinstlall Solaris 8?
    Thanks,
    Iris

    Have you checked the EAS logs, <MIDDLEWARE_HOME>user_projects\epmsystem1\diagnostics\logs\services
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Unable to start admin server service for weblogic (startWebLogic.sh) Linux

    I installed ECM 11g on Linux 64-bit , installed weblogic 12
    so when I try to start admin server service for weblogic (startWebLogic.sh) and following error its showing
    I found solution to give full access permeation for the user , but it's still same issue
    and i am triyng to start services from the users how installed the Weblogic and ECM
    bash-4.1$ '/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/startWebLogic.sh' .
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
    WLS Start Mode=Development
    CLASSPATH=/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/home/ecm/Oracle/Middleware/patch_wls1211/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/ecm/Oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/lib/jvm/jdk1.6.0_33/lib/tools.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/weblogic_sp.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/weblogic.jar:/home/ecm/Oracle/Middleware/modules/features/weblogic.server.modules_12.1.1.0.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/webservices.jar:/home/ecm/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/ecm/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/ecm/Oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/home/ecm/Oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/common/derby/lib/derbyclient.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/xqrl.jar:/home/ecm/Oracle/Middleware/Oracle_ECM1/ucm/idc/jlib/idcloader.jar:/home/ecm/Oracle/Middleware/Oracle_ECM1/ucm/idc/components/NativeOsUtils/classes-NativeOsUtils.jar
    PATH=/home/ecm/Oracle/Middleware/wlserver_12.1/server/bin:/home/ecm/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/usr/lib/jvm/jdk1.6.0_33/jre/bin:/usr/lib/jvm/jdk1.6.0_33/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/ecm/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_33"
    Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
    Starting WLS with line:
    /usr/lib/jvm/jdk1.6.0_33/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/weblogic.policy -Xverify:none -Djava.endorsed.dirs=/usr/lib/jvm/jdk1.6.0_33/jre/lib/endorsed:/home/ecm/Oracle/Middleware/wlserver_12.1/endorsed -da -Dplatform.home=/home/ecm/Oracle/Middleware/wlserver_12.1 -Dwls.home=/home/ecm/Oracle/Middleware/wlserver_12.1/server -Dweblogic.home=/home/ecm/Oracle/Middleware/wlserver_12.1/server -Dcommon.components.home=/home/ecm/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain -Djrockit.optfile=/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/carml -Digf.arisidstack.home=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dipm.oracle.home=/home/ecm/Oracle/Middleware/Oracle_ECM1 -Ducm.oracle.home=/home/ecm/Oracle/Middleware/Oracle_ECM1 -Dem.oracle.home=/home/ecm/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/ecm/Oracle/Middleware/patch_wls1211/profiles/default/sysext_manifest_classpath:/home/ecm/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server
    <Sep 12, 2012 12:08:02 PM EEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Sep 12, 2012 12:08:03 PM EEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Sep 12, 2012 12:08:03 PM EEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.8-b03 from Sun Microsystems Inc..>
    <Sep 12, 2012 12:08:04 PM EEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 13340309 Thu Feb 16 18:30:21 IST 2012
    WebLogic Server Temporary Patch for 13019800 Mon Jan 16 16:53:54 IST 2012
    WebLogic Server Temporary Patch for BUG13391585 Thu Feb 02 10:18:36 IST 2012
    WebLogic Server Temporary Patch for 13516712 Mon Jan 30 15:09:33 IST 2012
    WebLogic Server Temporary Patch for BUG13641115 Tue Jan 31 11:19:13 IST 2012
    WebLogic Server Temporary Patch for BUG13603813 Wed Feb 15 19:34:13 IST 2012
    WebLogic Server Temporary Patch for 13424251 Mon Jan 30 14:32:34 IST 2012
    WebLogic Server Temporary Patch for 13361720 Mon Jan 30 15:24:05 IST 2012
    WebLogic Server Temporary Patch for BUG13421471 Wed Feb 01 11:24:18 IST 2012
    WebLogic Server Temporary Patch for BUG13657792 Thu Feb 23 12:57:33 IST 2012
    WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491 >
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
    <Sep 12, 2012 12:08:06 PM EEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.>
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log00009. Log messages will continue to be logged in /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log.>
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <Log Management> <BEA-170019> <The server log file /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    Sep 12, 2012 12:08:09 PM oracle.security.jps.internal.keystore.file.FileKeyStoreManager openKeyStore
    WARNING: Opening of file based keystore failed.
    <Sep 12, 2012 12:08:09 PM EEST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.>
    <Sep 12, 2012 12:08:09 PM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:148)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsRuntimeException: JPS-06514: Opening of file based keystore failed.
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsException: JPS-06514: Opening of file based keystore failed.
         at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2855)
         at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3097)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:164)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06514: Opening of file based keystore failed.
         at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKeyStore(FileKeyStoreManager.java:374)
         at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:104)
         at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:76)
         at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:66)
         at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)
         Truncated. see log file for complete stacktrace
    >
    <Sep 12, 2012 12:08:09 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
    <Sep 12, 2012 12:08:09 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
    <Sep 12, 2012 12:08:09 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
    bash-4.1$

    Looks to be a cert or keystore issue. How do you have that setup?

  • Unable to start Admin server after WLS 10.3.3 to 10.3.4 upgrade

    I am getting class path errors while starting Admin server in linux via startWeblogic.sh start script after upgrading from 10.3.3 to 10.3.4. Here is the error log:
    <Jun 7, 2011 2:03:46 PM EDT> <Critical> <WebLogicServer> <tloia105.goaa.org> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1307469826197> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
    java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:262)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:246)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppDeployments(ClassDeploymentManager.java:149)
    at weblogic.management.deploy.classdeployment.ClassDeploymentService.start(ClassDeploymentService.java:21)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    >
    ####<Jun 7, 2011 2:03:46 PM EDT> <Critical> <WebLogicServer> <tloia105.goaa.org> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1307469826211> <BEA-000286> <Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
    java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:262)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:246)
    at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppDeployments(ClassDeploymentManager.java:149)
    at weblogic.management.deploy.classdeployment.ClassDeploymentService.start(ClassDeploymentService.java:21)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    >
    ####<Jun 7, 2011 2:03:46 PM EDT> <Critical> <WebLogicServer> <tloia105.goaa.org> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1307469826214> <BEA-000286> <Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
    java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.net.URLClassLoader.findClass(URLClassLoader.java
    Please suggest if I am missing some class path setting here .
    Regards,
    Deepak

    Guys,
    It seems that the start scripts replaced while upgrading the domain did not have right class paths as the previous start scripts had which were created while creating the domain originally. Copying the necessary Class paths makes the new start scripts to work fine.
    Deepak
    AST Corp.

  • Unable to start Admin server by using weblogic.admin utility

    Hi,
    I stoped the admin server by using weblogic.admin utility command as bellow.
    java weblogic.Admin -url http://server1:8008 -username adminuser -password weblogic SHUTDOWN myserver
    It stopped successfully. But while starting as below i am getting error. Kindly help me out.
    java weblogic.Admin -url http://172.27.72.70:8008 -username adminuser -password weblogic START myserver
    <Warning> <Net> <BEA-000905> <Could not open connection with host: server1 and port: 8008.>
    Failed to connect to http://172.27.72.70:8008: Destination unreachable; nested exception is:
    java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'star', port: '8008'; No available router to destination
    Any suggestion is appreciated.
    Thanks,

    Hi,
    Thanks for your reply.
    Yes, Node Manager has configured on Managed Server's host machine.
    So can't we start admin server by using weblogic.admin utility if admin server is stopped?
    Thanks,

  • Errors Starting Managed Server

              Hai all!
              I Have 1 Admin server A and One Managed Server M.
              1)I Started Admin server A.
              2)It starts fine promitng Clustering services are started
              3)Now i starts Managed Server M.
              4)When starting M it gives error Application defaultwebAppA cannot be deployed
              into server M.
              5)At the same time in console of Admin A error message prints out reading Unable
              to deploy defaultWebAppB into Server A.
              What may be the problem?
              Can u Pls drive out of the problem?
              TIA
              Rgds
              Manohar
              

    [att1.html]
              

  • Failed to start Admin Server for Weblogic Server Domain

    I Created a domain named mydomain in weblogic server 10.3 in server 2003.But when i start Admin Server for Weblogic Server Domain from startmenu, it failed.
    I examined the log under domains\mydomain\servers\AdminServer\logs\AdminServer.log and got the following information:
    java.lang.NoClassDefFoundError:weblogic/ldap/EmbeddedLDAPChange
    at weblogic.ldap.EntryChangeListenerImpl.receiveEntryChanges(EntryChangeListenerImpl.java:28)
    Caused by :java.lang.ClassNotFoundException: weblogic.ldap.EmbeddedLDAPChange
    at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
    Caused by :java.util.zip.ZipException: error reading zip file
    at java.util.zip.ZipFile.read(Native Method)
    at java.util.zip.ZipFile.access$1200(ZipFile.java:29)
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
    at ...(CommonSecurityServiceManagerDelegateImpl.java:465)
    Caused by: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
    at .. (ServiceEngineImpl.java:365)
    Caused by: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
    at .. (BootStrapServiceImpl.java:910)
    Caused by: <openjpa-1.1.1-SNAPSHOT-r422266:891341 nofatal user error>kodo.jdo.UserException: This operation cannot be perfomed while a Transaction is active.
    at org.apache.openjpa.kernel.BrokerImpl.close(BrokerImpl.java:4087)
    ####<Critical><WebLogicServer><SOA><Adminserver><main><<WLS Kernel>><><><1282012271468><BEA-000362><Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399] Security Services Unavailable
    at weblogic.security.service.CommonSecurityserviceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
    I ignored some detailed error message.The runtime environment is server 2003 Enterprise Edition sp2.
    Thx in advance for any reply.

    Hello Djam,
    Please review the following:
    The FMW WebLogic Server (WLS) installation has been configured to use a non-default Java temporary files directory,
    i.e. the following has been set in the WebLogic startup or setDomainEnv.sh script:
    EXTRA_JAVA_PROPERTIES="-Djava.io.tmpdir=/appl/oracle/temp_java_files ${EXTRA_JAVA_PROPERTIES}"
    Reference: How to Change the WebLogic Server Location for Temporary Files (Doc ID 1336002.1)
    When the Middleware home was restored the directory specified by java.io.tmpdir parameter was missing,
    Therefore an IOException occurred when opening the wallet and WLS was unable to initialize the OPSS successfully.
    To resolve the issue re-create the directory specified by the java.io.tmp dir parameter, and make sure the owner and group access are the same as for the FMW installation.
    Unable Start AdminServer: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException (Doc ID 1923395.1)
    Bogdan

  • Starting admin server using WLST and NodeManager

    Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
    thanks
    manohar
    C:\oracle\Middleware\wlserver_10.3\server\bin>
    C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
    Connecting to Node Manager ...
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
    loading of the trusted certificate list raised a certificate parsing exception
    PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
    \,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
    arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
    0.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
    of the trusted certificate list raised a certificate parsing exception PKIX: Un
    supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 123, in nmConnect
    File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing nmConnect : Cannot connect to Node
    Manager. : I/O error while reading domain directory
    Use dumpStack() to view the full stacktrace
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline> dumpStack()
    This Exception occurred at Tue May 03 10:45:03 EDT 2011.
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:299)
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:312)
    at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
    a:248)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:199)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:205)
    at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
    java:52)
    at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
    eManagerService.java:179)
    at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
    rService.java:173)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyObject.invoke(Unknown Source)
    at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
    at org.python.pycode._pyx2.call_function(<iostream>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.pycode._pyx16.f$0(<console>:1)
    at org.python.pycode._pyx16.call_function(<console>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.core.Py.exec(Unknown Source)
    at org.python.util.PythonInterpreter.exec(Unknown Source)
    at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.WLST.main(WLST.java:29)
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    wls:/offline>
    wls:/offline>

    Hi manohar,
    Thank you, Pierluigi for encouraging Middleware Magic Team :)
    manohar, apart from what *"Pierluigi"* has suggested, additionally please notice the following messsage in your StackTrace (whih is basically a NOTICE message but does not look good)
    The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object:In your case it looks like the actual issue is your Certificate which comes by default with JDK. As mentioned in this BUG.
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6803022
    Additionally please refer to the following Thread:
    http://forums.oracle.com/forums/message.jspa?messageID=3958098#3958098
    I am suspecting that you need to do the following in order to get rid of Certificate Errors which is the ROOT cause of your issue
    Do the following: After taking a backup of *"$JAVA_HOME/jre/lib/security/cacerts"* file
    cd $JAVA_HOME/jre/lib/security
    cp -p cacerts cacerts.original
    chmod 644 cacerts
    keytool -delete -alias ttelesecglobalrootclass2ca -keystore cacerts
    keytool -delete -alias ttelesecglobalrootclass3ca -keystore cacertsAlso try with Node Manager Communication type as "*Plain*" because it looks like you are getting PKIX security certificate chain message, just to isolate the issue.
    Regards,
    Ravish Mody

  • Weblogic starting admin server automatically

    Hello,
    I have deployed a weblogic server on one of my company servers and i do not want to start and stop the admin server everytime i log in. Also, I have adf libraires installed along with the weblogic server. I created a windows service by running the installSvc.cmd file located at => C:\oracle\Middleware\wlserver_10.3\server\bin . Before running the installSvc.cmd command i edited the file by adding the following lines =>
    set DOMAIN_NAME=base_domain
    set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\base_domain
    set SERVER_NAME=AdminServer
    set WLS_USER=weblogic
    set WLS_PW=welcome1
    set PRODUCTION_MODE=true
    After i install this service i go to servoces and start this service.
    Now the issue i run into is that when i go to the admin console i see some of the adf libraries STATUS as "failed" and even when i deploy an adf app the status is failed. This doesnt hapen when i start the admin server from the gui mode by going to Start > user projects > base domain > start admin server or by starting the server from the command line with the command startWeblogic.cmd . How do i create a service so that i dont hv to start the server everytime when i log in to my server(box) which has the weblogic server .
    I am in a tight deadline and any help will be greatly appreciated!

    What errors are the libraries getting?
    Is the classpath the same between the service case and the start from menu case? Look at the server stdout or at the logs and the classpath system property?

  • Location of "Start Admin Server"

    Hi,
    I am new to the world of Application Servers etc.
    I have minimal knowledge of Java but am conversant in C++ and OO stuff.
    Today, i installed "Sun Java� System Application Server Platform Edition 8.1 2005Q1" on a Windows 200 (x86) machine.
    I then launched "Quick Start Guide " with the intention of getting the things running so that i can learn things fast -
    Under the section, "Starting the Admin Server " it is written that "From the Start menu, choose Programs -> Sun Microsystems -> Application Server PE-> Start Admin Server. " ---BUT I donot find "Start Admin Server", menu item under "Application Server PE" - where am I wrong here- did my installation was not correct.
    Also, if I click on the "Start Default Server", i get the following error:
    The domain (domain1) is already running.
    CLI156 Could not start the domain domain1.
    Press any key to continue . . .
    I am getting a feeling that, i didnot put the proper port numbers during installation.
    It will be nice if someone can guide me through this and get atleast the basics running on my machine.
    I also feel, my language above is very child-like - Umm, cannot help, i am new to the world of JAVA.
    I can also be contacted at [email protected]
    TIA...
    Regards,
    amol

    Thanks for the update.
    From thefile "C:\Sun\AppServer\domains\domain1\config\domain.xml" i was able to make out that the domain1 was listening at port number 1813 and not 8080.
    A snippet from the domain.xml is below:
    <http-service>
    <http-listener acceptor-threads="50" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-1" port="1813" security-enabled="false" server-name="" xpowered-by="true">
    </http-listener>
    <http-listener acceptor-threads="50" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="8181" security-enabled="true" server-name="" xpowered-by="true">
    </http-listener>
    <http-listener acceptor-threads="50" address="0.0.0.0" blocking-enabled="false" default-virtual-server="__asadmin" enabled="true" family="inet" id="admin-listener" port="4848" security-enabled="false" server-name="" xpowered-by="true">
    </http-listener>
    Now, after starting the server when i key-in http://localhost:1813 on web-browser then it displays the same page as is written in the "Quick start guide" for http://localhost:8080
    I am yet to proceed further i.e. i will now deploy "Hello" world" web app. Hope things work smoothly here onwards.
    Thanks for all the information with this regards.
    Best Wishes,
    Amol

  • OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin Server

    Hi,
    We are working on BPC 7.0NW. Recently we encountered the below error while we login to BPC for Admin. Earlier it was working fine. We didnt do any major configuration or changes to the system. Not sure why we are getting this error suddenly. Please suggest how we can resolve this error.
    Error popup- 'OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin Server'
    thanks/regards,
    Lokesh Nandula

    Hi Lokesh,
    Please try out the following option. Not sure whether it will work or not.
    Go to Server manager on the app box.
    delete the encryption key. (backup first if you like)
    re-create the encryption key
    register msolap90.dll on both servers
    I don't have the text for this handy. I think it's: regsvr32 "C:\xxx\xxx\xxxx\xxx\msolap90.dll"
    Note: you must use the quotes!
    reboot the DB box
    reboot the App box
    or
    To register the DLL Follow the below steps:
    1) From the Application server go to the run option in the start menu and enter the below command
    2) regsvr32 "c:\program files\common files\system\ole db\msolap90.dll"
    3) Hit Enter
    4) You should get a confirmation that the Dll was registered
    Hope this helps.

Maybe you are looking for