Netra T1 AC200 Install of Sol 7

Solaris 8 installs just fine, but Solaris 7 will not boot from cdrom. Have done everything from "boot cdrom" to changing the boot device "setenv boot-device cdrom disk net"
Any suggestions?
Thanks
Chris

shuhman74 is correct that the minimum OS is Sol 8 10/00 but that requires and additional Operating Environment CD be used. The same holds true for Sol 8 1/01. The first OS that you can load without the additional CD is Solaris 8 4/01. For more info see Quick Facts:
http://sunsolve.Sun.COM/handbook_pub/Systems/Netra_T1_AC200/Netra_T1_AC200.html

Similar Messages

  • Netra T1 AC200 problems booting into single user

    I have a stack of Sun Netra T1 AC200's. I installed them all with Solaris 8 10/01 from my
    Jumpstart server. I allready have about a hundred U1,U5 and U10's installed from this server so I know it should work. I have, however not installed any Netra's with it before.
    My problem is that I have no problem booting the Netra's after I have installed them, but if you try to
    boot into single user with fex. "boot -s" then it would display the usual "Type control-d to proceed with normal startup, or give root password for system maintenance". Problem is that no matter what I type, I don't get a reaction!!
    I have everything on console, and I checked that all my connectors are correct and of the type specified in the Netra user manual.
    Strange thing is that halting and jumping into the LOM works without problems, same goes for kicking the system down to single user from multiuser...
    I've also checked with installing Solaris 8 04/01, but same thing happens there.. I can't have three faulty machines either...
    All leads and helpful hints are welcome as I've checked and checked, but can't find anything out of the ordinary...
    On beforehand thanks,
    Thomas

    What does "printenv input-device" show you? My thinking is that maybe LOM might have control at this point. It should probably be "keyboard" or "ttya".
    Also check that root's shell is bin/sh in /etc/passwd.

  • Netra t1 105 install solaris9 from terminal session

    I have quite a problem, I am using a windows box hyper terminal into a netra t1 105 box and am able to boot up and log into the system, however as i am on a windows box i dont have the stop-a button to press when i power it down so as to boot from cdrom, I am trying to do a clean install of solaris 9 onto this box. It seems the more searching I do on this topic the more I hit my head against a brick wall....any help would be appreciated

    I believe you're looking for the STOP+A equivalent on a serial line: send a BREAK signal on the serial line.
    On some (but definitely not on all) windows versions, the bundled hyperterm can send a BREAK signal by
    pressing "control + break". Last I've looked into this I tried Win95 and Win NT 4.0 (?), one hyperterm could
    send a BREAK the other doesn't. But I don't remeber the details any more.
    I just googled a bit, and this page suggest to upgrade hyperterm to some 5.0 revision, to enable the BREAK
    signal:
    http://accuratedatasystems.com/configure-9180-HyperTerm.htm

  • Install Error: Sol 8 2/02; Abort - Cort Dump

    Hi
    I am trying to install Solaris 8 version 2/02 on my Sun Blade 100 and I keep getting the following error after the system config screen: Assertion Failed: Have_ext_net_info (nc) == True File main.c, line 931 Abort - core dump.
    I installed Sol 8 version 10/00 and applied the 8_Recommended.zip patches after my 4/01 CD's got scratched. I order the 2/02 version to replace my 4/01 CD's. The sun blade boots from 2/02 1 of 2 CD without a hitch. The set up screen requested the language english (choice 0 ) then a local: english (49/50). It then starts open windows. Then a beep with a blank screen.
    A small screen appears in the upper left hand corner with the message: System coming up, please wait in.rdisc: no interface detected.
    In the center of the screen is the screen containing the The Solaris install program: Click to continue: I do
    Network Connnectivty screen: Networked or not: Yes
    DHCP Yes or no: Yes
    Host name: austin
    IP address: 192.168.0.2
    System part of a subnet? No (stand alone with a connection to internet. In prior installation I used the subnet mask 255.255.255.0.
    Enable IPv6: no
    Confirm Information screen:
    After I click the button to continue, the box in the upper left reports the following message:
    Assertion Failed: Have_ext_net_info (nc) == True File main.c, line 931 Abort - core dump.
    Starting remote procedure call (RPC) services: sysidns done.
    A small screen in the center System Identification status: Just a moment.
    A this point the install process hangs indefinately. Any suggestions on what the problem is and how to resolve this issue?
    Thanks
    Douglas Sensenig
    [email protected]

    Hello Douglas,
    This is a known bug with Solaris 8 ( Sun Bug ID 4533342). It
    does have an easy work around. In your answers to the
    subnet question please answer yes... i.e
    Network Connnectivty screen: Networked or not: Yes
    DHCP Yes or no: Yes
    Host name: austin
    IP address: 192.168.0.2
    System part of a subnet? YES
    ^^^^^
    You can then give the subnet mask manually as 255.255.255.0
    No idea when this iwll be fixed.
    HTH
    Shridhar

  • Install of Sol. Mgr hangs during INSTALL SOFTWARE UNITS phase of SAPINST

    I'm installing Solution Mgr. 7.0 Ehp1 with Oracle on Windows 2003 Server.  The JDK is 1.4.2_26-x64
    When I get to the INSTALL SOFTWARE UNITS phase of SAPINST, it hangs.  This is phase 37 of 46
    I see several different warnings/errors in the various logs.  Not sure which one is the real problem.  Here is what I see in the various logs. 
    Thanks for any help you can give me.
    sapinst.log
    ERROR 2010-05-17 22:47:32.955
    FJS-00003  uncaught exception: nw.usageTypes.utlConnectionError:
    Execution of UTL tool 'C:\j2sdk1.4.2_26-x64\bin\java.exe -classpath C:\usr\sap\MES\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_jce.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_jsse.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_smime.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_ssl.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/w3c_http.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/antlr.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/exception.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/jddi.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/logging.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/offlineconfiguration.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/opensqlsta.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/SDMutil.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/SLUtil.jar;C:\usr\sap\MES\DVEBMGS00\exe\ojdbc14.jar -activated -prod_name=SOLMAN -usage_name=SM-APP -usage_vendor=sap.com -log=UTL_activate_usages.log -action=true -sid=MES -dsn=jdbc/pool/MES -ssprops=C:/usr/sap/MES/SYS/global/security/data/SecStore.properties -ssk=C:/usr/sap/MES/SYS/global/security/data/SecStore.key' aborts with return code 64 due to a database connection error. DIAGNOSIS: The connection parameters are wrong or the database server has been shut down. SOLUTION: Check 'UTL_activate_usages.log' and 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UTL.java.log' for more information. (in script unknown, line 0: ???)
    ERROR 2010-05-17 22:47:34.126
    FCO-00011  The step enableUsageTypes with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|enableUsageTypes was executed with status ERROR ( Last error reported by the step :uncaught exception: nw.usageTypes.utlConnectionError:
    Execution of UTL tool 'C:\j2sdk1.4.2_26-x64\bin\java.exe -classpath C:\usr\sap\MES\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_jce.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_jsse.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_smime.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/iaik_ssl.jar;
    solman/sapmnt/MES/SYS/global/security/lib/tools/w3c_http.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/antlr.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/exception.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/jddi.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/logging.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/offlineconfiguration.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/opensqlsta.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/SDMutil.jar;C:/usr/sap/MES/SYS/global/sltools/sharedlib/SLUtil.jar;C:\usr\sap\MES\DVEBMGS00\exe\ojdbc14.jar -activated -prod_name=SOLMAN -usage_name=SM-APP -usage_vendor=sap.com -log=UTL_activate_usages.log -action=true -sid=MES -dsn=jdbc/pool/MES -ssprops=C:/usr/sap/MES/SYS/global/security/data/SecStore.properties -ssk=C:/usr/sap/MES/SYS/global/security/data/SecStore.key' aborts with return code 64 due to a database connection error. DIAGNOSIS: The connection parameters are wrong or the database server has been shut down. SOLUTION: Check 'UTL_activate_usages.log' and 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UTL.java.log' for more information. (in script unknown, line 0: ???)).
    java_server.log:
    Info: Starting cluster instance processes.
    Info: Starting the instance JC_solman_MES_00 running on host solman
    Info: Starting the instance JC_solman_MES_00 processes. The instance is running on host solman                         
    Info: Starting the process server0
    std_server0.out
    May 17, 2010 11:39:38... ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_11] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:183)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
    dev_jcontrol
    [Thr 3208] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 1996] JControlDPMessageProxy: Thread 1996 started as handler thread for R/3 dispatcher messages.
    [Thr 3208] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_26-x64
    [Thr 3208] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\MES\DVEBMGS00\exe\jvmx.jar
    dev_rd
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 448
        (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1534) [nixxi.cpp    4436]
    ***LOG S23=> GwIDisconnectClient, client disconnected (003) [gwxxrd.c     11603]
    ***LOG S74=> GwIDisconnectClient, client disconnected ( solman) [gwxxrd.c     11614]
    ***LOG S0R=> GwIDisconnectClient, client disconnected () [gwxxrd.c     11649]
    ***LOG S0I=> GwIDisconnectClient, client disconnected ( jlaunch) [gwxxrd.c     11662]
    LOCATION    SAP-Gateway on host solman.sap.mertik.de / sapgw00
    ERROR       connection to partner 'solman.sap.mertik.de:1534' broken
    TIME        Mon May 17 23:39:38 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -6
    MODULE      nixxi.cpp
    LINE        4436
    DETAIL      NiIRead
    SYSTEM CALL recv
    ERRNO       10054
    ERRNO TEXT  WSAECONNRESET: Connection reset by peer
    COUNTER     3
    dev_server0
    [Thr 4332] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\MES\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID2285550]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_26-x64
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser -verbose:gc -Djco.jarm=1 -XX:PermSize=512m -XX:MaxPermSize=512m -XX:NewSize=320m -XX:MaxNewSize=320m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:PrintGCTimeStamps -XX:UseTLAB -XX:SoftRefLRUPolicyMSPerMB=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:+UseParNewGC -Drdbms.driverLocation=C:/usr/sap/MES/DVEBMGS00/exe/ojdbc14.jar
    -> java vm version    : 1.4.2_26-b03
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> stack size         : 2M
    -> root path          : C:\usr\sap\MES\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : C:\usr\sap\MES\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : C:\usr\sap\MES\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\MES\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 4332] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4404] JLaunchIStartFunc: Thread 4404 started as Java VM thread.
    [Thr 4404] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
         Java Parameters: -Xss2m
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Djco.jarm=1
    -> arg[ 11]: -XX:PermSize=512m
    -> arg[ 12]: -XX:MaxPermSize=512m
    -> arg[ 13]: -XX:NewSize=320m
    -> arg[ 14]: -XX:MaxNewSize=320m
    -> arg[ 15]: -XX:SurvivorRatio=2
    -> arg[ 16]: -XX:TargetSurvivorRatio=90
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -XX:+UseTLAB
    -> arg[ 19]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 20]: -Dsun.io.useCanonCaches=false
    -> arg[ 21]: -Djava.awt.headless=true
    -> arg[ 22]: -XX:+UseParNewGC
    -> arg[ 23]: -Drdbms.driverLocation=C:/usr/sap/MES/DVEBMGS00/exe/ojdbc14.jar
    -> arg[ 24]: -Dsys.global.dir=C:\usr\sap\MES\SYS\global
    -> arg[ 25]: -Dapplication.home=C:\usr\sap\MES\DVEBMGS00\exe
    -> arg[ 26]: -Djava.class.path=C:\usr\sap\MES\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\MES\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 27]: -Djava.library.path=C:\j2sdk1.4.2_26-x64\jre\bin\server;C:\j2sdk1.4.2_26-x64\jre\bin;C:\j2sdk1.4.2_26-x64\bin;C:\usr\sap\MES\DVEBMGS00\j2ee\os_libs;C:\ORACLE\MES\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\usr\sap\MES\SYS\exe\uc\NTAMD64
    -> arg[ 28]: -Dmemory.manager=1024M
    -> arg[ 29]: -Xmx1024M
    -> arg[ 30]: -Xms1024M
    -> arg[ 31]: -Xss2M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=4328
    -> arg[ 35]: -Djstartup.ownHardwareId=U1840606892
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=MES_00_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=64998
    -> arg[ 42]: -DSAPSYSTEM=00
    -> arg[ 43]: -DSAPSYSTEMNAME=MES
    -> arg[ 44]: -DSAPMYNAME=solman_MES_00
    -> arg[ 45]: -DSAPPROFILE=C:\usr\sap\MES\SYS\profile\MES_DVEBMGS00_solman
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=00
    -> arg[ 50]: -DSAPSYSTEMNAME=MES
    -> arg[ 51]: -DSAPMYNAME=solman_MES_00
    -> arg[ 52]: -DSAPDBHOST=solman
    -> arg[ 53]: -Dj2ee.dbhost=solman
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 4404] JHVM_LoadJavaVM: Java VM created OK.
    [Thr 5488] Mon May 17 23:39:30 2010
    [Thr 5488] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 5488] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 5488] Mon May 17 23:39:32 2010
    [Thr 5488] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.engine.Compress
    [Thr 4440] Mon May 17 23:39:38 2010
    [Thr 4440] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 4440] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.

    Basis Guy,
    I followed your instructions, and the problem still exist.  Per note 908911, I added "SAP_BC_JSF_COMMUNICATION" role to the SAPJSF user in the backend ABAP system.  I've tried starting and stopping
    the System through SAP MMC, and I see the following (solman is our hostname):
    solman 0 - The AS ABAP work processes start sucessfully,  the AS Java processes, show three processes, with two in the stopped state:
    1) SDM - state is stopped
    2) Dispatcher - state is running
    3) server0 - state is stopped, with a return code of -11113
    solman 1 - shows 2 processes
    1) Msg Server - running
    2) Enqueue Server - running
    From SAP MMC, I look at the Developer trace for the 2 stopped processes (SDM and server0).  This brings up the dev_server0 log, and the dev_sdm log.  In both files, I see the following error:
    [Thr 3712] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\MES\DVEBMGS00\exe\jvmx.jar
    When I look for this file, it does not exist.  Is this my problem, and where does this file come from during the install?
    From the Syslog of SAP MMC, I see three errors when starting the system, in this order:
    Process Type: DP Message ID: GZZ
    SAP-Basis System: > 1 possible network problems detected - check tracefile and adjus
    Process Type: RD Message ID: Q01
    SAP-Basis System: Operating system call           recv failed (error no. 10054)
    Process Type: D0  Message ID:  R49  User: SAPJSF Client: 001
    SAP-Basis System: Communication error, CPIC return code 020, SAP return code 223
    Also, I see the following error in the defaulTtrace.0.trc file:
    #com.sap.security.core.server.secstorefs.FileIOException: I/O error on file "
    solman
    sapmnt
    MES
    SYS
    global
    security
    data
    SecStore.properties".
    java.io.FileNotFoundException:
    solman
    sapmnt
    MES
    SYS
    global
    security
    data
    SecStore.properties (The requested operation cannot be performed on a file with a user-mapped section open)
    However, I see that this file does exist, but what does it mean "a user-mapped section is open"?
    As for the configtool, Global Server Configuration, when I look for all instances of J2EE_GUEST or SAPJSF, only two parameters show up:
    ume.login.guest_user.uniqueids = J2EE_GUEST
    ume.r3.connection.master.user = SAPJSF
    Looking in the ABAP System (via SU01), I see that J2EE_GUEST shows password deactivated.  Is this correct?
    Please advise.
    Rick
    Sunny,
    Not sure what you mean by update the latest logs from sapinst.log.   I've displayed the sapinst.log in the original post.  I may just be misunderstanding your request. 
    Let me know if there is more info that you need.

  • Recommended patch 120445-01 will not install with Sol. 9 (09/2005)

    Patch 120445-01 will not apply to a Solaris 9 (09/2005) setup. The hardware is an Ultra-80. Although it is recommended, it fails with the "patchadd" message:
    Checking installed patches...
    One or more patch packages included in 120445-01 are not installed on this system.
    The host was installed from scratch and the "smpatch" was run until it had no more patches to apply except this one.
    For us, this patch is only an annoyance. When I cursorily read the description, I doubt that these features exists on this hardware.

    I had to install the packages:
    TSBWvplr.u
    TSBWvplu.u
    from the DVD media. I could not find these packages from the CD media that I used. I had to use another machine to extract the packages.
    I saw another post where it mentioned that patch 120445-01 would not apply. I suspect that the package install of it already has this patch.

  • SIMS server can install on Sol 8 x86 or not?

    I tried it...I solve the ldap installation and some patch problem...
    But finally I cannot resolve error no ldaadmser in java.library.lang...
    I try many method...to include the path where libldaadmser.so is existing...
    But still can not finish the Installation...
    And the script finally said it can not found the Message Store configuration file...
    What can I do? Is that because I am installing it on Solaris 8?

    Looks like SIMS 4.0 is for Solaris 2.6 and Solaris 7. I believe the product has migrated to iPlanet Messaging Server 5.x. You may want to post a query in the iPlanet forum. http://supportforum.sun.com/iplanet/

  • Solaris 10 on Netra T1 install issues....

    I have gentoo installed on my netraT1 (which is apparently in the sun4u Platform Group) it has a 500mhz UltraSparc IIe processor and 1Gig of RAM.
    I decided to try solaris 10 so I downloaded all the cd images to my winows machine and used nero to burn them all. I put the first one in and typed boot cdrom and got a panic:
    ok boot cdrom
    Boot device: /pci@1f,0/pci@1,1/ide@d/cdrom@0,0:f File and args:
    Short read. 0x0 chars read
    krtld: error during initial load/link phase
    panic - boot: exitto64 returned from client program
    Program terminated
    Ok
    Here is some more info:
    ok probe-scsi
    Target 0
    Unit 0 Disk SEAGATE ST318305LSUN18G 0340
    Target 1
    Unit 0 Disk SEAGATE ST34371W SUN4.2G7462
    Firmware CORE Release 1.0.12 created 2002/1/8 13:0
    Release 4.0 Version 12 created 2002/01/08 13:01
    cPOST version 1.0.12 created 2002/1/8
    CORE 1.0.12 2002/01/08 13:00
    Is there anything I could do to get this install to work? This is my only sun machine so I dont think I could get netbooting to work. I tried burning the first cd 2 times just to make sure it wasnt my burner and it still was getting the same errors ;(
    Thanks,
    Ryan

    I have no really good answer here..
    I guess you are using a Netra T1 AC200, right?
    Some futher questions;
    Are you using an internal CD-Rom?
    Have you tried the CD-Rom before so you know it works?
    What happens if you try "boot cdrom" without inserting any CD? I think the bootpath to the cd-rom looks a bit strange, and testing that would be the easiest way of verifying if its correct or not. If the path is correct you should get a different error if you attemt to boot from a non-existing CD.
    Last question; which Solaris 10 version did you download?
    7/M.

  • Installing solaris 10 on netra t1 105

    im need to sun computer system....i have got to the point of hyperterm lom> and booting the system, but it has no software installed.. im trying to install solaris on a sun netra t1 105 256 mb ram and 19gb hd and NO CDROM im trying to "network install" from a windows 2003 server.. is this possibly or do i have to a sun workstation to install as boot/install server... or could i connect the hard drive to a windows 2003 server and format and install solaris on it using virual pc.... i haveit networked to my wireless router as well a x86 computer...
    Edited by: lebaronman on Feb 28, 2008 2:01 AM

    I have no really good answer here..
    I guess you are using a Netra T1 AC200, right?
    Some futher questions;
    Are you using an internal CD-Rom?
    Have you tried the CD-Rom before so you know it works?
    What happens if you try "boot cdrom" without inserting any CD? I think the bootpath to the cd-rom looks a bit strange, and testing that would be the easiest way of verifying if its correct or not. If the path is correct you should get a different error if you attemt to boot from a non-existing CD.
    Last question; which Solaris 10 version did you download?
    7/M.

  • Netra T1 booting problems, works only if I "boot disk"

    I'm having a problem booting my Netra T1 AC200. When I issue the "poweron" command from the LOM or when I issue the "reset" command from the ok prompt, the system fails to boot, gives me an error, and drops back to the ok prompt. However, if I type "boot disk" at the ok prompt, the system will boot just fine. I have tried playing with setenv, but eventually returned all of those values to their defaults. I have a fresh install of Solaris 9.
    The error message and the output of printenv are below.
    Thank you in advance!!
    LOM event: +1h36m0s host reset
    Resetting ...
    Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
    OpenBoot 4.0, 1024 MB memory installed, Serial #51329155.
    Ethernet address 0:3:ba:f:38:83, Host ID: 830f3883.
    000000000000001500000000f000000000000000000000000000000000000000ffffffffd3858020000000000000000d00000004
    Watchdog Reset
    Externally Initiated Reset
    ok
    ok printenv
    Variable Name Value Default Value
    ras-shutdown-enabled? false false
    shutdown-temp 75 75
    warning-temp 70 70
    env-monitor disabled disabled
    diag-passes 1 1
    diag-continue? 0 0
    diag-targets 0 0
    diag-verbosity 0 0
    keyboard-click? false false
    keymap
    scsi-initiator-id 7 7
    #power-cycles 0 No default
    system-board-serial# No default
    system-board-date No default
    ttyb-rts-dtr-off false false
    ttyb-ignore-cd true true
    ttya-rts-dtr-off false false
    ttya-ignore-cd true true
    ttyb-mode 9600,8,n,1,- 9600,8,n,1,-
    ttya-mode 9600,8,n,1,- 9600,8,n,1,-
    pcia-probe-list 8,5,6,7 8,5,6,7
    pcib-probe-list 7,c,3,d,5 7,c,3,d,5
    mfg-mode off off
    diag-level max max
    fcode-debug? false false
    output-device ttya ttya
    input-device ttya ttya
    load-base 16384 16384
    auto-boot-retry? false false
    boot-command boot boot
    auto-boot? true true
    watchdog-reboot? false false
    diag-file
    diag-device net net
    boot-file
    boot-device disk net disk net
    local-mac-address? false false
    net-timeout 0 0
    ansi-terminal? true true
    screen-#columns 80 80
    screen-#rows 34 34
    silent-mode? false false
    use-nvramrc? false false
    nvramrc
    security-mode none No default
    security-password No default
    security-#badlogins 0 No default
    oem-logo No default
    oem-logo? false false
    oem-banner No default
    oem-banner? false false
    hardware-revision No default
    last-hardware-update No default
    diag-switch? false false
    ok

    The drive is disk0 on my Netra T1 AC200. Typing "boot disk" results in the system booting just fine. "reset-all" or "poweron" causes the error described above. My aliases are as follows:
    ok devalias
    lom /pci@1f,0/pci@1,1/ebus@c/SUNW,lomh@14,200000
    dload /pci@1f,0/pci@1,1/network@c,1:,
    net2 /pci@1f,0/pci@1,1/network@5,1
    net /pci@1f,0/pci@1,1/network@c,1
    diskx /pci@1f,0/pci@1/scsi@8,1/disk@0,0
    diskx3 /pci@1f,0/pci@1/scsi@8,1/disk@3,0
    diskx2 /pci@1f,0/pci@1/scsi@8,1/disk@2,0
    diskx1 /pci@1f,0/pci@1/scsi@8,1/disk@1,0
    diskx0 /pci@1f,0/pci@1/scsi@8,1/disk@0,0
    scsix /pci@1f,0/pci@1/scsi@8,1
    disk /pci@1f,0/pci@1/scsi@8/disk@0,0
    disk3 /pci@1f,0/pci@1/scsi@8/disk@3,0
    disk2 /pci@1f,0/pci@1/scsi@8/disk@2,0
    disk1 /pci@1f,0/pci@1/scsi@8/disk@1,0
    disk0 /pci@1f,0/pci@1/scsi@8/disk@0,0
    scsi /pci@1f,0/pci@1/scsi@8
    cdrom /pci@1f,0/pci@1,1/ide@d/cdrom@0,0:f
    ide /pci@1f,0/pci@1,1/ide@d
    ttyb /pci@1f,0/pci@1,1/isa@7/serial@0,2e8
    ttya /pci@1f,0/pci@1,1/isa@7/serial@0,3f8

  • Silly question regarding sol 8 containers and disk sizes

    I've got what is probably just about the silliest question, but I can't seem to find an answer whilst searching around for the past couple of hours. Say I have 2 boxen, one is a sol 8 server and the other is a brand new install of sol 10/8. They have the exact same hardware, including disk size. If I want to turn the first box into a solaris 8 container running under the second, how do I reconcile the fact that the disk sizes are the same? The sol 8 box is only using, say, 25-30GB of the 72GB on the disk. Do I have to resize the slice into something smaller to enable it fit into a container on the second server? It would seem that is the case, but I didn't know if there was some magic I was not aware of. I've not done a ufsdump or flash archive before so I don't know if the 'empty' space on the disc will be disregarded, possibly allowing me to squeeze it onto my sol 10 server and allow me to resize it smaller in zfs. This topic isn't touched in all the tutorials I've read, so I assume it's either a completely retarded/braindead concern, or everyone always migrates these boxen onto servers with much more in the way of resources.
    Sorry if I offended anyone with my ignorance ; P

    No. Solaris8/9 containers make use the "branded zones" technology. But it's still the same thing and there's no "disk image", at least not like you might think of for VMware or Xen.
    Now if you want to call a ufsdump or flash archive an "image", then that's fine. But you can see in either case, the free space or minor changes is size are irrelevant. You're just copying files. It's a system image, not a "disk image".
                      Installer Options :
                            Option          Description
                            -a filepath     Location of archive from which to copy system image.
                                            Full flash archive and cpio, gzip compressed cpio,
                                            bzip compressed cpio, and level 0 ufsdump are
                                            supported. Refer to the gzip man page available in the
                                            SUNWsfman package.--
    Darren

  • Netra t1 200 diag light

    I have a older netra t1 with the diag lights on amber in the front.
    i did a prtdiag and it does not show any faults..
    <div class="pre"><pre>System Configuration: Sun Microsystems sun4u Netra T1 200 (UltraSPARC-IIe 500MHz)System clock frequency: 100 MHzMemory size: 2048 Megabytes========================= CPUs ========================= Run Ecache CPU CPUBrd CPU Module MHz MB Impl. Mask--- --- ------- ----- ------ ------ ---- 0 0 0 500 0.2 13 1.4========================= IO Cards ========================= Bus# FreqBrd Type MHz Slot Name Model--- ---- ---- ---- -------------------------------- ---------------------- 0 PCI-1 33 12 ebus 0 PCI-1 33 3 pmu-pci10b9,7101 0 PCI-1 33 3 lomp 0 PCI-1 33 7 isa 0 PCI-1 33 12 network-pci108e,1101 SUNW,pci-eri 0 PCI-1 33 12 usb-pci108e,1103.1 0 PCI-1 33 13 ide-pci10b9,5229 0 PCI-1 33 5 network-pci108e,1101 SUNW,pci-eri 0 PCI-1 33 5 usb-pci108e,1103.1 0 PCI-2 33 8 scsi-glm Symbios,53C896 0 PCI-2 33 8 scsi-glm Symbios,53C896 No failures found in System===========================</pre></div>
    is there any way to reset the diag lights ? or any other ways of finding a problem other than prtdiag ?
    Thanks

    Have you used lom?
    #. should get you to lom> prompt
    lom> environment
    or
    lom> check
    Once you see what is faulty or repair it then you can
    lom> faultoff
    lom> console
    will get you back to Solaris.
    Chapter 8 in the Netra T1 AC200 and DC200 Server User's Guide has great info on LOM - Lights Out Management Looks like manual is only available to contract sunsolve users:
    http://sunsolve.sun.com/handbook_private/Systems/Netra_T1_AC 200_shared/docs.html
    This assumes you have SUNWlomr, SUNWlomu & SUNWlomm packages loaded & patched.

  • Sol Manager 4.0 Installation: java_home not available

    Hi,
    We are facing some problems when installing a sol manager 4.0 on a Windows 2003 Server SP 64bits.
    The Environment variables are ok as we can see... ther SDK version is 1.4.2_16 downloaded from the SUN website.
    "Error:
    condition: JAVA_HOME
    Result Code: Could not check
    Severity: HIGH
    Message: It is not recomended to use JDK version 1.4.2_10. Current version: JAVA_HOME not available. See also SAP Note 867110 (updated 2006-06-12)
    Can someone help us?
    Thank you very much,
    João Durã

    Hi,
    Please navigate to:
    Java Installation directory/bin folder
    and execute java -v command on windows console. If you have installed it successfully, it should be executed properly and should show currently installed Java version.
    If you got proper results, then please set JAVA_HOME variable to the above directory path.
    Or else, you can also mention the above Java path in PATH variable.
    Please let me know if it  helped.
    Regards,
    Faisal

  • SAP Sol Mgr 4.0 Upgrade to 7.0 Enterprise Edition

    Hi,
    I have installed SAP Sol Mgr 4.0 SR3. Now I want to upgrade to SOl Mgr 7.0 Enterprise Edition.
    What are the steps I need to follow.
    Regards,
    B

    Hi Neshimi,
    Thanks for your reply. Points assigned.
    I actually installed Sol Mgr 4.0 SR3.  In your reply you mentioned it same as Sol Mgr 7.0 SR3.
    Is the Sol Mgr 7.0 EHP1 same as Sol Mgr Enterprise Edition?
    Please let me know the steps I need to follow to upgrade to Enterprise Edition. I understood your reply partly.
    Please be more clear so that I can understand easily.
    What are the patches or updates I need to download. How to Upgrade after I download the files.
    The reason why I installed Sol Mgr 4.0 SR3 first is I have the license for it. Is the upgrade free for the next version?
    Regards,
    B
    You can also install ETP as a add-on
    check #1109650 and:
    #1140258:
    2. Prerequisites for the installation
    You require SAP Solution Manager 7. 0 SP15 to SPS 17. With SPS 18 (identical to EHP 1) it is automatically activated. The steps described further down are not required.
    3. Preparing for the installation
    4. Executing the installation
    Download the SAP Solution Manager Extension Add-on ST-ETP from SAP Service Marketplace. For details see note 1109650.
    Install the Add-on in your Solution Manager
    5. After the installation
    To activate SAP Solution Manager Enterprise Edition, the Enterprise Addon SM_APPLM has to be activated in the IMG of the Solution Manager System. This is done via IMG activity SAP Solution Manager->Configuration->Scenario-Specific Settings->Activate Solution Manager Enhancements.
    a) In the case of ST-400 SP15-SP17
    To use Extended Tracebility in Change Request Management activate BC-Set SOLMAN40_CHARM_CONTEXT_001 in transaction SCPR20
    b) In the case of ST-400 SP18 or higher
    The activation of BC-Set SOLMAN40_CHARM_CONTEXT_001 will be done automatically.
    Please also note that your Solman 4.0 SR3 is similar to SolMan 7.0 SR3. The name has just changed in order to matchup with the Netweaver naming convention
    Nesimi

  • Use Sol8 intel as install server for NetraX1. possible?

    I spend several days trying to reinstall the Solaris 8 10/01 into my brand new Netra X1 server. but no luck.
    this is my first and only sparc server. i'm using Solaris 8 intel as install server and install the netra drivers...
    my question is:
    is it possible to using Solaris 8 intel as install server for Netra X1 net install?
    I don't think i will buy one more sparc machine in this reason.
    Chris

    Yes, you can use an X86 box to install Solaris Sparc to a Netra X1.
    First, you must be using InfoDoc 26310 ( available on SunSolve).
    In between steps 6 & 7 of that procedure you must do the following:
    After applying the mis.netra-x1.259-3836-03 script you will need to add the dmfe driver to the boot image served out by your jumpstart server. This is done at the shell prompt as root. Please note that in the example below the root image is located at: /jumpstart/2.8/sparc_1001/Solaris_8/Tools/Boot
    on the example server. This location will vary depending on the setup of your server. The example is used to illustrate the point that you must specify the whole path all the way to the alternate root that is served across the network to your client. The sample command line is:
    # add_drv -b /jumpstart/2.8/sparc_1001/Solaris_8/Tools/Boot -m "* 0600 root sys" -i '"pci128h,9102" "pci1282,9102" "ethernet"' dmfe
    This can also be broken out using backslashes as follows:
    # add_drv -b /jumpstart/2.8/sparc_1000/Solaris_8/Tools/Boot \
    -m "* 0600 root sys" \
    -i '"pci128h,9102" "pci1282,9102" "ethernet"' dmfe Note that the ">" symbols will be added as you hit return after each "\".
    The above procedure must be done to each boot image you wish to install. For example, if you have a 10/2001 image and a 01/2001
    image that you use for different configurations, you will need to add the dmfe driver to both .../Solaris_8/Tools/Boot directories.
    Proceed with step 7 and beyond in the procedure from Info Doc 26310 to complete your installation.

Maybe you are looking for