Newbie problem: EJB Manager password

Hi,
I have installed weblogic 6.1 server on unix. I haven't made any changes to anything whatsoever. When I start, say the default server, I get this:
<Sep 29, 2004 9:20:51 PM EDT> <Notice> <WebLogicServer> <ListenThread listening on port 7001>
<Sep 29, 2004 9:20:52 PM EDT> <Notice> <WebLogicServer> <Started WebLogic Admin Server "myserver" for domain "mydomain" running in Production Mode>
Now, I try to ping it or shut it down using weblogic.Admin, I get something like this:
java weblogic.Admin t3://localhost:7001 PING 1 1Failed to connect to t3://localhost:7001 due to: [weblogic.socket.UnrecoverableConnectException: [Login failed: 'Incompatible version:Incompatible versions - this server:6.1.0.0 client:5.1.0]]
Any help... Thanks..

"Harleen Dhillon" <[email protected]> wrote in message
I have installed weblogic 6.1 server on unix. I haven't made any changes to anything whatsoever. When I start, say the defaultserver, I get this:
>
<Sep 29, 2004 9:20:51 PM EDT> <Notice> <WebLogicServer> <ListenThread listening on port 7001>
<Sep 29, 2004 9:20:52 PM EDT> <Notice> <WebLogicServer> <Started WebLogic Admin Server "myserver" for domain "mydomain" running inProduction Mode>
>
Now, I try to ping it or shut it down using weblogic.Admin, I get something like this:
java weblogic.Admin t3://localhost:7001 PING 1 1Failed to connect to t3://localhost:7001 due to: [weblogic.socket.UnrecoverableConnectException: [Login failed: 'Incompatible
version:Incompatible versions - this server:6.1.0.0 client:5.1.0]
Any help... Thanks..I though the problem manifests itself: you are running admin util from WebLogic 5.1 instead of 6.1.
Use correct CLASSPATH pointing to weblogic.jar in 6.1 installation.
Slava

Similar Messages

"Error getting EJB Manager": password?

Hi,
          I have just installed Weblogic 6.1 and am trying to use the examples server.After I start my server, if I want to do something minor like list all EJBs deployed, I get the following error:
          >java weblogic.deploy list mypassword
          Connecting to localhost, port 7001...
          Error getting EJB manager - have you supplied a password?
          Error: class javax.naming.CommunicationException [null]
          "mypassword" is the same that I supply while starting weblogic server. I'm running the examples server in development mode so all EJBs in examples directory should be deployed. (If I go into web console and look under ejb deployments, I see all the jar files in examples directory and they are marked as deployed. Yet, I can't call any client on them from command line).
          I would appreciate any help.
          Thanks a lot.

Hi Biqiang ,
please confirm the followings:
- your SLD is running on the very same host as DTR.
If not, then you have specified the SLD's host in the Development Configuration Pool settings in NWDS.
- your NWDS matches to the version of the DTR on server side. This is important since the NWDS has also DTR client built in which guarantees the communication between DTR client and DTR server. If there's a major difference between them, you can face communication problems. You can check the version of NWDS in Help -- About in NWDS menu, and you can check the version of the DTR by checking the version of the SC DI_DTR on server side. This you can check by invoking the Component Info page. On 700 this is http://host:port/sap/monitoring/ComponentInfo, as of 710 this is http://host:port/nwa/sysinfo -- "Components" tab.
Best Regards,
Ervin
P.S.: I have also seen you have opened a ticket by us. I'll inform the processor to be aware of this forum thread.

Startup problems for managed server

