Setting timeout in weblogic.admin command

Hello:
I run a script that checks the state of several thing in my platform. One of the commands I use in this script
is
java -cp .. weblogic.Admin localhost:7001 ..... GETSTATE
IS there anyway to set a timeout in this command for the case weblogic server is hang and doesn´t answer anything. I have tried using sun properties for connect timeout and readTimeout but they haven´t worked(I suppose that it is because weblogic.admin uses t3 instead http). I have thought to make the following
sleep 10|ps -efx| grep -i GETSTATE|grep -v grep|awk '{ print $2 }'|xargs kill -9 &
java -cp .. weblogic.Admin localhost:7001 ..... GETSTATE
but I don´t like at all this solution
Regards,
Mario.

hi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

Similar Messages

  • Creating a Global Role using weblogic.Admin command

    Hi,
    Does anyone have an example of creating a global role using the weblogic.Admin commands? I think I have to use the INVOKE command with the DefaultRoleMapper and createRole method, but I'm not quite sure what the rest of the syntax is.
    Thanks,
    Gabriel

    Gabriel,
    The following works for me:
    weblogic.Admin -url t3://localhost:80 -username weblogic -password weblogic INVOKE -mbean "Security:Name=myrealmDefaultRoleMapper" -method createRole "" "MyGlobalRole" "Grp(Administrators)" ""
    The null first parameter identifies this role as a global role.
    The second param is the name of the role.
    The third parameter is the policy expression. Here, I've mapped the role to the Administrators group. You can also map it to users or a combo of the two. For example, to map it to the "weblogic" user, use "Usr(weblogic)" as the policy expression. If you leave this parameter empty, the role will be created but will not be mapped to anything.
    I'm not sure what the fourth parameter is for. It's not defined in the RoleEditorMBean docs but not including it causes an error. I suspect it's a description field because WLS does not seem to care what you put there.
    HTH,
    Mike

  • Weblogic.Admin command

    After I ran setEnv.sh, I used Java weblogic.Admin command for THREAD_DUMP, it produced error "Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Admin
    ". What would be the best way to run a THREAD_DUMP, kill -3 PID or a java command?

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • Weblogic.Admin command for stopping all Managed Servers in cluster

    Hello All,
    I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
    I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
    I am looking for a way to do that using java weblogic.Admin utility
    Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
    Thanks
    Weblogic Consultant

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • Using weblogic.Admin utility with Weblogic 10.0

    I am trying to write a script which perform PING server to ensure weblogic servers are up before moving on to start another server (the script starts all managed and admin servers), i used to be able to PING server on weblogic 8.1 using weblogic.Admin utility but on weblogic 10.3 i am getting the following exception:
    java.lang.NoClassDefFoundError: weblogic/transaction/internal/TransactionHelperImpl
    at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.<clinit>(EnvironmentManager.java:26)
    at weblogic.jndi.spi.EnvironmentManager.getInstance(EnvironmentManager.java:48)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    at weblogic.jndi.Environment.getContext(Environment.java:277)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
    at weblogic.management.commandline.tools.AdminToolHelper.getMBeanHome(AdminToolHelper.java:559)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.doCommandline(ServerInfoCommandLineInvoker.java:920)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.<init>(ServerInfoCommandLineInvoker.java:116)
    at weblogic.management.commandline.AdminMain.main(AdminMain.java:132)
    at weblogic.Admin.useAdminMain(Admin.java:43)
    at weblogic.Admin.main(Admin.java:22)
    java.lang.NoClassDefFoundError: weblogic/transaction/internal/TransactionHelperImpl
    at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.<clinit>(EnvironmentManager.java:26)
    at weblogic.jndi.spi.EnvironmentManager.getInstance(EnvironmentManager.java:48)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    at weblogic.jndi.Environment.getContext(Environment.java:277)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
    at weblogic.management.commandline.tools.AdminToolHelper.getMBeanHome(AdminToolHelper.java:559)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.doCommandline(ServerInfoCommandLineInvoker.java:920)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.<init>(ServerInfoCommandLineInvoker.java:116)
    at weblogic.management.commandline.AdminMain.main(AdminMain.java:132)
    at weblogic.Admin.useAdminMain(Admin.java:43)
    at weblogic.Admin.main(Admin.java:22)
    The Classpath i am using:
    /ascddata3/olcppads-dev01/weblogic10/server/lib/weblogic.jar:/ascddata3/olcppads-dev01/weblogic10/user_projects/autosc_pss/lib:/ascddata3/olcppads-dev01/weblogic10/server/lib/xmlx.jar:/ascddata3/olcppads-dev01/weblogic10/server/lib/wls-api.jar:/ascddata3/olcppads-dev01/weblogic10/server/lib/wlclient.jar:/ascddata3/olcppads-dev01/weblogic10/server/lib/wljmsclient.jar
    The command i am using is:
    java weblogic.Admin -url ins2d.med.ge.com:9010 -username USERNAME -password PASSWORD PING -verbose
    In weblogic 8.1 the class weblogic/transaction/internal/TransactionHelperImpl used to be present in wljtaclient.jar but i can't locate the class anywhere in weblogic 10.3/server/lib. Kindly let me know how to use weblogic.Admin utility on weblogic 10.3

    Hi,
    First I ran the setDomainEnv.cmd script to set the environment and then executed the weblogic.Admin command and it worked for me.
    D:\wls103\user_projects\domains\816532Local>java weblogic.Admin -adminurl t3://localhost:7010 -username weblogic -password weblogic PING
    Sending 1 ping of 100 bytes.
    RTT = ~16 milliseconds, or ~16 milliseconds/packet
    D:\wls103\user_projects\domains\816532Local>
    Regards.

  • Cannot execute weblogic.Admin class

    Hello, I´m using WLS5.1 SP9, jdk1.2.2_07.
    I cannot execute the weblogic.Admin command in my WLS running, and cannot
    connect through the console.
    I´m getting marshalling exceptions. When I try the command:
    java -classpath
    ./lib/weblogic510sp9boot.jar:./classes:./lib/weblogicaux.jar:./lib/weblogic5
    10sp9.jar weblogic.Admin t3://ip:port PING 1 1
    I get the following exception:
    Failed to connect to t3://10.16.9.51:7701 due to:
    [weblogic.rmi.UnexpectedException: Marshalling:
    - with nested exception:
    [java.lang.ClassNotFoundException: No class found for abbrev=65]]
    I am trying this command from $WL_HOME and I am in the same machine. I have
    tried with and without the SP9 jar files in the classpath and the result is
    the same.
    Does anyone have idea why i am getting this exception?

    Thank you Mike,
    the problem was I had to put weblogic510sp9.jar FIRST in my classpath.
    I tried executing my setEnv.sh script, in which I had set this, an it works
    now.
    Regards,
    David
    "David Rodriguez" <[email protected]> escribió en el mensaje
    news:[email protected]..
    Hello, I´m using WLS5.1 SP9, jdk1.2.2_07.
    I cannot execute the weblogic.Admin command in my WLS running, and cannot
    connect through the console.
    I´m getting marshalling exceptions. When I try the command:
    java -classpath
    ./lib/weblogic510sp9boot.jar:./classes:./lib/weblogicaux.jar:./lib/weblogic5
    10sp9.jar weblogic.Admin t3://ip:port PING 1 1
    I get the following exception:
    Failed to connect to t3://10.16.9.51:7701 due to:
    [weblogic.rmi.UnexpectedException: Marshalling:
    - with nested exception:
    [java.lang.ClassNotFoundException: No class found for abbrev=65]]
    I am trying this command from $WL_HOME and I am in the same machine. Ihave
    tried with and without the SP9 jar files in the classpath and the resultis
    the same.
    Does anyone have idea why i am getting this exception?

  • No output at all from weblogic.Admin HELP | GETSTATE | VERSION on linux

    Hi, somehow I am getting zero output from weblogic.Admin command, is it redirected somewhere?
    #>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD VERSION
    #>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD GETSTATE
    #>
    #>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -username weblogic -password $WPWD HELP
    #>
    Thanks.

    Hi,
    You need to Run the SetDomainEnv.sh/cmd from the Domain_Home/bin and then you can execute the below Commands and they will execute succesfully
    Eg:From Windows Environment Same applies in Linux Environmet as well
    C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl  t3://localhost:7001  -username weblogic -password weblogic1 VERSION
    WebLogic Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638
    C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl  t3://localhost:7001  -username weblogic -password weblogic1 GETSTATE
    Current state of "AdminServer" : RUNNING
    C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl  t3://localhost:7001  -username weblogic -password weblogic1 HELP
    Usage: java [<SSL trust options>] weblogic.Admin
            [ [-url | -adminurl] [<protocol>://]<listen-address>:<port>]
            -username <username> [-password <password>]
            <COMMAND> <ARGUMENTS>
    Hope it helps

  • Add 3rd party Security MBeans with weblogic.Admin?

    [Weblogic 8 SP4 on Solaris]
    Would be great if either through weblogic.Admin or another Java interface I could add 3rd party Security MBeabs (i.e. SiteMinderIdentityAsserter as Identity Asserter). Any ideas? Using the create task in wlconfig doesn't work (NullPointerException while the property table is being updated):
    [wlserver] <2005-okt-27 kl 8:12 IRDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String)
    And I don't want to the console to make additions. Any ideas?

    Will take a look at the scripting. Thanks. But the weblogic.Admin command given is a no go. Maybe later version av weblogic (currently using WLS 8 SP4) support domain qualified names but I get the following error:
    $ blogic.sspi.auth.SiteMinderIdentityAsserter -name Security:Name=myrealmSiteMinderIdentityAsserter
    ObjectName: Invalid value -> Security:Name=myrealmSiteMinderIdentityAsserter
    But if I specify with the create command -mbean "Security:Name=myrealmSiteMinderIdentityAsserter,Type=anything" -type com.netegrity.siteminder.weblogic.sspi.auth.SiteMinderIdentityAsserter then the resource is added. Odd thing is that the Type property in the mbean arguement must be stated. I can put anything there. Doesn't matter.

  • Create pool ....... weblogic.Admin

    Hi
    Weblogic 8.1 sp2
    I am trying to create connection pool through weblogic.Admin command and i m getting error message.
    Command
    java weblogic.Admin -username system -password XXXX -url t3://myserevr:9002 CREATE_POOL -poolName rConnectionPool url=jdbc:sybase:Tds:coolwater:2058/mydb, driver=com.sybase.jdbc2.jdbc.SybDriver
    Error
    Missing startup value props in JDBC Connection Pool url=jdbc:sybase:Tds:172.26.68.175:2058/asdr01db,
    I tried lots of param but keeps giving such message for different param. I tried putting in props also but dosent help. Can someone send me working command.
    thanks
    cw

    Cool Water wrote:
    Hi
    Weblogic 8.1 sp2
    I am trying to create connection pool through weblogic.Admin command and i m getting error message.
    Command
    java weblogic.Admin -username system -password XXXX -url t3://myserevr:9002 CREATE_POOL -poolName rConnectionPool url=jdbc:sybase:Tds:coolwater:2058/mydb, driver=com.sybase.jdbc2.jdbc.SybDriver
    Error
    Missing startup value props in JDBC Connection Pool url=jdbc:sybase:Tds:172.26.68.175:2058/asdr01db,
    I tried lots of param but keeps giving such message for different param. I tried putting in props also but dosent help. Can someone send me working command.
    thanks
    cwHi. The form for the create_pool command is:
    CREATE_POOL poolName props=myProps,initialCapacity=1,maxCapacity=1,capacityIncrement=1,allowShrinking=true,shrinkPeriodMins=15,
    driver=myDriver,url=myURL, testConnsOnReserve=true,testTableName=tablename
    see: http://edocs.beasys.com/wls/docs81/admin_ref/cli.html#1155747
    You need an element like "props=..." for the driver. Try this:
    props=user=system
    Joe

  • How to use weblogic.Admin to set JMS ErrorDestination property on WLS 7?

    This thread is talking about using weblogic.Admin to set the ErrorDestination property.
              http://forums.bea.com/bea/thread.jspa?threadID=200036378&messageID=202187327&start=0
              We run the script against the WLS 7.0 server, script get 'OK' result but it didn't work (property wasn't set). Some error is reported in the admin.log on the server.
              We also run the scipt against the WLS 8 server. It worked perfectly.
              Does anyone know whether this works at all on WLS 7?

    The reason we are using weblogic.Admin is that we are using conf2admin to generate the scripts. weblogic.Admin seems to be the only option for WLS7. Thanks for your suggestion and will definitely check out WLST.
              The full error message is:
              ####<Aug 27, 2004 8:55:20 AM NZST> <Emergency> <Management> <rbd1> <admin> <ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <141067> <The value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue specified for the ErrorDestination attribute is not valid. MBean: n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue. Method: setAttributes. Exception: javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
              Target exception: java.lang.NullPointerException
              .>
              javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
              Target exception: java.lang.NullPointerException
                   at weblogic.management.internal.DynamicMBeanImpl.checkAttributeValueIsLegal(DynamicMBeanImpl.java:1517)
                   at weblogic.management.internal.DynamicMBeanImpl.prepareForModification(DynamicMBeanImpl.java:1440)
                   at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1004)
                   at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:353)
                   at weblogic.management.internal.DynamicMBeanImpl.setAttributes(DynamicMBeanImpl.java:827)
                   at com.sun.management.jmx.MBeanServerImpl.setAttributes(MBeanServerImpl.java:1475)
                   at weblogic.management.internal.RemoteMBeanServerImpl.setAttributes(RemoteMBeanServerImpl.java:905)
                   at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
                   at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
                   at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
                   at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

  • Admin Command Timeout

    My streaming server 3 hanged last night and can be restarted.
    I found that the admin logs have thousands of line like the
    following:
    2008-12-22 03:20:15 236 (e)2671287 Admin Command Timeout:
    (Command (getServerStats) timed out.) -
    2008-12-22 03:20:15 236 (e)2671287 Admin Command Timeout:
    (Command (getVHostStats) timed out.) -
    How can I solve this problem? Restart the computer helps, but
    I wonder there is a way to solve it.

    Well, really, none of these problems should happen! But,
    sadly, they do and not just for me.
    A Google search will show that these Admin timeouts are a
    very common problem but no-one seems to have a solution. More
    worryingly, I have never seen any suggestion from Adobe about what
    might cause them.
    Since my original post I have made two changes to our app:
    (1) when the 'owner' of the room leaves I unload the instance
    (after a 30 seconds delay)
    (2) I amended the application.xml for this app to timeout
    idle connections after 2 minutes (the default is no timeout)
    This has made things slightly better in that the app now runs
    for 2/3 days without failing (rather than failing twice a day).
    But, it still fails and the only thing that brings it back is a
    reboot of the server which is totally unacceptable in a live
    environment where we usually have 500+ clients watching 100 live
    streams at any one time (many on a pay-per-minute basis). The only
    other significant thing I notice now is that once the machine has
    been running for a couple of days the logging stops completely for
    some (but not all) instances i.e. nothing is displayed in the admin
    console and nothing is written to the log files. It's as if the FMS
    Admin has just given up.
    Re. your suggestion about checking IPs etc. There are no
    "hidden clients"! When the Admin fails it is possible to be on a
    machine with a single connection (i.e. my client). When I reload my
    client there is a trace that I have disconnected, then reconnected
    again *but* the connection count goes up by one. If I reload twenty
    times the count will increase to 20. Even if I close my browser the
    connections will apparently stay, sometimes for days!
    As I mentioned, this happens on multiple servers with lots of
    different clients and very, very low load. When it happens is, so
    far, unpredictable other than it will happen and bring down our
    live system.

  • Weblogic Admin server - Configuration/Server Start/Arguments ignored?

    Hi,
    I'm trying to specify a http proxy for a WebLogic Admin Server in order for an application to access external resources. I've placed the settings into the "Server Configuration / Server Start / Arguments", and verified that they have been saved into the config/config.xml file for that domain:
    <server-start>
    <arguments>-Dhttp.proxyHost=[XXXX] -Dhttp.proxyPort=8080</arguments>
    <password-encrypted>[XXXX]</password-encrypted>
    </server-start>
    However, no matter how I start the server, these settings are ignored despite that the documentation states these should be added to the java command line.
    starting weblogic with Java version:
    java version "1.6.0_19"
    Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK16~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
    As a test I created a new managed server in the same domain, specifying the same startup properties, and they were picked up during startup.
    If I manually place the settings into the bin/setDomainEnv.cmd batch file for the domain they are also picked up and work.
    Is there an undocumented restriction on Admin Servers that they ignore the "Server Start / Arguments" setting, or is there something else I can check as to why this is not working?
    Many thanks,
    - Micha.

    Umm... I already pasted the relevant snippet out of the config.xml, but following is the entire file. The startup arguments, as specified in the admin console, are:
    -Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080
    which matches what is saved in the config.xml.
    <?xml version='1.0' encoding='UTF-8'?>
    <domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
    <name>wls_starter</name>
    <domain-version>10.3.2.0</domain-version>
    <security-configuration>
    <name>wls_starter</name>
    <realm>
    <sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
    <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
    <sec:active-type>AuthenticatedUser</sec:active-type>
    </sec:authentication-provider>
    <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
    <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
    <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
    <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
    <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
    <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
    <sec:name>myrealm</sec:name>
    <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
    <sec:name>SystemPasswordValidator</sec:name>
    <pas:min-password-length>8</pas:min-password-length>
    <pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
    </sec:password-validator>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>[XXXXXXXX]</node-manager-password-encrypted>
    </security-configuration>
    <server>
    <name>AdminServer</name>
    <max-http-message-size>-1</max-http-message-size>
    <ssl>
    <enabled>false</enabled>
    </ssl>
    <log>
    <file-name>logs/AdminServer.log</file-name>
    <rotation-type>bySize</rotation-type>
    <number-of-files-limited>true</number-of-files-limited>
    <file-count>7</file-count>
    <file-min-size>500</file-min-size>
    <rotate-log-on-startup>true</rotate-log-on-startup>
    <logger-severity>Trace</logger-severity>
    <logger-severity-properties></logger-severity-properties>
    <log-file-severity>Info</log-file-severity>
    <stdout-severity>Info</stdout-severity>
    <domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
    <memory-buffer-severity>Debug</memory-buffer-severity>
    <log4j-logging-enabled>false</log4j-logging-enabled>
    <redirect-stdout-to-server-log-enabled>false</redirect-stdout-to-server-log-enabled>
    <domain-log-broadcaster-buffer-size>1</domain-log-broadcaster-buffer-size>
    </log>
    <machine>[XXXXXXXXXX]</machine>
    <listen-port>8080</listen-port>
    <listen-port-enabled>true</listen-port-enabled>
    <web-server>
    <frontend-http-port>0</frontend-http-port>
    <frontend-https-port>0</frontend-https-port>
    <keep-alive-enabled>true</keep-alive-enabled>
    <keep-alive-secs>30</keep-alive-secs>
    <https-keep-alive-secs>60</https-keep-alive-secs>
    <post-timeout-secs>30</post-timeout-secs>
    <max-post-size>-1</max-post-size>
    <send-server-header-enabled>false</send-server-header-enabled>
    <wap-enabled>false</wap-enabled>
    <accept-context-path-in-get-real-path>false</accept-context-path-in-get-real-path>
    </web-server>
    <listen-address></listen-address>
    <java-compiler>javac</java-compiler>
    <tunneling-enabled>false</tunneling-enabled>
    <tunneling-client-ping-secs>45</tunneling-client-ping-secs>
    <tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
    <server-start>
    <arguments>-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080</arguments>
    <password-encrypted>[XXXXXXX]</password-encrypted>
    </server-start>
    <server-life-cycle-timeout-val>30</server-life-cycle-timeout-val>
    <startup-timeout>0</startup-timeout>
    <graceful-shutdown-timeout>30</graceful-shutdown-timeout>
    <ignore-sessions-during-shutdown>false</ignore-sessions-during-shutdown>
    <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
    </server>
    <embedded-ldap>
    <name>wls_starter</name>
    <credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.3.2.0</configuration-version>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <machine>
    <name>[XXXXXXXXXX]</name>
    </machine>
    <jms-server>
    <name>WseeJmsServer</name>
    <target>AdminServer</target>
    <persistent-store>WseeFileStore</persistent-store>
    </jms-server>
    <jms-server>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <persistent-store>WseeFileStore</persistent-store>
    </jms-server>
    <self-tuning>
    <work-manager>
    <name>weblogic.wsee.mdb.DispatchPolicy</name>
    <target>AdminServer</target>
    </work-manager>
    </self-tuning>
    <file-store>
    <name>WseeFileStore</name>
    <directory>WseeFileStore</directory>
    <target>AdminServer</target>
    </file-store>
    <jms-system-resource>
    <name>WseeJmsModule</name>
    <target>AdminServer</target>
    <sub-deployment>
    <name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
    <target>WseeJmsServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <sub-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>[XXXXXXXXXX]</target>
    </sub-deployment>
    <descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
    </jms-system-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
    </jdbc-system-resource>
    <saf-agent>
    <name>ReliableWseeSAFAgent</name>
    <target>AdminServer</target>
    <store>WseeFileStore</store>
    </saf-agent>
    </domain>

  • Weblogic Admin Server Doesnt start.

    I have installed Oracle 11g, RCU (WCC 11.1.1.6), Web Center Content 11.1.1.6 (C:\Oracle\Middleware\Oracle_ECM1) and created a domain for Content and was trying to restart the Weblogic Admin Server (C:\Oracle\Middleware\user_projects\domains\WC_Domain6\bin).
    I get the below error:
    'C:\Oracle\MIDDLE~1\Oracle_ECM1\ucm\idc\bin\\Installer -noCommEnv -platform win3
    2 -dumpFormat %s=%s -show IDC_NATIVE_PATH' is not recognized as an internal or e
    xternal command,
    operable program or batch file.
    Content Server provided no native path information in idcCommEnv.cmd.
    'C:\Oracle\MIDDLE~1\Oracle_ECM1\ucm\idc\bin\\Installer -noCommEnv -platform win3
    2 -show NativeOsUtils_classpath' is not recognized as an internal or external co
    mmand,
    operable program or batch file.
    The directory name is invalid.
    Any help is greatly appreciated. Thank you.

    I have a batch file i create that will start everything up. I don't think i've ever seen your error, but the admin server can be called using the startWeblogic up one dir from Bin, i dont know if it makes a difference but i've always used that one. Copy and paste below into a text file (update your paths and urls accordingly), rename to a .bat and you should be able to start everything at once
    @echo off
    START "ECMAdmin" C:\Oracle\Middleware\user_projects\domains\IMTST\startweblogic.cmd
    TIMEOUT 100
    START "NodeManager" C:\Oracle\Middleware\wlserver_10.3\server\bin\startNodeManager
    TIMEOUT 15
    START "soaserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic soa_server1 http://IMTSTipm01:7001
    START "UCMserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic UCM_server1 http://IMTSTipm01:7001
    TIMEOUT 150
    START "IPMserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic IPM_server1 http://IMTSTipm01:7001

  • Weblogic.Admin -TEST_POOL

    Hi All
    I'm trying to test connection pools using weblogic.Admin tool. Even though the connection pool exists in domain, weblogic.Admin returns "Pool does not exist". Could some one help me please? My command is
    <b>${JAVA_HOME}/bin/java weblogic.Admin -url $ADMIN_HOST:$ADMIN_PORT -userconfigfile $DOMAIN_HOME/userconf -userkeyfile $DOMAIN_HOME/userkey TEST_POOL -poolName coustomerOrderConnectionPool
    </b>
    I'm trying this from Unix box and I have ADMIN_HOST, ADMIN_PORT and DOMAIN_HOME set up as environment variables

    Ram Silva wrote:
    Hi All
    I'm trying to test connection pools using weblogic.Admin tool. Even though the
    connection pool exists in domain, weblogic.Admin returns "Pool does not exist".
    Could some one help me please? My command is
    <b>${JAVA_HOME}/bin/java weblogic.Admin -url $ADMIN_HOST:$ADMIN_PORT
    -userconfigfile $DOMAIN_HOME/userconf -userkeyfile $DOMAIN_HOME/userkey TEST_POOL -poolName coustomerOrderConnectionPool
    </b>
    I'm trying this from Unix box and I have ADMIN_HOST, ADMIN_PORT and DOMAIN_HOME set up as environment variablesWhat happens when you hand-type everything in the command?
    Could it just be that you mis-spelled customerOrderConnectionPool
    as you did above? ('coustomerOrderConnectionPool')
    Joe

  • Changing the weblogic admin user password

    I have faced an issue in reseting weblogic admin user password. Following are the steps i have executed in sequence.please help to understand why it is not working this way
    I have 2 managed instances running on two separate computers.
    `Step 1.` shutdown the admin server instance ( i did not shutdown the node manager and other 2 manage server instances
    `Step 2.` Set the environment variables
    `cd $DOMAIN_HOME/bin`
    . ./setDomainEnv.sh
    `Step 3.` then executed the command below to create the new password
    cd ../security
    mv DefaultAuthenticatorInit.ldift oldDefaultAuthenticator
    java weblogic.security.utils.AdminAccount weblogic new_password .
    `Step 4.` backed up existing `boot.properties` file and created a new file. Also backed up data directory of admin server. created a new `boot.properties` file with following configuration
    with plain text username(weblogic_admin) and password (new_password).
    cd ../servers/AdminServer
    mv data data_old
    cd security/
    mv boot.properties oldboot.properties
    Step 5. Then i restarted the admin server. admin server is restarted successfully and i was able to login the admin console with my new username and password. Issue came when i try to shoutdown the admin server. when i execute sh stopWeblogicAdmin.sh , it will through following exception. But , if i kill the admin server process , then i am able to start the admin server with out any problem. and i am able to login to the server also. I am also able to stop and start manage server instances through admin console. But why it is failing only when i try to stop.could anybody help me on this
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Connecting to t3://jipsl13t:12001 with userid weblogic_admin ...
    This Exception occurred at Fri Jan 18 12:20:09 GMT-00:00 2013.
    javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic_admin, failed to be authenticated.]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:42)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:682)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:520)
    at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:573)
    at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:313)
    at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
    at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
    at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyObject.invoke(Unknown Source)
    at org.python.pycode._pyx4.connect$1(<iostream>:16)
    at org.python.pycode._pyx4.call_function(<iostream>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.pycode._pyx15.f$0(/product/jip/jipsl11t/wls/eni132_domain/shutdown.py:6)
    at org.python.pycode._pyx15.call_function(/product/tsm/jipsl11t/wls/eni132_domain/shutdown.py)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.util.PythonInterpreter.execfile(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.WLST.main(WLST.java:29)
    Caused by: java.lang.SecurityException: User: weblogic_admin, failed to be authenticated.
    at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:116)
    at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Problem invoking WLST - Traceback (innermost last):
    File "/product/jip/jipsl11t/wls/eni132_domain/shutdown.py", line 6, in ?
    File "<iostream>", line 22, in connect
    File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing connect : User: weblogic_admin, failed to be authenticated.
    Use dumpStack() to view the full stacktrace
    Done
    Stopping Derby Server...
    Edited by: user8643895 on Jan 18, 2013 9:28 AM

    Hi,
    This issue was occurring because stopWebLogic.sh was picking the username and password from properties user config files in user's home directory: username-WebLogicConfig.properties, username-WebLogicKey.properties.
    If the credentials for weblogic server are changed then new user config files should be created, if these are not created then stopWebLogic.sh will pick up the old credentials and hence fail.
    Please refer the following document for information on user configuration files:
    http://docs.oracle.com/cd/E21764_01/web.1111/e13813/reference.htm#WLSTC430
    Connecting to the server after deleting username-WebLogicConfig.properties, username-WebLogicKey.properties resolves the issue as it forces the script to use the credentials provided by the user while running stopWebLogic.sh
    There are two ways you can resolve this issue:
    1) Create new user config files with the correct credentials as explained in the following document:
    http://docs.oracle.com/cd/E21764_01/web.1111/e13813/reference.htm#WLSTC430
    Or
    2) To force the stopWeblogic.sh script to use credentials provided by the user while running the script follow these steps:
    In the stopWeblogic.sh file use the following connect command:
    connect(userConfigFile='',userKeyFile='', url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')instead of:
    connect(${userID} ${password} url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')Hence in the stopWebLogic.sh script replace:
    echo "import os" >"shutdown.py"
    echo "if os.environ.has_key('wlsUserID'):" >>"shutdown.py"
    echo " wlsUserID = os.environ['wlsUserID']" >>"shutdown.py"
    echo "if os.environ.has_key('wlsPassword'):" >>"shutdown.py"
    echo " wlsPassword = os.environ['wlsPassword']" >>"shutdown.py"
    echo "connect(${userID} ${password} url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')" >>"shutdown.py"
    echo "shutdown('${SERVER_NAME}','Server')" >>"shutdown.py"
    echo "exit()" >>"shutdown.py"with:
    echo "import os" >"shutdown.py"
    echo "if os.environ.has_key('wlsUserID'):" >>"shutdown.py"
    echo " wlsUserID = os.environ['wlsUserID']" >>"shutdown.py"
    echo "if os.environ.has_key('wlsPassword'):" >>"shutdown.py"
    echo " wlsPassword = os.environ['wlsPassword']" >>"shutdown.py"
    echo "connect(userConfigFile='',userKeyFile='', url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')" >>"shutdown.py"
    echo "shutdown('${SERVER_NAME}','Server')" >>"shutdown.py"
    echo "exit()" >>"shutdown.py"
    Regards,
    Kishore

Maybe you are looking for

  • HTTP 403 ERROR IN SXMB_MONI

    Hello Experts, My interface is JDBC to ABAP PROXY in DEV it is workin fine in QUAL in SXMB_MONI it is throwing HTTP Error Error while sending by HTTP (error code:  403 ,error text: Forbidden) (See attachment HTMLError for details) . if i open the mes

  • ESS standard Application modification

    Hello, We are on ERP 6.0 EHP4. We have got ESS and MSS implemented. Applications are working fine now. However user has not yet reverted with any modification on standard one...but still I need to find out on how I can make changes to existing standa

  • Drive not reading discs

    It seems that only some discs will read - I can hear the drive rev up then it slows down..this process repeats three times then it ejects the disc. It won't even read the install disc that came with the computer. Any ideas?

  • Urgent ! add a point to a Chart

    How can I add a point in a Chart (graph type 61) ? I managed to add a data but the point is not visible when my graph is painting.

  • Error -1401 when Updating iPod

    First of all, I've been having the same problem that a lot of others have been having where iTunes crashes when it's trying to update the iPod. I've figured out that mine will not hold any more than 2gb of music at a time, so the first 400 or so song