Weblogic could not started

Hi Gurus,
We are having a problem in starting the weblogic server after modifications done in the Admin tool (we gave privileges to Subject Areas to certain users). We also created new application roles in EM and give these roles privileges to access the dashboard.
When we tried to restart adminserver and bi components, the following errors were thrown:
*<Oct 5, 2011 11:14:03 AM PHT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Oct 5, 2011 11:14:03 AM PHT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Oct 5, 2011 11:14:04 AM PHT> <Notice> <LoggingService> <BEA-320400> <The log file /home/apps11g/Oracle/Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Oct 5, 2011 11:14:04 AM PHT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/apps11g/Oracle/Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer.log06063. Log messages will continue to be logged in /home/apps11g/Oracle/Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer.log.>
<Oct 5, 2011 11:14:04 AM PHT> <Warning> <oracle.as.jmx.framework.MessageLocalizationHelper> <J2EE JMX-46041> <The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.>
<Oct 5, 2011 11:14:12 AM PHT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
<Oct 5, 2011 11:14:16 AM PHT> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.rules, referenced from: /home/apps11g/Oracle/Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/tmp/_WL_user/emai/xalnv4]. Make sure the referenced optional package has been deployed as a library.>
<Oct 5, 2011 11:14:18 AM PHT> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
<Oct 5, 2011 11:14:26 AM PHT> <Notice> <LoggingService> <BEA-320400> <The log file /home/apps11g/Oracle/Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Oct 5, 2011 11:14:26 AM PHT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/apps11g/Oracle/Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer.log06064. Log messages will continue to be logged in /home/apps11g/Oracle/Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer.log.>
PostInstallConfigIntegration:oracle_ias_farm target auth registration is done.
<Oct 5, 2011 11:14:46 AM PHT> <Warning> <org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl> <BEA-000000> <Configurator services already initialized.>
<Oct 5, 2011 11:14:54 AM PHT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.store.io.file.StoreFile.close(StoreFile.java:440)
at weblogic.store.io.file.Heap.open(Heap.java:320)
at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:104)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:431)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:422)
Truncated. see log file for complete stacktrace
>
<Oct 5, 2011 11:14:54 AM PHT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Oct 5, 2011 11:14:54 AM PHT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Oct 5, 2011 11:14:54 AM PHT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN*
We also tried restoring our backup for the config.xml, system-jazn-data.xml, rpd file and catalog files to at least get the weblogic server up and running. Unfortunately, the same error is being given.
Kindly help.
Thanks and regards,
Nicole

Hi,
Can you please try to Start weblogic services manually. Shutdown all the services and the follow below steps.
1) Start the Weblogic server...startweblogic.cmd
2) Start the node manager from the services.
3) Then login into weblogic console start the bi server1
4) Start the opmn services from cmd prompt.
Hope this will help you...
Thanks
Deva