I am starting up a managed server - although I havent designated this server
          to be in a cluster yet and on startup, I get the exception below.
          Does anyone have any suggestions as to what the cause might be - or what I
          should investigate to narrow it down.
          I am using WLS6.1 GA (it is an eval license).
          Cheers, Nick
          <31-Aug-01 01:44:01 BST> <Info> <WebLogicServer> <Using low strength
          (exportable) SSL.>
          <31-Aug-01 01:44:02 BST> <Info> <Dispatcher> <Exception thrown by rmi
          server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid:
          '-8115623877909240659S:192.168.0.2:[8080,8080,8090,8090,8080,8090,-1]:CCOMDe
          v:CCOMServer01', oid: '9', implementation:
          'weblogic.jndi.internal.RootNamingNode@2130c2''
          javax.naming.NameNotFoundException: Unable to resolve
          weblogic.transaction.resources.CCOMServer01. Resolved:
          'weblogic.transaction.resources' Unresolved:'CCOMServer01' ; remaining name
          at
          weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
          ode.java:802)
          at
          weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
          at
          weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129
          at
          weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
          at
          weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
          at
          weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
          at
          weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
          at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
          Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          at
          weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
          :93)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          at
          weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
          at
          weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          at
          weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :253)
          at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :220)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy6.list(Unknown Source)
          at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:151)
          at
          weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(Serv
          erCoordinatorDescriptor.java:1008)
          at
          weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoo
          rdinatorDescriptor.java:944)
          at
          weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCo
          ordinatorDescriptor.java:936)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          <31-Aug-01 01:44:02 BST> <Info> <Connector> <Initializing J2EE Connector
          Service>
          <31-Aug-01 01:44:02 BST> <Info> <Connector> <J2EE Connector Service
          initialized successfully>


