Cannot start the managed server 2 to node 1

Similar Questions

• Cannot start the managed server - Urgent

  I created a Domain Admin Server (7044) and I am able to connect to the server. User later asked to create the cluster, so I created the new server (WSMS1 - 8044) and the new Cluster. For the Cluster I have given the port (7044) the admin and I targeted the data source exist also, but at present I'm not able to start the managed server using the following command in putty - «./startManagedWeblogic.sh WSMS1 http://localhost:8044".» For your information, there is another area (created by any other person) have the same configuration and it works very well.

  Help, please.

  For starting Managed Server use the below command

  ./startManagedWebLogic.shmanaged_server_nameadmin_url(UNIX)

  In your case

  ./startManagedWeblogic.sh WSMS1 http://localhost:7044 /

  Better to use the Ip address of the local host instead of typing of server

• Cannot start the managed server - unable to get the property of the transaction log.

  I have a server that is managed in a cluster to a single member. The field is simple - server admin and a cluster, the cluster member.
  
  I can boot is no longer this server. When I try to start, he left after the following message:
  
  < BEA-000362 > < server failed. Reason: Failed to get the property of the transaction log. Make sure that the migratable Transaction Recovery Service is migrated on the current server before restarting.
  
  I've checked everything I can think or offers documentation of the error. There is only one target migratable in the field, the managed server. automatic migration is not enabled. I deleted the store by default from the file system, and it gets recreated at startup (so not a problem of permission of system files). I have Activate Server registration to any Transaction scope weblogic debug debugging tab, no additional messages are coming around this message.
  
  Target only shows migratable are hosted on the managed server and not the last migration status.
  
  So I'm puzzled. Can anyone suggest what I should look at?
  
  WebLogic 10.3.5, JDK 1.6.0_29 (64-bit), RHEL 5.6
  
  Published by: SteveElkind on August 28, 2012 11:54

  Hi Steve,.

  Then remove the cluster migratable option, it will sort your problem.

  Kind regards
  Kal

• Cannot start the managed server.

  Hello.

  I try to install weblogic 12.1 on CentOS 6.5 64. I installed, cluster. AdminServer, managedserver on the first server, then I installed the Web server to another server.

  Then I deployed the first node to the second. Run nodemanager on the second server, and when I try to start managedserver on the second server, I get following:

  # < 8 July 2014 16:59:06 IS > < WARNING > < security > < server2 > < Server-22 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1404827946007 > < BEA-090076 > < an error has occurred the attempt to load LDIF for provider authorized person of the u4/wl_server/wls12120/wlserver/server/lib/XACMLAuthorizerInit.ldift file. >

  # < 8 July 2014 16:59:06 IS > < error > < security > < server2 > < Server-22 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1404827946009 > < BEA-090870 > < domain 'myrealm' could not be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: an error has occurred the attempt to load LDIF for provider authorized person of the file/u4/wl_server/wls12120/wlserver/server/lib / XACMLAuthorizerInit.ldift...

  weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: an error has occurred the attempt to load LDIF for provider authorized person of the u4/wl_server/wls12120/wlserver/server/lib/XACMLAuthorizerInit.ldift file.

  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:470)

  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:845)

  Please help me.

  Thanks in advance.

  Andrii.

  Hi Andrii

  I want to confirm how you move the domain created in the fist node the second node.

  If you have not already tried so, you can use pack and unpack to achieve

  Overview of the Pack and unpack commands - 11g Release 1 (10.3.6)

  Basically, the procedure would be

  1. install the weblogic server in the first node

  2 run the pack in the first node

  3. install weblogic serer in the second node

  4 run the Nations United-pack in the second node

  5. test.

  In addition, CentOS is not a platform certified for weblogic server. This migth cause the undesirable behavior

  http://www.Oracle.com/technetwork/middleware/IAS/downloads/fusion-certification-100350.html

  I hope this helps

  Best regards

  Luz

