Error Installation Admin Server

Hi All,
i've tried to install Directory und AdminServer JES2.
I'm getting the following error after the installtion of the packages:
Configuration of the server(s) succeeded.
Directory Server Configuration Succeeded ...
Configuration succeeded for : DirectoryServ32
*** End configuring DirectoryServ32***
*** Start configuring AdminServ... ***
AdminServConfigurator::configure() called ...
Command //usr/sbin/mpsadmserver configure -f /tmp/adminserv.statefile generated the follwing outputs :
Output Log:
The UNIX user and group specified in the Server Root (/var/opt/mps/serverroot)
do not match values from silent installation configuration file.
Admin Server Configuration Failed ...
Configuration failed for : AdminServ
*** End configuring AdminServ***
where do i have to look?
thanks

Are you installing DS as non root and AS as root? Then it might be bug 5040383.
If so, you can install as root and follow the instructions in the bug how to change it back later.
Also you can open a case so we can add the customer to the bug report.

Similar Messages

  • OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin Server

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

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

  • Error starting Admin Server in a OSB Cluster installation

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

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

  • Certificate error while admin server startup (solaris 8, wls 8.1.4)

    HI All,
    I am getting the following error while starting up my admin server using startWebLogic.sh.
    <Feb 5, 2010 7:51:19 AM GMT> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server "BOS1-ADMIN" for domain "BOS1">
    java.io.IOException: Inconsistent security configuration, Certificate expired: [
    Version: V3
    Subject: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: com.sun.net.ssl.internal.ssl.JSA_RSAPublicKey@672
    Validity: [From: Thu Feb 03 11:25:08 GMT 2005,
    To: Tue Feb 02 11:25:08 GMT 2010]
    Issuer: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00
    Certificate Extensions: 3
    [1]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    [2]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00]
    [3]: ObjectId: 2.5.29.19 Criticality=false
    BasicConstraints:[
    CA:true
    PathLen:2147483647
    Algorithm: MD5withRSA
    Signature:
    0000: 74 15 DF 05 54 27 1D 1D D5 35 F4 99 24 1A 84 1C t...T'...5..$...
    0010: BF 93 25 FA 50 D7 1E 36 66 7F 30 1A EF 67 2A 79 ..%.P..6f.0..g*y
    0020: 4A 72 FD C1 3B 33 05 61 D0 52 92 2D 15 89 68 67 Jr..;3.a.R.-..hg
    0030: E8 13 A6 60 18 38 16 53 16 22 CC 4D 87 19 9F 30 ...`.8.S.".M...0
    0040: 28 F3 3C C0 4C C2 C4 34 69 D3 BA 5C B2 4D 8A FF (.<.L..4i..\.M..
    0050: AA DD BD 04 96 AF 69 05 73 77 8D 93 89 90 5D 23 ......i.sw....]#
    0060: E9 D0 CA 02 5A 20 39 40 85 12 A9 67 04 ED 7B 59 ....Z [email protected]
    0070: 34 FB 31 E7 AD F6 C0 AE E4 5E 66 BB 8E 7D 45 72 4.1......^f...Er
    at weblogic.t3.srvr.SSLListenThread.initSSLContext(SSLListenThread.java:205)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:139)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1637)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:890)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
    at weblogic.Server.main(Server.java:32)
    Any thoughts to share mates????
    I have already posted this topic in general discussion forum and as suggested by faisal posting here as well..Please let me know how to renew certificates????
    Cheers,
    Dinesh

    Hi Dinesh,
    Below are the steps to renew / get new certificates.
    Step A -- Create a Keystore file
    1. Using keytool, enter the following:
    keytool -genkey -alias server -keyalg RSA -keystore your_domain.jks
    'your_domain' in the command above should be the name of the domain you are securing. If you are ordering a Wildcard Certificate, do not include the * in the filename as it is not a valid filename character.
    2. You will be prompted to enter the information for your certificate.
    Please note: When prompted for the first and last name, DO NOT enter your first and last name. Instead, enter the name to which the certificate is being issued (e.g., www.yourdomain.com, mail.yourdomain.com, *.yourdomain.com).
    3. When prompted, enter 'y' or 'yes' to confirm. You will next be asked for a password. You will need to use this same password when generating a CSR and importing your certificates.
    Step B -- Generate a CSR from your new keystore
    1.     Use keytool to create a Certificate Signing Request from your keystore:
    keytool -certreq -alias server -keyalg RSA -file your_domain.csr -keystore your_domain.jks
    Again, 'your_domain' is the name of the domain you are securing. (without the * character if you are ordering a Wildcard Certificate).
    2.     Enter the keystore password.
    3.     Submit the CSR to the Certificate Authority for the certificates.
    Step C: Import and Install the Certificates.
    1.     First you will need to install the Root CA Certificate into your keystore. Copy-and-paste the root certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as trustroot.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the root certificate geotrustroot.pem into your keystore using the following command:
    keytool -import -alias geotrustca -keystore mykeystore -file geotrustroot.pem
    The command should be typed on one line. This command imports the GeoTrust Root CA Certificate into the keystore named mykeystore.
    Step D: Import and Install the SSL Server Certificate
    1.     Next install your SSL Server Certificate (public key) into your keystore. Copy-and-paste the server certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as public.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the SSL server certificate public.pem into your keystore using the following command:
    keytool -import -alias tomcat -keystore mykeystore -file public.pem
    The command should be typed on one line. This command imports the SSL server certificate into the keystore named
    mykeystore.
    Step E: Configuring Keystores
    1.     Both the GeoTrust root CA and SSL server certificates are now installed on your server. Next you will need to configure the keystores by following the instructions in the WebLogic documentation section Configuring Keystores.
    2.     Restart the WebLogic server.
    Hope the information helps.
    Regards,
    Raj

  • Weblogic admin server error.

    Hi Team,
    I am trying to started weblogic admin server from windows i am getting below error from admin server logs.
    but I am able to start weblogic from the command prompt.
    I verified classpath are same in command prompt and windows services and Node Manager also working fine from windows services.
    Please help me on this.it is urgent for me .
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000436> <Allocating 2 reader threads.>
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000446> <Native IO Enabled.>
    ####<Nov 14, 2012 8:31:27 PM GMT+05:30> <Info> <IIOP> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905287039> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288695> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288898> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_9V5rIdcvntKDauQNwFIW41HchnU=>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090511> <The following exception has occurred:
    com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Error> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified..
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Notice> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Critical> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289023> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FAILED>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Error> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Info> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000236> <Stopping execute threads.>
    Thanks in advance.
    Regards,
    Ravi.

    Hi,
    Check this link :
    Re: myrealm error when start through node manager

  • System Exception:OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin

    Hi Experts,
    While logging into the BPC admin client, we are facing the following errors:
    System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin Server
       at OSoft.Services.Webservice.AdminMainService.AdminMainService.GetText(Int64 intStringNum, String& strReturnString, String sParam1, String sParam2, String sParam3, String sParam4, String sParam5)
       at OSoft.Services.Webservice.AdminMainService.AdminMainService.LoadRes()
       at OSoft.Services.Webservice.AdminMainService.AdminMainService..ctor()
       --- End of inner exception stack trace ---}
    We have been facing this issue since the time the server was restarted after changing the admin password.
    Please help us in resolving this issue.
    Thanks in advance.
    Meera

    So you changed the pwd for installation user of SAP BPC.
    After you performed this change did you open Server Manager and go to Reset Credential link?
    There you have to input the new pwd for installation user.
    After that try to login again using BPC client.
    Regards
    Sorin Radulescu

  • Core Dump admin-server instance in Solaris 10 U5 x86

    I have successful upgrade my Solaris 10 x86 u4 to u5. But, the Sun Java System Web Server admin-server unable to start, it produces core files within <SJSWS installation>/admin-server/config.
    I tried re-install SJSWS, but appear the same problem.
    All web server instance are running properly. The problem only appear in admin-server instance only.
    Thanks,
    Regards,
    Adhari

    Can you send more details?
    #cd <SJSWS installation>/admin-server/
    #mdb config/core
    ::stack
    Can you try changing JDKs and seeing if the problem goes away?
    Can you try increasing default page size?
    Have you tried applying required patches ?
    http://docs.sun.com/app/docs/doc/820-2210/gduwe?a=view

  • Admin Server and Managed server startup problem

    Hi,
    My weblogic server version is 11g and OS is Linux.
    When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down.
    FPR6 4008000000000000 (f: 0.000000, d: 3.000000e+00)
    FPR7 4010000000000000 (f: 0.000000, d: 4.000000e+00)
    FPR8 006f007300690078 (f: 6881400.000000, d: 1.379624e-306)
    FPR9 0053006f0063006b (f: 6488171.000000, d: 4.228017e-307)
    FPR10 00650074004d0075 (f: 5046389.000000, d: 9.346098e-307)
    FPR11 0078006500720024 (f: 7471140.000000, d: 2.136208e-306)
    FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
    FPR13 4068000000000000 (f: 0.000000, d: 1.920000e+02)
    FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    Module=/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so
    Module_base_address=0800000000003000
    Target=2_40_20090409_033254_BHdSMr (AIX 5.3)
    CPU=ppc64 (4 logical CPUs) (0x220000000 RAM)
    - Stack Backtrace -
    /usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so:0x000046F4 [0x00003000 +0x000016F4]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005F7088 [0x005AF000 +0x00048088]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB8228 [0x00FAB000 +0x0000D228]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB884C [0x00FAB000 +0x0000D84C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EDE08 [0x005AF000 +0x0003EE08]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF600 [0x005AF000 +0x00040600]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF3A8 [0x005AF000 +0x000403A8]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EC1A0 [0x005AF000 +0x0003D1A0]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB5B4 [0x005AF000 +0x0000C5B4]
    /usr/java6_64/jre/lib/ppc64/default/libj9prt24.so:0x0064C21C [0x00649000 +0x0000321C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB4D0 [0x005AF000 +0x0000C4D0]
    /usr/java6_64/jre/lib/ppc64/default/libj9thr24.so:0x006375F0 [0x00635000 +0x000025F0]
    /usr/lib/libpthreads.a:0x005084F0 [0x00505000 +0x000034F0]
    0x00000000
    JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
    JVMDUMP007I JVM Requesting System dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp'
    JVMDUMP010I System dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp
    JVMDUMP007I JVM Requesting Snap dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc'
    UTE105: Error writing header to tracefile: /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP010I Snap dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP007I JVM Requesting Java dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt'
    JVMDUMP012E Error in Java dump: /usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt
    JVMDUMP013I Processed dump event "gpf", detail "".
    After adding "<native-io-enabled>false</native-io-enabled>" in cofig.xml as shown below , i am able to start the admin server.
    <server>
    <name>AdminServer</name>
    <native-io-enabled>false</native-io-enabled>     
    <listen-port>9595</listen-port>
    <listen-address>10.10.15.16</listen-address>
    </server>
    i did the same thing for managed servers to start the server.
    My Question is:
    Are we missing any configurations/settings while creating domain?
    Is there any other option to start the server without adding <native-io-enabled>false</native-io-enabled>?
    Regards,
    Naga

    Hi,
    my managed server heap size properties are
    -XX:PermSize=256m -XX:MaxPermSize=256m -Xms256M -Xmx512M
    But the error with Admin server also and we are not providing any heap size properties to admin server. Becuase while creating the domain, i haven't got any
    option to set the heap size for Admin server. Am i required to set heap size properties in Admin server by following this path "Summary of Servers >AdminServer->Server start->"Arguements"?
    Sorry, i am not able to find activity.log. Can you please tell me the location where i can find acivity.log. If i am not wrong, are you taling about serverOut.log? If that is serverOut.log, please tell me which log you require? is it admin server or managed server?

  • Admin server cannot Re-discover the managed server

    Hi,
              mypc) win2k version 6.0 sp2, ip=192.168.1.108:7001 (being an admin
              server)
              abpqa1) solaris8 version 6.0sp2, ip=192.168.3.20:8888 adm port:1755
              abpqa2) solaris8 version 6.0sp2, ip=192.1683.2:8888 admport:1755
              **abpqa1 and abpqa2 is clustered.**
              After WL server has restarted in
              mypc(-Dweblogic.management.discover=true option has been used), it
              cannot find any managed WL. What else I need to do in order to make
              discover action work?
              Thanx in Advance.
              Regards,
              Tony
              Starting process:
              C:\bea\wlserver6.0sp1>"C:\bea\jdk130\bin\java" -hotspot -ms64m -mx64m
              -classpath
              .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogic.Domain=mydomain
              -Dweblogi
              c.Name=myserver "-Dbea.home=C:\bea"
              "-Djava.security.policy==C:\bea\wlserver6.0s
              p1/lib/weblogic.policy" -Dweblogic.management.discover=true
              -Dweblogic.managemen
              t.password=password weblogic.Server
              Starting WebLogic Server ....
              <2001/8/20 ??02?56?46?> <Notice> <Management> <Loading configuration
              file .
              \config\mydomain\config.xml ...>
              log file: C:\bea\wlserver6.0sp1\.\config\mydomain\logs\weblogic.log
              <2001/8/20 ??02?56?50?> <Info> <Logging> <Only log messages of severity
              "Er
              ror" or worse will be displayed in this window. This can be changed at
              Admin Con
              sole> mydomain> Servers> myserver> Logging> General> Stdout severity
              threshold>
              <2001/8/20 ??02?56?55?> <Notice> <Management> <Starting discovery of
              Manage
              d Server...>
              <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <WebLogic Server
              started>
              <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <ListenThread
              listening o
              n port 7001>
              <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <SSLListenThread
              listenin
              g on port 7002>
              [ytlu.vcf]
              

    Hi,
              After administration port changed back to 0, it has no error and admin
              server
              can discover the managed server.
              However, the admin server cannot control the active/inactive of the
              deployment
              of the war/ear file in the managed servers after admin has discovered those
              managed server. What I have done is...
              1. click in deployment tab
              2. select a war/ear file from available box to chosen box
              3. click apply
              4. try to view in my browser
              5. 404 page not found
              6. restart managed server
              7. try to view in my brower
              8. got the page displayed in my browser
              ** I have tried active the ear/war files and inactive those files. the
              result is the same **
              Anything configuration I have missed?
              Regards,
              Tony
              ytlu wrote:
              > Already set the value to true. Please read the log carefully.
              >
              > Regards,
              > Tony
              >
              > Kumar Allamraju wrote:
              >
              > > In 6.0 the default value of weblogic.management.discover = false.
              > > You have to explicitly turn it on for the admin server to discover
              > > managed servers.
              > >
              > > --
              > > Kumar
              > >
              > > ytlu wrote:
              > >
              > >> Hi,
              > >>
              > >> mypc) win2k version 6.0 sp2, ip=192.168.1.108:7001 (being an
              > >> admin
              > >> server)
              > >> abpqa1) solaris8 version 6.0sp2, ip=192.168.3.20:8888 adm
              > >> port:1755
              > >> abpqa2) solaris8 version 6.0sp2, ip=192.1683.2:8888 admport:1755
              > >>
              > >> **abpqa1 and abpqa2 is clustered.**
              > >>
              > >> After WL server has restarted in
              > >> mypc(-Dweblogic.management.discover=true option has been used), it
              > >> cannot find any managed WL. What else I need to do in order to make
              > >>
              > >> discover action work?
              > >>
              > >> Thanx in Advance.
              > >>
              > >> Regards,
              > >> Tony
              > >>
              > >> Starting process:
              > >>
              > >> C:\bea\wlserver6.0sp1>"C:\bea\jdk130\bin\java" -hotspot -ms64m
              > >> -mx64m
              > >> -classpath
              > >> .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              > >> -Dweblogic.Domain=mydomain
              > >> -Dweblogi
              > >> c.Name=myserver "-Dbea.home=C:\bea"
              > >> "-Djava.security.policy==C:\bea\wlserver6.0s
              > >> p1/lib/weblogic.policy" -Dweblogic.management.discover=true
              > >> -Dweblogic.managemen
              > >> t.password=password weblogic.Server
              > >> Starting WebLogic Server ....
              > >> <2001/8/20 ??02?56?46?> <Notice> <Management> <Loading configuration
              > >>
              > >> file .
              > >> \config\mydomain\config.xml ...>
              > >> log file: C:\bea\wlserver6.0sp1\.\config\mydomain\logs\weblogic.log
              > >> <2001/8/20 ??02?56?50?> <Info> <Logging> <Only log messages of
              > >> severity
              > >> "Er
              > >> ror" or worse will be displayed in this window. This can be changed
              > >> at
              > >> Admin Con
              > >> sole> mydomain> Servers> myserver> Logging> General> Stdout severity
              > >>
              > >> threshold>
              > >>
              > >> <2001/8/20 ??02?56?55?> <Notice> <Management> <Starting discovery of
              > >>
              > >> Manage
              > >> d Server...>
              > >> <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <WebLogic Server
              > >> started>
              > >>
              > >> <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <ListenThread
              > >> listening o
              > >> n port 7001>
              > >> <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <SSLListenThread
              > >> listenin
              > >> g on port 7002>
              > >
              [ytlu.vcf]
              

  • The admin server could not be reached

    Dear All,
    I have oracle weblogic server running on red hat enterprise Linux, with one managed server. I created a self-signed certificate to access the admin server using SSL connection, after creating the certificate and start running the domain, The admin server run fine, but when i start running the managed server using
    $ ./startManagedWebLogic.sh osb_server1 https://server_ip:7006 i got that error, " The admin server could not be reached on https://server_ip:7006
    and the managed server running independence of admin server, as well as admin server can not establish jmx:t3 connection with the managed server on its SSL port
    also in admin server log i got this error
    <Sep 30, 2013 6:51:00 PM EET> <Warning> <JMX> <BEA-149504> <The adminstration server was unable to establish JMX Connectivity with the osb_server1 at the JMX Service URL of service:jmx:t3://172.17.11.13:8011/jndi/weblogic.management.mbeanservers.runtime.>
    how can i resolve this error?
    thanks in advanced 

    Hi John,
    Thanks. Notable errors in this log are:
    Failed to connect.[Root Cause: Connection refused ] com.hyperion.css.spi.util.jndi.pool.JNDIConnectionPool.validateSocketConnection(Unknown Source)
    Native Directory is not reachable. Will try to re-connect after 3 seconds... com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
    Attempting to connect to Native Directory: Retry Count: 10 com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
    Failed to connect to native directory. com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
    Any ideas?
    Thanks.
    Edited by: 960369 on 21-Sep-2012 02:56
    Edited by: 960369 on 21-Sep-2012 03:33

  • Admin server start up failure

    All,
    Do you see the following error during admin server startup? What may be the cause?
    The password or id typo will not cause the follow errors.
    Thanks.
    ==========================================================
    java.lang.SecurityException: Invalid Subject: principals=[administrator, Adminis
    trators]
    at weblogic.security.service.SecurityServiceManager.seal(SecurityService
    Manager.java:880)
    at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.ja
    va:152)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:374)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    End server side stack trace
    ==========================================================

    check the filerealm.properties
    in the line
    Invalid Subject: principals=[administrator, Adminis trators] at
    it should be like this
    acl.boot.weblogic.server=Administrators,everyone
    group.Administrators=system,admin
    acl.lockServer.weblogic.admin=Administrators
    acl.unlockServer.weblogic.admin=Administrators
    acl.shutdown.weblogic.admin=Administrators
    thanks
    Mir

  • Error starting weblogic Admin server

    Hi All,
    I am not very familiar with Fusion and weblogic but here is my situation:
    Background: I am trying to install Fusion Middleware so I can integrate Oracle Transport Management with E-Business Suite (as per note Integrating Oracle E-Business Suite Release 12 with Oracle BPEL in Oracle SOA Suite 11g (Doc ID 1321776.1))
    I just installed the following on Oracle Enterprise  Linux 64bits
    - SOA Suite 11.1.1.7.0
    - Weblogic Server 10.3.6
    -JDK 1.7.0_25
    -Jdev 11.1.1.7.0
    When starting the weblogic Admin server using "DOMAIN_HOME/startWebLogic.sh' I get an error:
    Starting weblogic with Java version:
    Unrecognized option -jrockit
    Error: Could not create the Java virtual machine
    I found a few thread with similar issue (for different versions of SOA suite)  where it got fixed by changing some parameters in the cmd file but I am not sure they apply to my case.
    Is the jdk version compatible? (I can start JDeveloper ok) , if not which one is the appropriate version. If i need to change it, can you provide details of how to do it? (I am not expert on SOA/Jdev  )
    Can you please help me here ?
    Thanks in advance!

    Well, I tested it
    java -version and it shows :
    1.7.0_25
    Java HotSpot 64 bit Server VM
    --> So I guess the problem is I don't seem to have the jrockit.
    I donwloaded it (Rel 28.7) and installed it. During installation it says "for JDK 1.6.0_45"
    Anyway. I let it install anyway and I modified the PATH to point to the Jrockit bin directory. Then run java -version and it now shows JDK 1.6.0_45 and jvm as rockit
    Now I tried to start the weblogic server and I get the same error. it still uses the JDK 1.7
    So.. again.. is this supported with JDK 7 ?
    How can I fix it now that I installed everything using the JDK 7?
    Thanks

  • CCM.LOG Showing Errors Connecting to Server (Error 5 - Access Denied) to \\\admin$ Share

    Hi All!
    We are encountering what I think would be a normal error in most cases if a client is unavailable or offline.  During client push, we are receiving errors connecting to a NULL value in the log (\\\admin$) as opposed to an actual client:
    Under normal circumstances, the log should read as follows:
     Attempting to connect to administrative share
    \\<machine_name>\admin$ using <Client Push Account>.
    What we are running into is a repeating error (with some processed CCR records in between) that shows as follows:
    ~ Doing Account Cleanup Operation .... SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:14 AM 8612 (0x21A4)
    ~ Processing domain DOMAIN1 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:14 AM 8612 (0x21A4)
    ~ Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:14 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN3\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN2\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN1\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN1\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN1\clientpush_service_account (00000775) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Failed to connect to Server. Error 5 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Processing domain DOMAIN2 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN3\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN2\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN1\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN1\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN1\clientpush_service_account (00000775) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Failed to connect to Server. Error 5 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Processing domain DOMAIN3 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN3\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN2\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN1\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN1\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN1\clientpush_service_account (00000775) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Attempting to connect to administrative share '\\\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Failed to connect to Server. Error 5 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    ~ Account Cleanup Operation Completed successfully. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
    We have Three Domains (Domain1, Domain2, and Domain3) with service accounts specified in the Client Push Installation Client properties. 
    I don't know if there is an entry (or entries) in the SCCM database that are NULL or blank that is generating these errors. 
    \\\admin$ indicates, to me, that there is a missing machine name that should follow the two \\ and before the \admin$.  Obviously we aren't going to be able to connect to a machine with no name (hence the Failed to Connect to Server.  Error
    5). 
    Is there a way to clean the database of these empty records and fix this recurring error?  It repeats every 15 minutes.
    Thank you!

    Yes, I know this is an old post, but I’m trying to clean them up.
    I would review the CM07 console to see if there are any device without a netbios name. It will be these device that are cause you problems.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • "Unauthorized Host" error when you try to connect to the admin server

    "Unauthorized Host" error when you try to connect to the admin server
    <p>
    If you see this error message when you try to connect to a Netscape
    administration server:<P>
    Internal Error
    The administration server was unable to fulfill your request.
    Reason: Unauthorized host
    --------------------------<P>
    Here is how to solve the problem and gain access. First you should
    temporarily open access to all sites, and then once you make sure that
    this lets you get into your administration server, try again to set up
    the domain name or IP address access restrictions you want.<P>
    For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
    Communications servers (1.x) on Unix:<P>
    <OL>
    <LI>Open the "ns-admin.conf" file with a text editor. You can
    find this file in the "admserv" directory under your Netscape
    server root. The directory is named "admin-serv" in 3.x servers.<P>
    <LI>Delete the "Hosts" and "Addresses" lines you see there (either one
    of them might not be present). Don't confuse the "Addresses" line,
    which you should delete, with the "Address" line, which you should NOT
    delete.<P>
    <LI>Save the file, then restart your administration server (on Unix run
    "stop-admin" then "start-admin"; on Windows NT go into the Services
    control panel and stop/start the "Netscape Admin Server" service).<P>
    </OL><P>
    For Commerce Server or Communications Server (1.x) on Windows NT:<P>
    <OL>
    <LI>Go into the registry editor. On Windows NT 4.0, run the command
    "regedit". On Windows 3.51, run the command
    "regedt32".<P>
    <LI>Navigate down to the section
    "HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".<P>
    <LI>Delete the "Hosts" and "Addresses" entries you see there (either one
    of them might not be present). Don't confuse the "Addresses" entry,
    which you should delete, with the "Address" entry, which you should NOT
    delete.<P>
    <LI>Close the registry editor, then restart your administration server
    by going into the Services control panel and stopping then starting the
    "Netscape Administration" service.<P>
    </OL>
    Now try again to access your administration server. Remember, the URL
    will be something like "http://servername:12345/", where
    "12345" is where the administration server's port number goes.<P>
    If you still get the same "Unauthorized host" error, then make sure that
    your "ns-admin.conf" file really doesn't contain any "Hosts" or
    "Addresses" lines any more, and try stopping your administration server
    again then starting it back up.<P>
    Once you have access to your administration server, you can try again to
    set up the access controls you want.<P>
    <UL>
    <LI>For the administration server on a 3.x server installation, select
    "Admin Preferences" from the General Administration page (the first page
    you see when you connect to the admin server), then click on "Superuser Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 2.x server installation, select
    "Configure Administration" from the Server Selector page (the first page
    you see when you connect to the admin server), then click on "Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 1.x server installation, select
    "Configure Administration Server" from the bottom of the Server Manager
    page, then enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the substrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that your
    DNS can resolve those hostnames -- it's generally safer to stick with IP address
    restrictions.
    When you're finished configuring this, click "Make These Changes" then
    restart your admin server.<P>
    </UL><P>
    If you still find yourself getting an "Unauthorized host" error message,
    you can use the above steps to open up access and try different
    settings.<P>

    "Unauthorized Host" error when you try to connect to the admin server
    <p>
    If you see this error message when you try to connect to a Netscape
    administration server:<P>
    Internal Error
    The administration server was unable to fulfill your request.
    Reason: Unauthorized host
    --------------------------<P>
    Here is how to solve the problem and gain access. First you should
    temporarily open access to all sites, and then once you make sure that
    this lets you get into your administration server, try again to set up
    the domain name or IP address access restrictions you want.<P>
    For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
    Communications servers (1.x) on Unix:<P>
    <OL>
    <LI>Open the "ns-admin.conf" file with a text editor. You can
    find this file in the "admserv" directory under your Netscape
    server root. The directory is named "admin-serv" in 3.x servers.<P>
    <LI>Delete the "Hosts" and "Addresses" lines you see there (either one
    of them might not be present). Don't confuse the "Addresses" line,
    which you should delete, with the "Address" line, which you should NOT
    delete.<P>
    <LI>Save the file, then restart your administration server (on Unix run
    "stop-admin" then "start-admin"; on Windows NT go into the Services
    control panel and stop/start the "Netscape Admin Server" service).<P>
    </OL><P>
    For Commerce Server or Communications Server (1.x) on Windows NT:<P>
    <OL>
    <LI>Go into the registry editor. On Windows NT 4.0, run the command
    "regedit". On Windows 3.51, run the command
    "regedt32".<P>
    <LI>Navigate down to the section
    "HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".<P>
    <LI>Delete the "Hosts" and "Addresses" entries you see there (either one
    of them might not be present). Don't confuse the "Addresses" entry,
    which you should delete, with the "Address" entry, which you should NOT
    delete.<P>
    <LI>Close the registry editor, then restart your administration server
    by going into the Services control panel and stopping then starting the
    "Netscape Administration" service.<P>
    </OL>
    Now try again to access your administration server. Remember, the URL
    will be something like "http://servername:12345/", where
    "12345" is where the administration server's port number goes.<P>
    If you still get the same "Unauthorized host" error, then make sure that
    your "ns-admin.conf" file really doesn't contain any "Hosts" or
    "Addresses" lines any more, and try stopping your administration server
    again then starting it back up.<P>
    Once you have access to your administration server, you can try again to
    set up the access controls you want.<P>
    <UL>
    <LI>For the administration server on a 3.x server installation, select
    "Admin Preferences" from the General Administration page (the first page
    you see when you connect to the admin server), then click on "Superuser Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 2.x server installation, select
    "Configure Administration" from the Server Selector page (the first page
    you see when you connect to the admin server), then click on "Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 1.x server installation, select
    "Configure Administration Server" from the bottom of the Server Manager
    page, then enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the substrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that your
    DNS can resolve those hostnames -- it's generally safer to stick with IP address
    restrictions.
    When you're finished configuring this, click "Make These Changes" then
    restart your admin server.<P>
    </UL><P>
    If you still find yourself getting an "Unauthorized host" error message,
    you can use the above steps to open up access and try different
    settings.<P>

  • Errors & warnings when using the Admin Server Console - Help Needed

    hi,
    i just installed weblogic 12c and created a new domain which contains an adminServer and managedServer under
    one cluster.
    after finishing the installation, i started the Admin Server and afterwards started the admin server console.
    and i got the next warning and errors.
    the warning look like this:
    <20:00:35 IST 23/03/2012> <Warning> <Munger> <BEA-2156203> <A version attribute
    was not found in element "web-app" in the deployment descriptor C:\Oracle\Middle
    ware\user_projects\domains\base_domain\servers\AdminServer\tmp\_WL_internal\cons
    oleapp\jxhze9\console-ext\sipserver-console-ext\WEB-INF\web.xml. A version attri
    bute is required, but this version of the WebLogic Server will assume that the l
    atest version is used. Future versions of WebLogic Server will reject descriptor
    s that do not specify the Java EE version. To eliminate this warning, add an app
    ropriate "version=" to element "web-app" in the deployment descriptor.>
    the errors look like this:
    <20:01:51 IST 23/03/2012> <Error> <netuix> <BEA-423158> <No content found at con
    tentUri = /PortalConfig/security/providers/AuthenticatorConfigCommon.portlet.>
    what is the problem? anyone knows?

    If you want to have an weblogic environment with one domain having server spread across different physical machines , then you will have to perform the installations of the weblogic server separately on all the machines . Also make sure that the version of the Weblogic server you are installing is same across the machines and the directory structure is also exactly same.
    In short you will have to perform the below steps :
    1 : install the weblogic server on all the machines with exactly same version and same dir structure .
    2 : Create domain on MachineA providing all the details of the Managed Server and different machine hostnames.
    3 : Start the Admin Server on machineA and then shut down it.
    4 : execute the WLST pack command on MachineA creating a domain template JAR file.
    5 : copy the create jar file on all the Machines ( B , C , D ) you have to distribute your domain.
    6 : Execute the WLST unpack command on all the machines ( B , C , D ) .
    7 : Execute the WLST nmEnroll () command on all the machines ( B, C , D ).
    8 : Start the Managed Servers on all the machines ( B , C , D )

Maybe you are looking for