Make sure you have admin server running when you start your managed server.
          Also, in your admin server you have already configured this managed server
          name and it's ip address.
          Wenji
          "Movva" <[email protected]> wrote in message
          news:[email protected]...
          > Hi,
          > Iam also having the same problem. Iam starting the weblogic servers
          > as windows 2K services. The service install script is as follows:
          > (Infact it is the same in case of starting the servers using scripts
          > in the cmd shell also).
          > ------------------------------------------------------
          > @echo off
          >
          > SETLOCAL
          >
          > cd C:\bea\wlserver6.0\config\cdes
          >
          > rem *** Set Classpath to load Weblogic Classes
          > set
          CLASSPATH=.;C:\bea\wlserver6.0\lib\weblogic_sp.jar;C:\bea\wlserver6.0\lib\we
          blogic.jar;C:\bea\mssqlserver4\classes;C:\bea\mssqlserver4\license
          >
          > rem *** Set Command Line for service to execute
          > rem *** %JAVA_HOME%\java will automatically be prepended.
          > rem C:\bea\jdk130\bin\java -ms128m -mx256m -classpath
          >
          .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;C:\bea\mssqlserver4\classes;C:\be
          a\mssqlserver4\license;
          > -Dweblogic.Domain=cdes -Dweblogic.Name="cdesServer11j2"
          > "-Dbea.home=C:\bea" -Dweblogic.management.server="156.15.59.38:7001"
          > "-Djava.security.policy==C:\bea\wlserver6.0/lib/weblogic.policy"
          > -Dweblogic.management.password=weblogic weblogic.Server
          >
          > set CMDLINE="-ms64m -mx256m -classpath \"%CLASSPATH%\"
          > -Dweblogic.Domain=cdes -Dweblogic.Name=cdesServer11i1
          > -Djava.security.policy==\"C:\bea\wlserver6.0/lib/weblogic.policy\"
          > -Dbea.home=\"C:\bea\" -Dweblogic.management.server=156.15.59.38:7001
          > -Dweblogic.management.password= weblogic.Server"
          >
          > rem *** Install the service
          > "C:\bea\wlserver6.0\bin\beasvc" -install -svcname:cdesServer11i1
          > -javahome:"C:\bea\jdk130" -execdir:"C:\bea\wlserver6.0"
          > -extrapath:"C:\bea\wlserver6.0\bin" -cmdline:%CMDLINE%
          >
          > ENDLOCAL
          > ------------------------------------------------------ END OF FILE
          >
          > Any problem in this script ? please let me know.
          >
          > Thnx in Adv,
          > Movva
          >
          >
          > "Prasad Peddada" <[email protected]> wrote in message
          news:<[email protected]>...
          > > Did you use scripts to start servers or do you have your own scripts. If
          > > have your own, could you tell me how you did it.
          > >
          > > -- Prasad
          > >
          > > "Nick Minnutello" <[email protected]>
          wrote
          > > in message news:[email protected]...
          > > > I am starting up a managed server - although I havent designated this
          > > server
          > > > to be in a cluster yet and on startup, I get the exception below.
          > > >
          > > > Does anyone have any suggestions as to what the cause might be - or
          what I
          > > > should investigate to narrow it down.
          > > >
          > > > I am using WLS6.1 GA (it is an eval license).
          > > >
          > > > Cheers, Nick
          > > >
          > > > <31-Aug-01 01:44:01 BST> <Info> <WebLogicServer> <Using low strength
          > > > (exportable) SSL.>
          > > > <31-Aug-01 01:44:02 BST> <Info> <Dispatcher> <Exception thrown by rmi
          > > > server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid:
          > > >
          > >
          '-8115623877909240659S:192.168.0.2:[8080,8080,8090,8090,8080,8090,-1]:CCOMDe
          > > > v:CCOMServer01', oid: '9', implementation:
          > > > 'weblogic.jndi.internal.RootNamingNode@2130c2''
          > > > javax.naming.NameNotFoundException: Unable to resolve
          > > > weblogic.transaction.resources.CCOMServer01. Resolved:
          > > > 'weblogic.transaction.resources' Unresolved:'CCOMServer01' ; remaining
          > > name
          > > > ''
          > > > at
          > > >
          > >
          weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
          > > > ode.java:802)
          > > > at
          > > >
          > >
          weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
          > > > at
          > > >
          > >
          weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129
          > > > )
          > > > at
          > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
          > > > at
          > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
          > > > at
          > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
          > > > at
          > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
          > > > at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
          > > > Source)
          > > > at
          > > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          > > > at
          > > >
          > >
          weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
          > > > :93)
          > > > at
          > > >
          > >
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          > > > at
          > > > weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
          > > > at
          > > >
          weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          > > > at
          > > >
          weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          > > > at
          > > >
          > >
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          > > > :253)
          > > > at
          > > >
          > >
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          > > > :220)
          > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          > > > at $Proxy6.list(Unknown Source)
          > > > at
          > > weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:151)
          > > > at
          > > >
          > >
          weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(Serv
          > > > erCoordinatorDescriptor.java:1008)
          > > > at
          > > >
          > >
          weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoo
          > > > rdinatorDescriptor.java:944)
          > > > at
          > > >
          > >
          weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCo
          > > > ordinatorDescriptor.java:936)
          > > > at
          weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > >
          > > > <31-Aug-01 01:44:02 BST> <Info> <Connector> <Initializing J2EE
          Connector
          > > > Service>
          > > > <31-Aug-01 01:44:02 BST> <Info> <Connector> <J2EE Connector Service
          > > > initialized successfully>
          > > >
          > > >

Manage Passwords List Empty

Starting about 1 week ago all of the passwords in my "Manage Password" list under client security are gone. I know I didn't back them up, so I started to enter some of the passwords back fully intent when I had at least 10 or 15 passwords to back it up. 4 days later the list of 3 or 4 passwords is gone again. Any body know why the list is getting wiped out? Any ideas how I can stop it from getting wiped out?
I am using XP SP 2, Explorer 7.0, and I use Avast for my Anti Virus. I don't download anything, however I don't think I have downloaded a virus. I checked the add ons and Thinkvantage Center is still there. I do not know what the problem here could be. Any help would be appreciated
Thank you
Malay