• Using the lens of departure-WLS server to start the managed server

  It is possible to start the managed server using start-server using maven plugin WLS goal?

  Documentation indicates the default value that is an administrator of the server. I tried with the next block in the pom file, but it does not recognize the command given here.

  implementation of <>

  < id > start-osb / < ID >

  pre-integration-test < phase > < / phase >

  < objectives >

  < target > start-server < / target >

  < / objectives >

  < configuration >

  < domainHome > givenpath < / domainHome >

  < command >

  osb_server1 startManagedWeblogic.cmd < param > < / param >

  < / order >

  < / configuration >

  < / run >

  Thank you

  Siva

  Hi Robert,.

  When I try to use the pom file, I get the following error. For this reason, I used the command syntax and parameters as displayed above. Even after this change, it does not start the managed server.

  [org.codehaus.plexus.component.configurator.ComponentConfigurationException: cannot assign configuration 'command' with the value entry ' ${domainHome}\bin\startManagedWeblogic.cmd osb_server1 ${adminUrl} "type java.lang.String to property of type java.lang.String]

• Cannot start the vCenter Server Service

  Cannot start the vCenter Server Service. To get this message to control the attached screenshot

  2013-09 - 03T 21: 34:18.800 + 05:30 [info 03612 'utilvpxdVdb'] [VpxdVdb::SetDBType] connect to DSN: VMware vCenter with username

  2013-09 - 03T 21: 34:18.800 + 05:30 [03612 error 'utilvpxdVdb'] [VpxdVdb::SetDBType]: database error: ODBC error: (IM002) - data [Microsoft] [ODBC Driver Manager] source name not found and no default driver specified

  2013-09 - 03T 21: 34:18.800 + 05:30 [03612 "Default" error] error obtaining configuration information from the database

  This looks like a problem in the registry for the part of the database or a correctly configured system DSN.

• Start the managed server

  Hello
  
  I installed a WLS10.3.5 on a Linux machine. We have created the new domain and be able to start the administration server. But when creating a server managed; and tried to start, it throws error as:
  
  < 16 sep 2011 14:26:02 > < INFO > < NodeManager > < server output log file is "/ opt/weblogic/user_projects/domains/cohe_domain/servers/Cohe-Server1/logs/Cohe-Server1.out" >
  Exception in thread "main" java.lang.NoSuchMethodError: weblogic.i18n.logging.CatalogMessage.getDiagnosticVolume () Ljava/lang/String;
  at weblogic.logging.MessageLogger.log(MessageLogger.java:85)
  at weblogic.logging.MessageLogger.log(MessageLogger.java:111)
  at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:52)
  at weblogic.security.SecurityLogger.logDisallowingCryptoJDefaultJCEVerification(SecurityLogger.java:13444)
  at weblogic.security.utils.SecurityUtils.turnOffCryptoJDefaultJCEVerification(SecurityUtils.java:78)
  in weblogic. Server.main (Server.Java:67)
  < 16 sep 2011 14:26:04 > < FINEST > < NodeManager > < waiting for the process to die: 7021 >
  < 16 sep 2011 14:26:04 > < INFO > < NodeManager > < server failed during startup, so won't be restarted >
  < 16 sep 2011 14:26:04 > < FINEST > < NodeManager > < returned runMonitor, finished setting = true and notification servers >
  
  
  Can someone please suggest, what could be the problem?
  
  Concerning

  In addition, look at the output of the Linux console and make sure that your server is using a compatible JVM... I had this problem in the past.

• Start the managed server (MSI)

  We have a grouped 10.3.2 environment and the need to ensure that all of our managed servers will begin where the server administrator falls down. So when I run the startmanagedWebLogic.cmd in the domain\bin folder it starts well managed server. However, it launches the application with the default memory settings-512-256. I was under the impression that he would use the startup.properties of this server managed out of the domain\server\xxxserver\data folder. Anyone who is familiar with that?
  
  Thank you

  Hi the_assface,

  By default, the MSI mode is enabled for managed servers by... This means that you can start managed servers without running AdminServer.
  If you are going through the 'startManagedWebLogic.sh' file then you will find that he calls the "startWebLogic.sh" internally.
  So that settings are memory you want to apply for your managed servers, you can provide it within the "setDomainEnv.sh" or else it will take the default heap settings... 256...

  If you want to have different piles for your different ManagedServers settings then you create separate Custom scripts for different ManagedServers... start with different Mem args.

  * "startup.properties" file content takes effect when you try to start ManagedServers using the custom NodeManager.* it take no effect if you start your ManagedServers by using startup scripts. "
  .
  .
  Thank you
  Jay SenSharma
  http://WebLogic-wonders.com/WebLogic (WebLogic wonders are here)