Similar Messages

  • WLS 9.2: MigrationException: Could not start JTAMT on local server

    I have configured a two machine WLS 9.2 Cluster with two Managed Servers.
              When I try to start the Managed Server through the Node Manager from Admin
              Server's WLS Console, it fails with the following error (
              actually both Managed Servers fail with the same error):
              weblogic.cluster.migration.MigrationException: Could not start JTAMT on
              local server because it could not be deactivated on the current host.
              at
              weblogic.transaction.internal.TransactionRecoveryService.deployAllTransactionRecoveryServices(TransactionRecoveryService.java:400)
              at
              weblogic.transaction.internal.TransactionRecoveryService.resume(TransactionRecoveryService.java:170)
              at
              weblogic.transaction.internal.TransactionRecoveryService.start(TransactionRecoveryService.java:181)
              at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
              at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
              This message resides in file:
              bea920\weblogic92\common\nodemanager\servers\MANAGED-SERVER1\logs\MANAGED-SERVER1.log
              The WLS installation was done including the Node Manager Service.
              Is this error message familiar at all and what could be done to fix it?
              These Managed Servers run on Win2000 and Win2003 respectively. Should I do
              something to the OS (Enable XA Txs in Control Panel/MSDTC)?

    Did you start AdminServer before try to start MANAGED-SERVER1?
              Did you ever migrate Transaction Recovery Service of MANAGED-SERVER1 to other servers?
              If the problem still exist, you can enable the debug option "DebugJTAMigration" and post the stack trace.

  • Weblogic Server not starting up: Boot identity not valid

    Hi All,
    I am trying to start the weblogic server and the following error appears:
    ####<May 28, 2010 12:05:53 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553504> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<May 28, 2010 12:05:53 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553535> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
    ####<May 28, 2010 12:05:53 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553535> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
         at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
         at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
         at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
         at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
         at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
         at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy16.login(Unknown Source)
         at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
         at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy34.authenticate(Unknown Source)
         at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
         at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FAILED>
    ####<May 28, 2010 12:05:53 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<May 28, 2010 12:05:53 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553582> <BEA-000236> <Stopping execute threads.>
    Kindly help me regarding
    Thanks in advance

    Just to add some more details here which will help in diagnosing the problem. I deleted the boot.properties file and the command prompt asked me for the username and password. I provided the correct details but still the server could not start up. Here are the details from the log file:
    ####<May 28, 2010 12:45:47 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947053> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<May 28, 2010 12:45:47 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947084> <BEA-090403> <Authentication for user weblogic denied>
    ####<May 28, 2010 12:45:47 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947084> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
    weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
         at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
         at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
         at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
         at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
         at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
         at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy16.login(Unknown Source)
         at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
         at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy34.authenticate(Unknown Source)
         at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
         at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FAILED>
    ####<May 28, 2010 12:45:47 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<May 28, 2010 12:45:47 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947131> <BEA-000236> <Stopping execute threads.>

  • Urgent: Could not start the Web Analysis services

    Hello Experts,
    I am having issues when starting Web Analysis Services. Could not start the Web Analysis services
    starting weblogic with Java version:
    java version "1.5.0.07"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.07-_20_mar_2007_05_31)
    Java HotSpot(TM) Server VM (build 1.5.0.07 jinteg:03.20.07-11:05 IA64, mixed mode)
    Starting WLS with line:
    /opt/java1.5/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dhyperion.home=/hyphome/Hyperion -DESS_ES_HOME=/hyphome/Hyperion/BIPlus/appsinfo/WebAnalysis/EssbaseJAPI -Datf.session.binding.kill-with-prejudice=true -Dweblogic.j2ee.application.tmpDir=/var/tmp/hyperion -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -da -Dplatform.home=/hyphome/bea/weblogic91 -Dwls.home=/hyphome/bea/weblogic91/server -Dwli.home=/hyphome/bea/weblogic91/integration -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/hyphome/bea/patch_weblogic910/profiles/default/sysext_manifest_classpath -Dweblogic.Name=WebAnalysis -Djava.security.policy=/hyphome/bea/weblogic91/server/lib/weblogic.policy weblogic.Server
    <Jan 6, 2010 12:28:36 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0.07 jinteg:03.20.07-11:05 IA64 from Hewlett-Packard Company>
    <Jan 6, 2010 12:28:37 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: Unable to obtain lock on /hyphome/Hyperion/deployments/WebLogic9/./servers/WebAnalysis/tmp/WebAnalysis.lok. Server may already be running
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:59)
    at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:82)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:365)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:116)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:67)
    >
    <Jan 6, 2010 12:28:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jan 6, 2010 12:28:37 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jan 6, 2010 12:28:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Any suggestions would be of great help. Thanks in advance.
    Regards,
    Sudhir
    Edited by: 637223 on Jan 6, 2010 1:54 PM

    Are you sure there is not another web analysis web application process running, have you checked the processes running on the machine, you may have to kill or stop one of them to release the lock.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]

    I'm using Oracle Linux 6u6. While I'm installing openstack ( 2 node set up) using packstack, I'm getting this error:
    Applying 10.245.33.37_cinder.pp
    10.245.33.37_keystone.pp:                         [ ERROR ]
    Applying Puppet manifests                         [ ERROR ]
    ERROR : Error appeared during Puppet run: 10.245.33.37_keystone.pp
    Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    You will find full trace in log /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
    Please check log file /var/tmp/packstack/20150327-100335-ltC8Ic/openstack-setup.log for more information
    Additional information:
    * A new answerfile was created in: /root/packstack-answers-20150327-100336.txt
    * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
    * Did not create a cinder volume group, one already existed
    * File /root/keystonerc_admin has been created on OpenStack client host 10.245.33.37. To use the command line tools you need to source the file.
    * To access the OpenStack Dashboard browse to http://10.245.33.37/dashboard .
    Please, find your login credentials stored in the keystonerc_admin in your home directory.
    Packages:
    [root@slcai461 ~]# rpm -qa|grep keystone
    python-keystoneclient-0.9.0-5.el6.noarch
    python-keystone-2014.1.3-2.el6.noarch
    openstack-keystone-2014.1.3-2.el6.noarch
    [root@slcai461 ~]# rpm -qa|grep packstack
    openstack-packstack-puppet-2014.1.1-0.12.dev1068.0.4.el6.noarch
    openstack-packstack-2014.1.1-0.12.dev1068.0.4.el6.noarch
    Log :
    [root@slcai461 ~]# cat /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
    Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
    Warning: Scope(Class[Keystone]): The sql_connection parameter is deprecated, use database_connection instead.
    Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
    Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
    Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
    Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
    Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
    Notice: Compiled catalog for slcai461.us.oracle.com in environment production in 1.60 seconds
    Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
       (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
    Notice: /Stage[main]/Keystone/Keystone_config[DEFAULT/admin_token]/value: value changed '[old secret redacted]' to '[new secret redacted]'
    Notice: /Stage[main]/Keystone/Keystone_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'
    Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
    Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]: Triggered 'refresh' from 2 events
    Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    Wrapped exception:
    Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    Error: /Stage[main]/Keystone::Service/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    Notice: /Stage[main]/Keystone::Service/Service[keystone]: Triggered 'refresh' from 5 events
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Skipping because of failed dependencies
    Error: Could not prefetch keystone_endpoint provider 'keystone': Execution of '/usr/bin/keystone --os-endpoint http://127.0.0.1:35357/v2.0/ endpoint-list' returned 1: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
    Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Skipping because of failed dependencies
    Notice: /Stage[main]/Main/Keystone_service[cinder_v2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Main/Keystone_service[cinder_v2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Skipping because of failed dependencies
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies
    Notice: Finished catalog run in 3.10 seconds
    Please let me know how to fix this.

    This problem connected with proxy-setings.
    As the first steps you should try:
           1.  export system env variable:
    http_proxy=http://www-proxy.ru.oracle.com:80
    https_proxy=https://www-proxy.ru.oracle.com:80
    no_proxy=127.0.0.1,localhost
    and you can also export
        export OS_TENANT_NAME=admin
        export OS_USERNAME=admin
        export OS_PASSWORD=root
        export OS_AUTH_URL=http://<conntroller_IP>:5000/v2.0/
    2. and than restart mysqld, if it is running, stop iptables and repeat installation process from beginning with the currently generated answer file
    if we are exporting variable OS_PASSWORD, its value should be the same as value for CONFIG_KEYSTONE_ADMIN_PW in the currently generated answer file.
    This OS_PASSWORD will be written by packstack in the /root/keystonerc_admin file and will be used as admin's password for login to  Openstack dashboard.

  • SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host

    HI,
    I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
    Error: An error occured while starting a cluster instance.
    Oct 14, 2008 5:14:41 PM  Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
    Please check if there is an appropriate running cluster instances
    SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
    There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
    I am pasting the full LOG File details:-
    Oct 14, 2008 6:32:00 PM  Info: Starting cluster instance processes.
    Oct 14, 2008 6:32:00 PM  Error: An error occured while starting a cluster instance.
    Oct 14, 2008 6:32:00 PM  Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
    Name:JM_T1223989073901_0_CPCAPP109
    Host:SBPEPCI1
    State:5
    HostAddress:172.17.131.38
    Name:JC_CPCAPP109_EPP_01
    Host:CPCAPP109
    State:5
    HostAddress:172.17.131.31
    Please check if there is an appropriate running cluster instances.
    Oct 14, 2008 6:32:00 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Oct 14, 2008 6:32:00 PM  Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
    SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
    There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
    The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
    Name:JM_T1223989073901_0_CPCAPP109
    Host:SBPEPCI1
    State:5
    HostAddress:172.17.131.38
    Name:JC_CPCAPP109_EPP_01
    Host:CPCAPP109
    State:5
    HostAddress:172.17.131.31
    Please check if there is an appropriate running cluster instances.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Oct 14, 2008 6:32:04 PM  Info: Starting to save the repository
    Oct 14, 2008 6:32:05 PM  Info: Finished saving the repository
    Oct 14, 2008 6:32:07 PM  Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
    Oct 14, 2008 6:32:07 PM  Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
    Failed deployment of SDAs:
    development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
    Please, look at error logs above for more information!
    I have checked the CONFIGTOOl and the properties seem to be OK.
    I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
    Pls suggest.
    Regards,
    Abhijeet
    I

    Hi George,
    Thnx for your reply.
    I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
    Have checked the Visual admin,it is not in SAFE mode,it working normally.
    Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
    About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
    I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
    Kindly suggest what other steps I shud take.
    Regards,
    Abhijeet

  • Could not start transport control program tp while releasing the TR

    Hello experts,
    i have a problem if any one phase this kind of problem & if u know the solution please share to me its urgent
    problem in Development system ,for this  i had updated kernel , TP patch level , R3trans patch level in  development and quality system , but still the problem is occurring in development system . while  releasing the Transport Request this error is coming  that too not in frequently some times it is happening some times it not happening  ( some times its working fine ) 
    Could not start transport control program tp
    Message no. TP608 Diagnosis
    There was an attempt to start the transport control program tp using the local RFC interface. An
    error occurred here.
      Error code: 4
      RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
    Meaning of the error codes:
      03  RFC system failure
      04  RFC communication failure
    System Response
    The function terminates. Details about the error can be found in the trace file of the Gateway
    Monitor (SMGW).
    Procedure
    Contact your system administrator or use report RSTPTEST to localize the error. You can then
    execute the command again.
    please suggest me what can i do for better , how can i resolve this issue
    Thanks &  Regards,
    Narasimha

    Hello experts ,
    Last one and half month on-words we are phasing some problems on STMS
    while releasing the Transport Request getting this error messages on
    status-bar
    1. "could not start transport control program tp"
    2. while importing the TR into quality system getting this error message" RFC Error :timeout during allocate/CPIC-CALL "
    3.while forwarding the TR from QAS to PRD : " RFC Error :timeout during
    allocate/CPIC-CALL "
    after continues refreshing,we are able to release the request and importthe request into quality system. But after some time again same problem
    coming
    for this we did the kernel upgrade , tp , & R3trans update and STMS RE-
    Configuration etc...But no use with this we got the same problem after
    finishing all these workaround , but don't know what happened after 2-3
    days STMS starts working fine DEV-QAS-PRD ,
    Now we are in the same problem after continues refreshing,we are able torelease the request and import the request into quality system. But after
    some time again same problem coming
    please suggest us what could be the reason behind this & what we can do
    for better

  • Windows could not start the FLEXnet Licensing Service service on Local Computer Error 1068: The dependency service or group failed to start.

    Today I installed Adobe Director 11.5. I received a couple of errors in the FLEXnet Licensing Service. It looks It could not start. I tried to download the Licence fix what I found on Google but that doesn't work, so I checked the 'Service' at service (windows).
    It's status is empty. When I double click on the FLEXnet Licensing Service, clicked on start at the opened window and an error is coming: 
    Windows could not start the FLEXnet Licensing Service service on Local Computer
    Error 1068: The dependency service or group failed to start.
    I don't understand what it says with this message, only that it is impossible to start. However, that is not what I am trying of course, I want to start the FLEXnet Licensing Service, service. 
    Re-installing of the software, doesn't make any change. How can I start it so Director is also working?

    Hi Don1233,
    Please consider seek help at the software vendor side.
    For the services didn't start, follow the suggestions posted by Elton in the thread below:
    https://social.technet.microsoft.com/Forums/en-US/e35da253-f0df-41d1-8df2-b73fa54742a0/windows-could-not-start-the-flexnet-licensing-service-service-on-local-computer-error-1068-the?forum=w7itproinstall
    Best regards
    Michael Shao
    TechNet Community Support

  • 1)Could not start up os x 2)Only could start bootcamp 3)Tried resetting nvram 4)Could not start even in bootcamp 5)Verify disk says -. Verifying volume "Macintosh HD" Error: Live file system repair is not supported 6)Installed maverick on USB d

    1) Could not start up os x
    2) Only could start bootcamp
    3) Tried resetting nvram
    4) Could not start even in bootcamp
    5) Verify disk says …. Verifying volume “Macintosh HD”
    Error: Live file system repair is not supported
    6) Installed maverick on USB drive
    7) Boot from USB drive. Tried verifying HD: Volume header needs minor repair. The volume Recovery HD was found corrupt and needs to be repaired. Verifying volume “Macintosh HD”: Error: live file system repair is not supported.
    8) The terminal code says
    9) Last login: Wed Feb 11 14:09:47 on console
    10)  xxxx-MacBook:~ xxxx$ diskutil list
    11)  /dev/disk0
    12)  #: TYPE NAME SIZE       IDENTIFIER
    13)  0:      GUID_partition_scheme *160.0 GB   disk0
    14)  1: EFI EFI 209.7 MB   disk0s1
    15)  2:                  Apple_HFS Macintosh HD            80.1 GB disk0s2
    16)  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    17)  4:       Microsoft Basic Data 50.0 GB    disk0s4
    18)  /dev/disk1
    19)  #: TYPE NAME SIZE       IDENTIFIER
    20)  0:      GUID_partition_scheme *15.6 GB    disk1
    21)  1: EFI EFI 209.7 MB   disk1s1
    22)  2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
    23)  3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    24)  Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
    25)  No CoreStorage logical volume groups found
    26)  Saeedehs-MacBook:~ saeedehmirbagheri$ sudo gpt -vv -r show /dev/disk0
    27)  Password:
    28)  gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808
    29)  gpt show: /dev/disk0: PMBR at sector 0
    30)  gpt show: /dev/disk0: Pri GPT at sector 1
    31)  gpt show: /dev/disk0: Sec GPT at sector 312581807
    32)  start       size  index  contents
    33)  0          1 PMBR
    34)  1          1 Pri GPT header
    35)  2         32 Pri GPT table
    36)  34          6
    37)  40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
    38)  409640  156394528      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
    39)  156804168    1269544      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
    40)  158073712   56853648        
    41)  214927360   97652736      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
    42)  312580096       1679        
    43)  312581775         32         Sec GPT table
    44)  312581807          1         Sec GPT header
    45)  xxxx-MacBook:~ xxxx$ sudo fdisk /dev/disk0
    46)  Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
    47)  Signature: 0xAA55
    48)  Starting       Ending
    49)  #: id  cyl  hd sec -  cyl  hd sec [     start - size]
    50)  ------------------------------------------------------------------------

    Thank you -
    I booted from external USB. The diskutil list output is from OS x booting from the USB, which shows the following:
    Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *160.0 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            80.1 GB    disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data                         50.0 GB    disk0s4
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *15.6 GB    disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
    No CoreStorage logical volume groups found
    I am not able to use target disk mode because I don't have firewire/thunderbolt ports.

  • The Sun Java Application Server 8.1 could not start anymore

    Very incredible I was working fine from may days with Stydio Creator 2
    but yesterday I run the project and it does not work anymore, please can you suggest something:
    The Sun Java Application Server 8.1 could not start.
    from the Output console:
    C:\Sun\Creator2\SunAppServer8\bin\asadmin.bat start-domain --domaindir C:\Sun\Creator2\SunAppServer8\domains\ creator
    Failed to start server localhost:4848
    Deployment error: Failed to start server localhost:4848. See the server log file for details.
    Exception=Deployment error: Failed to start server localhost:4848. See the server log file for details.
    Deployment error: Failed to start server localhost:4848. See the server log file for details.
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:198)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:75)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
    Caused by: Failed to start server localhost:4848
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:152)
    ... 10 more
    and in the log file:
    [#|2006-02-24T11:49:51.296+0100|WARNING|sun-appserver-pe8.1_02|
    javax.enterprise.system.core|_ThreadID=25;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException: [C4073]: A JMS destination limit was reached.
    Too many Subscribers/Receivers for Queue :
    temporary_destination://queue/192.168.0.159/3376/2 user=admin, broker=127.0.0.1:27676(2403)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onTermination(JmsProviderLifecycle.java:476)
         at com.sun.enterprise.server.ApplicationServer.onTermination(ApplicationServer.java:454)
         at com.sun.enterprise.server.Shutdown.startShutdown(Shutdown.java:42)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeShutdownEventListener(AdminEventMulticaster.java:1445)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleShutdownEvent(AdminEventMulticaster.java:1434)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:443)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
         at com.sun.enterprise.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:90)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
         at sun.rmi.transport.Transport$1.run(Transport.java:153)
         at java.security.AccessController.doPrivileged(Native Method)
         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
         at java.lang.Thread.run(Thread.java:595)
    thanks

    I just had the same problem this morning. I believe the app server starts and if you browser directly to your app you'd get it, but the connection between the appserver and the IDE is somehow lost. An easier solution than completely reinstalling for me was to delete the .Creator folder in my home directory (C;|Documents and Setting\<username>\.Creator) and restart Creator

  • Workflow could not start in HCM process and Forms

    Hi All
    It would be really helpful if you can suggest possible solution regarding case management case in HCM forms and process.
    I have set up a simple custom HCM process and Form regarding Infotype 2 updation. I have checked the process and form consistency and it seems fine. Now when I run the process from HRASR_DT it generates a process number but it also gives an error workflow could not start.I get following error (SWIA log - Step history)
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Exception occurred - Error when starting work item 000000007031
    PROCESS_NODE - Error when processing node '0000000014' (ParForEach index 000000)
    CREATE - Error when creating a component of type 'Step'
    CREATE_WIM_HANDLE - Error when creating a work item
    CREATE_VIA_WFM - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event CREATED and (target) status
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event STATE_CHG and (target) status READY->ERROR
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Executing flow work item - Work item 000000007031: Object FLOWITEM method EXECUTE cannot be executed
    Executing flow work item - Error when processing node '0000000014' (ParForEach index 000000)
    I have searched few SAP notes such as 1384961 which talks about same error but it is implemented in our system (EA-HR 604 , Patch 27, )
    Appreciate any help.
    Thanks
    Umang

    Hi Swati
    One of the similar (not exact) issues were resolved by correcting the event linkage....please refer thread:
    http://scn.sap.com/message/14848795#14848795
    Not sure of the details of the the resolution, maybe Ragavendran Kanagaraj can throw more light.
    Just some high level checks (if not done already):
    Check event linkage errors in SWEQADM if anything is related to your WF
    Check in SWEL if it's showing any more details (not sure if it will)
    Any warnings in syntax check of WF template (PFTC) or WF definition (SWDD)
    Any error sin binding
    regards,
    Modak

  • Could not start the app due to a configuration problem - Launchpad issue

    Hi,
    When I try to launch a custom app from Fiori Launchpad I get an error could not start app due to configuration problem. Error 500- Internal Server Error.
    App works correctly when I try to execute via URL http://XXX/sap/bc/ui5_ui5/sap/zmyfioriui5_v11.
    Screenshot of Chrome debugging and lpd_cust attached.
    It seems problem with ResolveLink but unable to conclude.
    Any Suggestion how to proceed.
    Thanks,
    Mayank

    Hi Mayank,
    Few modifications :
    For additional information field : ".component" at the end is not required.
    Only keep : SAPUI5.Component=sap.ui.demo.myFiori
    Check this screenshot :
    Also, please don't keep Semantic object name and application alias as same name i.e. ymyfioriui5_v11. Its very confusing.
    If above doesn't solve, please confirm below :
    ZXXXLPD is your launchpad role in LPD_CUST tcode.
    Please use TRANSACTIONAL instead of transactional (might be case sensitive)
    Show your semantic object "ymyfioriui5_v11" created in /UI2/SEMOBJ
    Regards,
    Tejas

  • The Sun Java System Application Server could not start

    Hello All,
    I downloaded the Java Pet Store example from sun's website and followed the instructions for installation. After successful installation, I tried to deploy the project and gave the following error
    C:\Documents and Settings\sina\My Documents\Projects\services\nbproject\build-impl.xml:194: Deployment error:
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    See the server log for details.
    BUILD FAILED (total time: 5 minutes 20 seconds)
    The link above points to the following line in the build-impl.xml file
    <nbdeploy debugmode="false" forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" clientModuleUri="${client.module.uri}"/>
    Can any one help whats wrong.An early response will be highly appreciated.
    Kind Regards.
    Hasnain Javed.

    Hi,
    Maybe you already got this fix but here is a suggestion, a snippet from the readme index,html of the petstore download
    # Start the Sun Java System Application Server and the JavaDB database. To do so, open a command prompt and change directory to <javaeesdk.home>/bin and issue the following commands:
    asadmin start-database
    asadmin start-domain
    # Change directory to <petstore.home> and enter the following commands
    ant setup
    ant run
    This will setup, build and deploy the petstore on the application server, and then launch the application homepage in your default browser.
    The "ant setup" that you run from <petstore.home> (petstore.home is the directory where petstore is installed or where you unzipped it) will populate the database wth data and setup the proper database tables etc that are used by the application.
    hth,
    Sean

  • Sun Java System Application Server could not start

    Hi
    I have installed JDK1.5 Update1 + netbeans 5.5 with the JBOSS bundle and added the Sun Java System Application Server 9.1.02.
    I am creating the EJB-JMS application described at
    http://www.netbeans.org/kb/55/ejb30.html
    All the steps are followed properly, but while running the project i get the error
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    D:\MyNBProjects\EJBAPP1\nbproject\build-impl.xml:183: Deployment error:
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    See the server log for details.
    BUILD FAILED (total time: 5 minutes 3 seconds)

    Hi Roman,
    Sorry for the long wait....
    In the mean time I have downloaded NB6.1 (final Release) and JDK 1.6.0_04,added the sjsas-9_1_02 to NB6.1, all are in D:\javak (where previous setup of NB5.5 and jdk1.5 and SJSAS-9_1_02 is AS IS in D:\java)
    Current Scenario:
    Product Version: NetBeans IDE 6.1 (Build 200805300101)
    Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
    System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
    Userdir: D:\Documents and Settings\kedar\.netbeans\6.1
    Now, when i try to Run the SAME code i get the following error:
    Created dir: D:\ProjectsNB\EJBAPP1\dist
    Building jar: D:\ProjectsNB\EJBAPP1\dist\EJBAPP1.ear
    post-dist:
    dist:
    pre-run-deploy:
    Initial deploying EJBAPP1 to D:\ProjectsNB\EJBAPP1\dist\gfdeploy
    Error during incremental deploy: java.lang.NullPointerException
    Start registering the project's server resources
    Finished registering server resources
    java.lang.NullPointerException
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.getFileArchive(DirectoryDeploymentFacility.java:264)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:168)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
    at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
    at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
    java.lang.IllegalStateException: cannot find FileArchive class...
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
    at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
    at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
    Deployment error:
    cannot find FileArchive class...
    See the server log for details.
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:166)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
    Caused by: java.lang.IllegalStateException: cannot find FileArchive class...
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:194)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
    at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
    at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
    ... 16 more
    Caused by: java.lang.IllegalStateException: cannot find FileArchive class...
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
    ... 20 more
    BUILD FAILED (total time: 9 seconds)
    Thanks,
    Kedar.

  • Sun Java System Application Server8  could not start..using OSX

    I am having problems trying to run my application. When run the applicaiton it tries to deploy it but fails with a message that is could not start the applicaiton server. It suggests the fault could be port conflicts or corrupt domain.xml file.
    If I use a browser and goto localhost:18080 I see the applicaiton server seems to have started.....
    To be sure I have no port problems I shutdown all sharing services(FTP, Windows File Sharing etc.) Still not luck.....
    Ideas??

    Hi
    There are situations where appserver watchgog process might be running still even after shutting down the appserver process and sharing services.
    I experienced this few times and rebooted the machine to solve this. This may not be the best solution but try to reboot the machine.
    Thanks
    Srinivas

Maybe you are looking for

  • After the latest update for Adobe Flash, I can't watch movies that require Flash.

    Movies from You Tube and others that require Flash will not run. When I right click on it, it says Movie Not Downloaded. I am running Windows 7 64 Bit. I had no problem before the update.

  • SERVICE CONTROL MANAGER

    The Diagnostic Service Host service failed to start due to the following error:    The account specifield for this service is different from the account specifield    other service running in the same process.    - <Event xmlns="http://schemas.micros

  • MacBook Pro, the left speaker doesnt work

    Hi all, As per title i bought a second hand MacBook Pro A1286, the left speaker doesnt work though. I have tried to unclick "Use ambient noise reduction" that hasnt worked. I also did the cmd, alt, R and P reset. That also didnt work, i was wondering

  • Is an anti-virus needed for a new macbook pro?

    Is an anti-virus needed for a new macbook pro with retina display?

  • Export Database With Password Containing Special Characters

    Hi, I'm doing a database export using the command: exp userid=user/pass@instance parfile=exp_parms.dat The problem is that the password contains special characters so the command fails with a syntax error. The command works perfectly fine when I run