Have you found any solution? Suddenly my Password manager was empty too. I had all my passwords saved here, but now they are all gone. I'm not able to register new passwords either, even if I fill out the necessary fields when prompted. Any clues?
Best wished from a snowy Lillehammer, Norway.

Cannot set node manager password in weblogic console (10.3.3)

Hi,
I've been trying to configure a custom AD authenticator in the weblogic console for 10.3.3 and get Invalid pad byte on the node manager password when it tries to activate my changes. After trying several things suggested in other forums, I went into the weblogic console, under domains->security, changed the node manager user and password, and still get an Invalid pad byte on the password I entered! Any suggestions?
Thanks!
Julia Allen

Well that didn't work :( . I went into config.xml and changed <node-manager-username> and <node-manager-password-encrypted> to clear text, restarted, went into the console and tried to change the node manager username and password in Domains-->Security-->Advanced and still got invalid pad byte on the password I entered when I saved. Interestingly enough when the page came up the value for node-manager-username was the old value... not the one I changed in config.xml before I started the server. I verified that I changed the correct config.xml. When I looked at it after restart, the values had not been changed to encrypted values. And, yes, production mode is false. So I'm guessing a cache problem somewhere? Or a corruption in one of the other security files that I cannot determine?
One thing I did try was to reset the admin password following steps I found in other places (e.g. renaming ldift/initialized/properties files, running java weblogic.security.utils.AdminAccount) but nothing. Still the same problem. Also note that the server starts just fine... the console just barfs with this invalid pad byte error whenever I try and configure that AD provider or actually try and change the node user name and password.
Any other ideas? Your help is greatly appreciated!
Julia

Problem starting managed server in cluster (The name of the managed server is same as admin server)

          We have the following setup.
          CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
          administrator. We start CLUSTER3 as a self-managed server and then try and start
          CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
          1 and 2 we get the following:
          D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
          03:7001
          D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
          D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
          D:\bea\wlserver6.1>echo off
          * To start WebLogic Server, use the password *
          * assigned to the system user. The system *
          * username and password must also be used to *
          * access the WebLogic Server console from a web *
          * browser. *
          D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
          ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
          ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
          -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
          "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
          r
          <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
          Enter password to boot WebLogic server:
          Starting WebLogic Server ....
          Connecting to http://10.0.1.103:7001...
          The WebLogic Server did not start up properly.
          Exception raised: weblogic.management.configuration.ConfigurationException: The
          name of the managed server is same as admin server. The managed server will not
          be allowed to start up.
          weblogic.management.configuration.ConfigurationException: The name of the manage
          d server is same as admin server. The managed server will not be allowed to star
          t up.
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
          at weblogic.management.Admin.initialize(Admin.java:320)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          D:\bea\wlserver6.1>goto finish
          D:\bea\wlserver6.1>cd config\CLUSTER1
          D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
          D:\bea\wlserver6.1\config\CLUSTER1>
          Many thanks in advance,
          Alex Burton
          http://www.e-plus.com.au/


Don't start the admin server as managed. Removing
          -Dweblogic.management.server...
          from the command line should help.
          Alex Burton wrote:
          > We have the following setup.
          > CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
          > administrator. We start CLUSTER3 as a self-managed server and then try and start
          > CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
          > 1 and 2 we get the following:
          >
          > D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
          > 03:7001
          >
          > D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
          >
          > D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
          >
          > D:\bea\wlserver6.1>echo off
          >
          > ***************************************************
          > * To start WebLogic Server, use the password *
          > * assigned to the system user. The system *
          > * username and password must also be used to *
          > * access the WebLogic Server console from a web *
          > * browser. *
          > ***************************************************
          >
          > D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
          > ".
          > ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
          > ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
          > -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
          > "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
          > r
          > <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
          > Enter password to boot WebLogic server:
          > Starting WebLogic Server ....
          > Connecting to http://10.0.1.103:7001...
          > ***************************************************************************
          > The WebLogic Server did not start up properly.
          > Exception raised: weblogic.management.configuration.ConfigurationException: The
          > name of the managed server is same as admin server. The managed server will not
          > be allowed to start up.
          > weblogic.management.configuration.ConfigurationException: The name of the manage
          > d server is same as admin server. The managed server will not be allowed to star
          > t up.
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
          > at weblogic.management.Admin.initialize(Admin.java:320)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          > ***************************************************************************
          >
          > D:\bea\wlserver6.1>goto finish
          >
          > D:\bea\wlserver6.1>cd config\CLUSTER1
          >
          > D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
          >
          > D:\bea\wlserver6.1\config\CLUSTER1>
          >
          > Many thanks in advance,
          > Alex Burton
          > http://www.e-plus.com.au/