• Cannot start WebLogic managed server

  Hello
  
  I have a domain weblogic on a physical machine with two servers (AdminServer and osb_server1 [Managed Server]). (Weblogic 10.3.6)
  I started nodeManager and registered the domain by using the command nmEnroll in WLST.
  I can start "AdminServer" drawn nmStart ('AdminServer') command. AdminServer start correctly.
  
  However, when I want to start managed server (osb_server1):
  1. in the WebLogic administration console, he said:
  (Warning) User is not authorized to perform operations of the lifecycle on the server osb_server1.
  (Warning) All selected servers are currently in a State that is not compatible with this operation or are not associated with a Node Manager running or you are not authorized to perform the requested action. No action will be taken.
  
  2 using the startManagedWebLogic.cmd script after you have entered the name of user and password, it returns authentication denied.
  22 October 2012 10:31:21 IS > < critical > < security > < BEA-090403 > < authentication user weblogic denied >
  < 22 October 2012 10:31:21 IS > < critical > < WebLogicServer > < BEA-000386 > < server subsystem failed. Reason: weblogic.security.SecurityInitializationException: authentication of user weblogic has denied.
  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
  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)
  Truncated. check the log file full stacktrace
  Caused by: 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:251)
  to 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)
  Truncated. check the log file full stacktrace
  >
  
  3 using the nmStart nodeManager command, it complains boot.properties file.
  
  I can connect AdminServer with the same account with no problem.
  
  Best regards
  
  Published by: ToRRaDo on October 22, 2012 17:25

  Did you reboot AdminServer after deleting the LDAP authentication provider?
  I think that your managed server is always try to authenticate the user via ldap authentication provider.