I forgot my hidden file manager password,How can i get back my files

I forgot Hidden file manager password,how can i get back my my data

If you are able to Get Info on the folder of interest go the the very bottom section Sharing and Permissions.
You can gain access to this area by clicking on the lock in the lower right corner of the Get Info window.
Once you have input the admin password for the computer you should be able to edit the permissions on that file/directory.

Oracle Wallet manager password for B2B Host trading partner

Hi All,
I have exported one trusted certificate from B2B midtier wallet manager.
I have saved it as ora_wallet.txt and and oracle.tip.adapter.b2b.WalletLocation refers to its path.
I associated host trading partner delivery channel with non-repudiation and encryption.
Now I need to provide wallet manager password for host trading partner in B2B UI.
I am providing the password which I used while creating the certificate.
I am getting following error:
An error occurred when updating the trading partner.
Error -: AIP-16001: The model validation engine failed due to an internal system error.
As a second trail I exported user requested certificate from wallet to B2B but same error
Where I am doing wrong ?
Thanks

Hai Ramesh,
I did the setup described by you in the last post and I pushed an outbound payload.Fortunately previous error was gone
Now I am getting following error in log file
Error -: AIP-50025: Repository error
     at oracle.tip.adapter.b2b.init.Repository.readCertificates(Repository.java:1060)
     at oracle.tip.adapter.b2b.init.Repository.initExchange(Repository.java:487)
     at oracle.tip.adapter.b2b.init.Repository.initialize(Repository.java:557)
     at oracle.tip.adapter.b2b.init.B2BServer.readRepository(B2BServer.java:432)
     at oracle.tip.adapter.b2b.init.B2BServer.initialize(B2BServer.java:164)
     at oracle.tip.adapter.b2b.init.B2BStarter.startB2B(B2BStarter.java:217)
     at oracle.tip.adapter.b2b.init.B2BStarter.run(B2BStarter.java:104)
Thanks
Praveen

The password for the account "account name" was not changed. Your system administrator may not allow you to change your password or there was some other problem with your password. Contact your system administrator for help.

I have a user who's Active Directory password is going to expire. I had her reset her password by going to apple > system prefs > user > and clicking change password. She received the error "The password for the account "account name" was not changed. Your system administrator may not allow you to change your password or there was some other problem with your password. Contact your system administrator for help."
I had her change her password via the kpasswd command in terminal and that changed her password on the server sucessfully however the laptop has FileVault on it. Filevault is not recognizing the new password just the old password.
I have deleted the keychain which didn't resolve and now I am going to decrypt and reencrypt the drive. I'm hoping this is an isolated issue I have over 25 laptops configured like this.

I "think" the trick was unbinding and rebinding the computer account.
After unencrypting and trying to reencrypt Filevault would still not take the new password.
Rebooted the prompt to update the keychain appeared. Updated the keychain. Filevault would still not take the new password.
Unbinded and rebinded the computer account. It worked and let me add the user to filevault.

Problems with managed beans on included JSPs

I've got a problem with managed beans within an included JSP
The included page looks as follows:
<f:subview id="includedPage" binding="#{testBean.component}">
     <h:outputText value="Hallo from the included page"/>
     <h:outputText value="#{testBean.msg}" />
</f:subview>The including page is also very simple
<f:view>
     <html>
          <head>
               <title>Test include</title>
          </head>
          <body>
               <h:outputText value="Hello from the including page"/>
               <jsp:include page="included.jsp"/>
          </body>
     </html>
</f:view>The testBean is a managed bean with page scope and looks as follows:
public class TestBean {
    public UIComponent fComponent;
    public TestBean() {
        System.out.println("TestBean Constructor called " + toString() );
    public String getMsg() {
        return "Component = " + fComponent ;
    public void setComponent(UIComponent component) {
        System.out.println("setComponent called " + component);
        fComponent = component;
    public UIComponent getComponent() {
        System.out.println("getComponent called " + fComponent);
        return fComponent;
}The output to the console is:
TestBean Constructor called de.kvb.athena.web.beans.TestBean@1bc16f0
getComponent called null
TestBean Constructor called de.kvb.athena.web.beans.TestBean@18622f3
setComponent called javax.faces.component.UINamingContainer@160877b
TestBean Constructor called de.kvb.athena.web.beans.TestBean@5eb489
and the page displays
Hello from the include page
Hello from the included page Component = null
Can anyone explain this behavior ? What's the reason that the page displays
Component = null
and is it possible to display the parent naming container (subview) this way ?
how ?
Thanks

By "page scope" I assume you mean "none"? If so JSF creates a new bean for each place it's referenced. The closest to the behavior you want, once per "page", is really request scope.
(I'm not sure why the constructor is being called thrice, though. I should look into this.)
I assume you want a bean-per-subview scenario. This should be doable, and one way that allows a dynamic number of subviews would be as follows:
--create a "manager" bean in request scope
--give it get/set methods that retrieves a Map of "TestBean" instances; the idea is that each subview use a different key "s1", "s2", etc
back the manager method with Map implementation that checks if there's already a TestBean associated with the key returns it if yes, else null.
If that seems messy, the component solution is hairy :-) See http://forum.java.sun.com/thread.jspa?threadID=568937&messageID=2812561
--A

Problem starting managed server (WL6.1sp2)

I'm trying to staret a managed server, but keep getting errors fetching the
configuration from the admin server?
Right after the first error message, it says"> This condition generally
results when the managed and admin servers are using the same listen address
and port.>"
However, this is not the case here. Any ideas?
The managed server and the admin server uses the same password,
"adminpassword" (yes, this is an internal development system :-)
Here's the error message:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h
".;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=wavetech -Dbe
a.home=C:\bea -Dweblogic.management.password=adminpassword -Dweblogic.Produc
tionModeEnabled=false -Dweblogic.Name=cbfilter -Dweblogic.management.server=
http://192.168.10.31:6001/ -Djava.security.policy=C:\bea\wlserver6.1/lib/web
logic.policy weblogic.Server
Starting WebLogic Server ....
Connecting to http://192.168.10.31:6001/...
<08-03-2002 14:22:49 CET> <Emergency> <Configuration Management> <Errors
detected attempting to connect to admin server at http://192.168.10.31:6001/
during initialization of managed server ( 192.168.10.85:80 ). The reported
error was: < weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
> This condition generally results when the managed and admin servers are
using the same listen address and port.>
<08-03-2002 14:22:49 CET> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
      at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
      at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
      at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
      at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
      at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
      at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
      at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
      at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
      at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
      at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
      at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
      at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
      at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
      at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
      at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
      at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
      at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
      at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
      at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
      at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
      at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
      at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
      at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
      at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
C:\bea\wlserver6.1>cd config\wavetech
C:\bea\wlserver6.1\config\wavetech>ENDLOCAL

I'm trying to staret a managed server, but keep getting errors fetching the
configuration from the admin server?
Right after the first error message, it says"> This condition generally
results when the managed and admin servers are using the same listen address
and port.>"
However, this is not the case here. Any ideas?
The managed server and the admin server uses the same password,
"adminpassword" (yes, this is an internal development system :-)
Here's the error message:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h
".;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=wavetech -Dbe
a.home=C:\bea -Dweblogic.management.password=adminpassword -Dweblogic.Produc
tionModeEnabled=false -Dweblogic.Name=cbfilter -Dweblogic.management.server=
http://192.168.10.31:6001/ -Djava.security.policy=C:\bea\wlserver6.1/lib/web
logic.policy weblogic.Server
Starting WebLogic Server ....
Connecting to http://192.168.10.31:6001/...
<08-03-2002 14:22:49 CET> <Emergency> <Configuration Management> <Errors
detected attempting to connect to admin server at http://192.168.10.31:6001/
during initialization of managed server ( 192.168.10.85:80 ). The reported
error was: < weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
> This condition generally results when the managed and admin servers are
using the same listen address and port.>
<08-03-2002 14:22:49 CET> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
      at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
      at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
      at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
      at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
      at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
      at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
      at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
      at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
      at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
      at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
      at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
      at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
      at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
      at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
      at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
      at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
      at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
      at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
      at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
      at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
      at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
      at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
      at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
      at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
C:\bea\wlserver6.1>cd config\wavetech
C:\bea\wlserver6.1\config\wavetech>ENDLOCAL

Adobe app manager password reset

Hi, I can't find a way to retrieve or reset my adobe application manager password. Anyone know how?
Many thanks

Nearlynormalnora it is likely that something is interfering with the sign in process for the Adobe Application Manager. I would recommend trying the steps listed in Sign in, activation, or connection errors | CC, CS6, CS5.5 - http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html.

Manage passwords for Internet Explorer 11 on Windows 7 ??

How does a person find the mange passwords feature for Internet Explorer 11 on a Windows 7 box? I saw a few webpages on this topic for IE 10, and also for IE11 on Windows 8, but nothing for IE11 on Windows 7. When I go to IE 11 / Internet Options
/ Content / Auto Complete / Settings, there is no option to manage passwords. I went to Credentials Manager and it says there are no windows credentials, and it doesn't show any web or Internet Explorer credentials. Thanks

Thanks for the reply.
That link to the eightforums.com was not helpful. It states:
This tutorial will show you how to view ...
stored passwords by Internet Explorer 11 (IE11)
in your account in Windows 7,
Windows 8.1, and Windows RT 8.1.
View and Remove Stored Passwords for Sites in Credential Manager
1. Open the Control Panel (icons view), and click/tap on the Credential Manager icon.
2. Click/tap on Web Credentials, and expand a listed website (ex: www.eightforums.com) under "Web Passwords" that you want to view or remove ...
However it is apparent that the author of the article did not verify that this method is applicable to Windows 7.
When I click on the Credential Manager in Windows 7, there are no web credentials. I looked on all 3 of my Windows 7 computers (one Windows 7 Professional and two Home Premium boxes) and none of them had a web credentials section.
Any other ideas?

Too many fields QE-3018 when trying to change manager password

Hello, we are seting up a new database, we have uploaded tables with data transfer and copy express, and when trying to change the manager password we are getting this message.
thank you.
Jose.

Hi,
Check the below note 1304754:
[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1304754|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1304754]
Warmest Regards,
Chinho

Apple tv connection problems connection manager :: invoke:: failed to find service

HELP THIS IS WHAT I GET WHEN TRYINF TO LOG INTO APPLE TV:
apple tv connection problems connection manager :: invoke:: failed to find service

Check over on the right side of the thread here under More Like This. Look for one that has a green checkmark which means it is answered. I have read of this however, I do not know how to solve it. It seems as though it is one particular carrier this happens to.

Newbie problem: EJB Manager password

Similar Messages

Maybe you are looking for