• Cannot start the VirtualCenter Server Service after reboot of the vcenter - 5.1

  I'm unable to start service VirtualCenter Server and VirtualCenter Management Webservices in my vCenter Server.

  SSO, inventory, Web Client and VirtualCenter all in a single virtual machine running.

  All other services other than the Services of VirtualCenter can be started.

  I get the following error in SSL in my vpxd.log file.

  2013 02-14 T 14: 10:26.713 + 05:30 [04892 error 'Default'] SSL_connect SSLStreamImpl::DoClientHandshake (000000000ce5f3a0) has failed. Dumping error SSL queue:

  2013 02-14 T 14: 10:26.713 + 05:30 [04892 error 'Default'] [0] error routines: 14090086:SSL: SSL3_GET_SERVER_CERTIFICATE:certificate check failed
  2013 02-14 T 14: 10:26.714 + 05:30 [error 04892 "HttpConnectionPool-000001' '] [ConnectComplete] connection failed for < cs p:000000000c9d29c0, TCP:cdcdrvc02:7444 >; CNX: (null), error: class Vmacore::Ssl:SSLVerifyException(SSL_Exception:_Verification_parameters:)
  -> PeerThumbprint: 44:04:3E:61:BD:30:00:EF:75:D6:4 C: 16:01:A5:AA:C3:6 B: F4:C7:B6
  -> ExpectedThumbprint:
  -> ExpectedPeerName: cdcdrvc02
  -> The remote host certificate has these problems:
  ->
  -> * A host string certificate comes from an untrusted root.
  ->
  -> * Hostname does not match the name of the subject in the certificate.)
  2013 02-14 T 14: 10:26.715 + 05:30 [warning 03320 'VpxProfiler"] Vpxd::ServerApp:Init [SessionManagerMo::Init ()] took ms 106725
  2013 02-14 T 14: 10:26.715 + 05:30 [warning 03320 'VpxProfiler"] ServerApp::Init [TotalTime] took ms 112279
  2013 02-14 T 14: 10:26.716 + 05:30 [03320 error 'vpxdvpxdMain'] [VpxdMain] failed to initialize: SSL Exception: audit settings:
  -> PeerThumbprint: 44:04:3E:61:BD:30:00:EF:75:D6:4 C: 16:01:A5:AA:C3:6 B: F4:C7:B6
  -> ExpectedThumbprint:
  -> ExpectedPeerName: cdcdrvc02
  -> The remote host certificate has these problems:
  ->
  -> * A host string certificate comes from an untrusted root.
  ->
  -> * Hostname does not match the name of the subject in the certificate.
  2013 02-14 T 14: 10:26.716 + 05:30 [error 03320 "Default"] could not initialize VMware VirtualCenter. Closing...
  2013 02-14 T 14: 10:26.717 + 05:30 [info 03320 'vpxdvpxdSupportManager"] wrote the free/busy information
  2013 02-14 T 14: 10:34.709 + 05:30 [info 03320 "Default"] forcing of VMware VirtualCenter stop now
  Quick help would be highly appreciated.

  See if that helps

  http://communities.VMware.com/message/2191530

• Cannot start the report server

  Hi all
  
  I have an envirnment who both (11g) database and server applications (gr 10, 2) are installed in the same machine. I have not installed components of forms and reports from the application server and forms work well across the web. My problem is that I can't do the report server to the top and runing process as it is alwlyes dowen, and when I picked it up on the web, and then choose Start, the work done, but it always down.
  
  more than failled to the RWSERVER comand to create the new report server and aloyes the message "see installtion guide to how to set up a run this program, then, how do I do the running report server as my reports works do not."
  
  Thank you

  The EM Console is not the best way to find out if your report server is running, I sugest you use the command rwdiag - findall , it will show you the report upward on your server servers, so if you want to create a new report server, you must use *$ORACLE_HOME/bin/addnewservertarget.sh new_servername* for example, this command creates an entry in opmn.xml so that you can check the status of this using the command opmnctl status .

  I hope this helps.

  Greetings.

  Published by: Roberto Barrera on December 9, 2009 12:42
  As Paul says!

• Cannot start the Essbase Server

  Hi all
  
  Yesterday, I installed the OEPM 11.1.1.3 and was able to install and configure Essbase, Shared Services and planning.
  Even I accessed applications to sample (Sample-> basic). Today when I tried to access open console its raise an error.
  I stopped the essbase server service and tried to boot from the start menu. But the essbase server does not start. I checked the newspapers D:\Hyperion\logs\essbase and gives the following messages:
  
  [Mon 23 Nov 17:37:09 2009] Local/ESSBASE0 / / / Info (1051283)
  Recovery of license information, please wait...
  
  [Mon 23 Nov 17:37:09 2009] Local/ESSBASE0 / / / Info (1051286)
  The license retrieved information.
  
  [Mon 23 Nov 17:37:24 2009] Local/ESSBASE0 / / / Error (1051223)
  Single Sign-On [css_init] function call failed with error [error CSS: CSS method invocation of error: com.hyperion.css.CSSSystem < init >.]
  
  [Mon 23 Nov 17:37:24 2009] Local/ESSBASE0 / / / Info (1051198)
  Single Sign-On initialization failed!
  
  [Mon 23 Nov 17:37:30 2009] Local/ESSBASE0 / / / Info (1051232)
  
  Using English_UnitedStates.Latin1@Binary as the locale Essbase
  
  
  [Mon 23 Nov 17:37:31 2009] Local/ESSBASE0 / / / Error (1051527)
  Shared Services security mode it is not possible to start Essbase during SSO to the initialization fails.
  
  
  And also there is a file by name "SharedServices_Security_Client.log", where the content of it is as below.
  
  "2009-11-23 17:37:11, 687 INFO [hand] CSS is initialized as a customer. Properties default logger will be responsible com.hyperion.css.CSSSystem. < init >(Unknown Source)
  2009-11-23 17:37:11, 703 INFO [hand] CSS log file will be generated in the com.hyperion.css.CSSSystem D:\Hyperion\logs\essbase\SharedServices_Security_Client.log. < init >(Unknown Source)
  2009-11-23 17:37:11, 703 INFO [hand] set up CSS with registry com.hyperion.css.CSSSystem.initCSSSystem (unknown Source)
  2009-11-23 17:37:11, 703 INFO [hand] CSS to initialize the registry. com.hyperion.css.common.configuration.CSSConfigurationManager.getConfiguration (unknown Source)
  2009-11-23 17:37:11, 859 INFO [hand], trying to get registry Instance com.hyperion.css.registry.RegistryManager. < init >(Unknown Source)
  2009-11-23 17:37:24, 515 ERROR [main] 20:1092: failed to initialize the EPM system registry. [Root Cause: hyperion.jdbc.base.BaseSQLException: error [Hyperion] [Oracle JDBC Driver] establishing socket to host and port: ibm:1521.] [Reason: Connection refused: connect] com.hyperion.css.registry.RegistryManager. < init >(Unknown Source)
  2009-11-23 17:37:24, 515 ERROR [hand] Arguments: param1 = {}, param2 = null, param3 = D:\Hyperion\logs\essbase\, com.hyperion.css.CSSSystem.initCSSSystem (unknown Source)
  2009-11-23 17:37:24, 515 INFO [main] CSS system initialization has failed. : [ms 13047] com.hyperion.css.CSSSystem.initCSSSystem (unknown Source)
  
  
  Please advice how to solve this problem.

  Hello

  He has problems communicating with your Oracle database where shared Services of / registry is located.
  Connection refused from ibm:1521
  This could be up to oracle not in place and running, a network problem, a firewall problem.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Error at startup of the managed server.

  Hello

  WebLogic Version: 10.3.6.

  I got the error while I tried to start my server managed below.

  I followed the link starting/Stoping Weblogic Server managed - weblogicexpert to launch my managed server.

  I handed my AdminServer username and password. I try to start my MS1 managed server.

  Error LOG:

  weblogic.security.SecurityInitializationException: authentication of user weblogic denied

  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)

  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)

  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:256)

  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

  Caused by: 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:251)

  to 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)

  to javax.security.auth.login.LoginContext.access$ 000 (LoginContext.java:186)

  to 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)

  to com.bea.common.security.internal.utils.Delegator$ ProxyInvocationHandler.invoke (Delegator.java:57)

  to $Proxy16.login (Unknown Source)

  to weblogic.security.service.internal.WLSJAASLoginServiceImpl$ ServiceImpl.login (WLSJAASLoginServiceImpl.java:89)

  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)

  to com.bea.common.security.internal.utils.Delegator$ ProxyInvocationHandler.invoke (Delegator.java:57)

  to $Proxy34.authenticate (Unknown Source)

  at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)

  at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)

  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:930)

  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)

  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:256)

  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

  Kind regards

  Prasad K T,.

  Noemanager use the in-house startup script, it may be the other way around.

  Server management starts with the script but fails with NM.

  It is strange that NM is able to start the managed server, but the script will fail.

  Please check the format:

  startManagedWebLogic.cmd ts: / /:

• error message seen when starting a managed server (dsp_config.ear)

  Hello
  
  I have problems when I start the managed server by the server administrator.
  
  Seems that when I cancel the deployment dsp_config.ear the managed server seems to start without any problems.
  
  But since the dsp_config.ear is removed from the dspconsole is messed up.
  
  The server administrator works fine without any problems with or without deployment of dsp_config.ear.
  
  The trace of the error
  
  # < 27 July 2009 15:36:01 CEST > < WARNING > < DeploymentService > < wdcsn383a > < cashflow1MS1 > < ExecuteThread [ASSET]: '1' for the queue: ' (weblogic.kernel.Default)
  self-adjust)' > < < WLS Kernel > > <><>< 1248701761543 > < BEA-290064 > < deployment servlet service encountered an Exception When you handle the deployment service m
  message for id of the request '-1' from the server 'BEAAdminServer '. Exception: "java.lang.ClassNotFoundException: com.bea.wli.config.deployment.server.ServerVersion:
  This error can indicate that a component has been deployed to a cluster member but no other members of this group. Ensure that any component deployed o
  n a server that is part of a cluster is also deployed on all other members of this group
  at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
  at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
  at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
  at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
  at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
  at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
  at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
  at java.util.HashMap.readObject(HashMap.java:1030)
  at sun.reflect.GeneratedMethodAccessor1.invoke (unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
  at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
  at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
  at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
  at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
  at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
  at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
  at weblogic.deploy.service.internal.DomainVersion.readExternal(DomainVersion.java:180)
  at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
  at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
  at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
  at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readMessage(DeploymentServiceMessage.java:325)
  at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readExternal(DeploymentServiceMessage.java:301)
  at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
  at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
  at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
  at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
  at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.handleDeploymentServiceMessage(DeploymentServiceServlet.java:618)
  at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.internalDoPost(DeploymentServiceServlet.java:235)
  to weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.access$ 000 (DeploymentServiceServlet.java:77)
  to weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet$ 1.run(DeploymentServiceServlet.java:210)
  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
  at weblogic.security.service.SecurityManager.runAs (unknown Source)
  at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:207)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
  
  
  Can someone help me on this one?
  
  It seems more ODSI problem than the problem of weblogic server.

  Looks like you deploy dsp_config.ear on a domain/server that is not activated ODSI.

  com.bea.wli.config.deployment.server.ServerVersion is in /com.bea.common.configfwk.wlinterop_10.3.0.0.jar that is referenced by /features/odsi.server.modules_10.3.0.0.xml and used by com.bea.dsp.management.impl.DomainServiceImpl

• Cannot start the service of Directors of EBS R12.2.4

  Hi all

  EBS R12.2.4

  RHEL 6.6

  I was able to start admin service before but now it does not

  The error log does not show any idea. Help, please.  Thank you

  Service control script execution:

  /U01/appcrp/CRP/FS1/inst/apps/CRP_ip-10-0-0-216/Admin/scripts/adadminsrvctl.sh start - nopromptmsg

  Timeout specified in the context file:-1 second (s)

  
  

  script gave:

  ****************************************************

  
  

  You are running version 120.10.12020000.9 adadminsrvctl.sh

  From WLS Server Admin...

  See /u01/appcrp/CRP/fs1/inst/apps/CRP_ip-10-0-0-216/logs/appl/admin/log/adadminsrvctl.txt for more details

  adadminsrvctl.sh: leave with the State 1

  adadminsrvctl.sh: check the logfile /u01/appcrp/CRP/fs1/inst/apps/CRP_ip-10-0-0-216/logs/appl/admin/log/adadminsrvctl.txt for more information...

  .end std out.

  .end err out.

  
  

  
  

  The log is:

  
  

  ================================================================================

  Validated the arguments passed to the ebs-get-serverstatus option

  AdminServer is currently not running.

  Validated the arguments passed to the ebs-get-serverstatus option

  AdminServer is currently not running.

  03/23/15-18: 29:54: adadminsrvctl.sh version 120.10.12020000.9

  Validated the arguments passed to the ebs-get-serverstatus option

  AdminServer is currently not running.

  03/23/15-18: 29:58: adadminsrvctl.sh: exit with status 2

  ================================================================================

  03/23/15-18: 33:22: adadminsrvctl.sh version 120.10.12020000.9

  Validated the arguments passed to the ebs-get-serverstatus option

  AdminServer is currently not running.

  Validated the arguments passed to the ebs-nmstart-adminsrv option

  Check if the administration server is already in place.

  The server administrator is not already expired.

  Check if the Node Manager is already in place...

  Connection to the node Manager...

  Connected to the node Manager.

  The Node Manager is already in place.

  Start the AdminServer server...

  Error starting AdminServer server: weblogic.nodemanager.NMException: Exception when starting Server "AdminServer.

  03/23/15-18: 33:42: adadminsrvctl.sh: exit status 1

  ================================================================================

  Validated the arguments passed to the ebs-get-serverstatus option

  AdminServer is currently not running.

  Please see the workaround mentioned in the note:

  Error starting AdminServer server: weblogic.nodemanager.NMException: Exception when starting Server "AdminServer" (Doc ID 1906029.1)

  I hope this helps!

  -Kj