Difference b/w support pack ,plugin nd path level nd how to recognise them

Hello Experts,
I have one question?
How to recognize Wt is Support package, wt is add on or Plug in ,and wt is patch level , what is the difference between them all and how to trace them and where from to apply them .
Requestd to revert at earliest,my email id is [email protected]
Regards,
Somya

Hi Somya,
Support packs are the corrects to the SAP objects , we have to apply through SPAM where as SAINT will be used to install plugins and Add-ons. where are the patch level never play in your SAP.. it play between your operating system and SAP system.. that means the binary level fix.
I just tried to differentiate all the three things.
Please award points if i answered your question.
kind regards
Balamuralikrishnan.A

Similar Messages

  • Difference between HR support packs and EHP.

    Can anyone tell me the difference between HR support packs and EHP

    Hi Harish,
    Enhancement Packages-  SAP enhancement packages for SAP ERP are optionally installed software innovations for SAP ERP 6.0. They include functional enhancements, industry specific functionality, and simplifications u2013 for example, to the user interface. With enhancement packages, you can easily adopt ongoing SAP innovations at a lower cost than full upgrades. In addition, enterprise services are delivered with enhancement packages.
    Support Pack  - If the same or similar bug is reported by multiple clients or end users, then SAP recognizes such bug corrects them and collects all these corrections in one place and adds some enhancements to the earlier version of SAP and then calls this as a SUPPORT PACK. In simple words collection of  SAP NOTES is a SUPPORT PACK.
    Enhancement packages are not support packages: Support Packages contain corrections and legal changes, SAP enhancement packages new functionality.
    Do let me know if I helped you.
    Thanks,
    Padmaja.

  • SAP_HR Support Pack.

    Hi Team:
    Currently  our  SAP_HR  support pack is SAPKE60017 we are  a part of payroll international.
    We would seriously planning for the  enhancement of the support pack to the  latest level:
    We need  information for the below query  to process further  on this, anybody  faced similar kind of problem can  extend  their co operation:
    1.What would be the Exact impact on other sub modules especially
    FICO once HR support pack is enhanced to the latest u2013 ECC
    6.0/ECC 6.X including enhancement packs.
    2.With the enhancement of latest  support pack, what are the
    additional features can be availed in other sub modules of HR domain
    along with core Payroll.
    3. Can the latest support pack be directly implemented or need to be
    implemented in a sequence to reach the latest pack.
    After SAP big release i. e ECC 6.0, now SAP is releasing
    Enhancement packs (Eg :Like ECC 6.2 ).
    Now I would like to seek a clarifications that if we would like to
    implement latest enhancement pack to fully utilize the
    new functionalities/features , do we need to implement first latest support pack
    till ECC 6.0 release  followed by  latest enhancement  pack
    (ECC 6.2)  implementation..
    Let me know what are the latest support pack pertaining to ECC 6.0 /
    ECC 6.2.need to be implemented in order to have latest SP/EP in the system.
    Looking forward  for a positive reply.
    Regards
    Team Member
    Edited by: Patlolla Mallikarjun on Aug 11, 2009 11:01 AM

    No comments

  • Support Pack upgrade path

    We recently upgraded from ECC 6.0 support pack 9 to support pack 15. At the same time, we installed EHP4 support pack 5. A few questions:
    1. Will we upgrade our ECC 6.0 support pack 15 system to the next support pack, for example  to support pack16 or 17, OR will our support packs follow the EHP4 support pack update path, for example upgrading our current environment by moving from EHP4 support pack 5 to support pack 6?
    2. We have not yet enabled any of the new EHP4 functions in our landscape. Is it recommended that if we upgrade EHP4 support pack 5 to support pack 6 we do a full integration test? If we haven't enabled any EHP4 support pack 5 functions, I wasn't sure if an integration test was needed.
    thank you,
    Jonathan

    Hello Jonathan,
    I hope you are aware of SPDD/SPAU.
    Point to be notes is support package will not overwrite your own customizing (Z, Y).
    and if you modified any Standard object for your purpose and its been overwritten by the Support package then you will definately get a prompt in SPDD and SPAU and you have a chance to take decision how would you like to go. whether you want to keep your customizing to the standard objects or you want the new standard code to overwrite it.
    So, you will not need to do integration testing for complete things in your system.
    Let me know if you need more clarifications.
    Best Regards
    Niraj

  • Difference Between Patches And Support Packs

    Hi Experts,
    I have one doubt,
    1.... I want to Know Difference Between the Patches And the Support Packs
    2...What is the Use of these Two??????????Is it Necessary to Apply these Two??
    I asked This Question in Number of Queries...................
    Please Let me Know All the Above Mentioned Queries
    Regards
    Khanna

    Thank you  for ur Quick Reply Satish.
    And one more thing i want to clarify with you ...
    Here i am going to Install XI 3.0 with WAS 6.20.
    1......I installed j2sdk1.4.2_12
    2......Installed Oracle 9i
    <b>Question1:-</b> Do i need to Patch it to Oracle 9.2.0.7.0?????????
                              Or I can do it Later Also???????(At Present I dont Have it)
    I Installed Up to Here.
    3.....After this I wil  Install WAS 6.20 with ABAP + JAVA Stack
                                                                      ( I have Doc for this).......
    4....After this I wil Install XI 3.0
    I think this is the XI Installtion.....
    <b>Question2:-</b> Is this way of Installation is Correct?????
    <b>Question3:-</b>After Completion of All these We should do the XI Post Installtion...Right?????
    <b>Question4:-</b>  When can we Apply the Support Packs And Patches??????? In the Post Installation  Or After the Post Installation?????
    Please Give me the Right Direction To Install the XI Successfully.......
    Helpful ANS Wil be REWARD Points
    Regards
    Khanna

  • Difference between Support Stacks & Support Packs

    Hi All,
    Just the general question.
    Difference between Support stacks & Support Packs? Please explain.
    Thanks you all.

    You can find all the products existing into CRM in the PeopleSoft Enterprise CRM 9 Product-to-PeopleBook Index, with the name of each linked Peoplebook to refer on the main CRM Peoplesoft documentation page.
    And especially the PeopleSoft Enterprise CRM 9 Call Center Applications PeopleBook about Support and HelpDesk features.
    Nicolas.

  • Difference between service pack and support pack

    Hi,
    what is the exact difference between service pack and support pack. Are they same?
    The version details presnt in integration builder -> help-> inforamtion  of my XI server are as follows :
    Service pack: 09
    Release: 645_VAL_REL
    does it mean that the both support package and service package for my XI server are 09?
    thanks in adavance
    regards
    Jagruthi

    1. A service pack (in short SP) is a collection of updates, fixes and/or enhancements to a software program delivered in the form of a single installable package. Service packs are usually numbered, and thus shortly referred to as SP1, SP2, etc. It is notable that they may bring, besides bug fixes, entirely new features.
    http://help.sap.com/saphelp_nw04/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
    Service packs in 2004 and 2004s;
    in 2004 - in 2004s
    SP12 & < - SP04 http://XI 3.0
    SP13 + 14 - SP05 http://PI 7.0
    SP15 - SP06
    SP16 - SP07
    SP17 - SP08
    SP18 - SP09 and so on...
    2) Support pack -
    http://help.sap.com/saphelp_nw04s/helpdata/en/9e/5bc53f3e0f0228e10000000a114084/frameset.htm
    For the ABAP parts of usage type PI, this is the implementation of support packages. For the Java parts, the deployment with the Java Support Package Manager (JSPM) is used.
    You can find currently available support packages on SAP Service Marketplace at service.sap.com/sp-stacks.
    A description of how to apply support packages is available in SAP Note 879289.

  • Difference between Hot Pack and Support Pack

    Hello,
    Can anyone throw some light on difference between Hot Pack and Support Pack(if there is any) and what is Tax Update Bulletins, do we need to configure for TUBs or what is the SAP HR consultants role is Tubs.
    Thanks
    Charlene

    Hi,
    I believe both (hot pack and support pack) are one and the same.
    For TUBS, you can find more information in:
    Service Marketplace -> SAP ERP Human Capital Management -> Country Info -> North America -> United States -> Tax Update Bulletins -> Tax Factory 8 -> Tub Downloads
    Hope this helps,
    Reward points if helpful,
    Thank You,

  • MIDDLEWARE ( R/3 Plugin support pack details)

    Hi Experts,
    We have to integrate CRM5.0 with R/3 4.7. Can anybody tell me the version of the PI( plug-in) support package, which has to be installed at R/3.
    Points will be rewarded.
    Thanks in advance
    Nadh.

    Hi Eric,
    Thanks for your support.
    I have gone through the SAP note 672651 - OCS: Known problems with Support Packages in Basis Rel.6.40 and did a analysis of steps to install BW 3.5 support packs
    1.Logon to client 000 with superuser having full authorisaton (i.e SAP_ALL and SAP_NEW)
    2.Update SPAM/SAINT Version
    3.Install PI_Basis 2005_1_640 with SAINT tcode
    4.Install SAP_BASIS support packs with SPAM
      SAPKB64013---SAPKB64014
      SAPKB64015---SAPKB64018
      SAPKB64019---SAPKB64021
    5.Install SAP_ABA support packs with SPAM
      SAPKA64013---SAPKA64014
      SAPKA64015---SAPKA64018
      SAPKA64019---SAPKA64021
    6.Install PI_Basis 2006_1_640 with SAINT
    7.Install SAP_BW Support packs
      SAPKW35013---SAPKW35014
      SAPKW35015---SAPKW35018
      SAPKW35019---SAPKW35021
    Our BW 3.5 system is having SAP_Basis SAPKB64012 as current level and SAP_BW SAPKW35012
    as current level.
    Please let me know is the queue defined for Basis,ABAP and BW Supports packs is ok.
    Regards,
    Anil.

  • Error in JSPM Support Pack update

    Hi,
    i am in the process of doing java support packs form level 9 to 14.
    I am doing 3 at a time
    After the sap-jee support pack got deployed the server0 for j2ee is not starting.
    Pls hlep
    The following is the log of disp_server0
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 7296
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:30:40 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 4660] Tue Jun 17 16:30:40 2008
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 4660] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4660] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 6916] JLaunchRequestFunc: Thread 6916 started as listener thread for np messages.
    [Thr 4836] WaitSyncSemThread: Thread 4836 started as semaphore monitor thread.
    [Thr 4660] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 4660] CPIC (version=700.2006.09.13)
    [Thr 4660] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 4660] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> 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
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 4660] JLaunchISetDebugMode: set debug mode [no]
    [Thr 6772] JLaunchIStartFunc: Thread 6772 started as Java VM thread.
    [Thr 6772] [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]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=7296
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 6772] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 4752] Tue Jun 17 16:30:41 2008
    [Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4752] JLaunchISetClusterId: set cluster id 13786450
    [Thr 4752] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4752] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 7688] Tue Jun 17 16:30:52 2008
    [Thr 7688] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 7688] ***********************************************************************
    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.*
    [Thr 7688] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 4560
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:30:55 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 5300] Tue Jun 17 16:30:55 2008
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 5300] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5300] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 7140] JLaunchRequestFunc: Thread 7140 started as listener thread for np messages.
    [Thr 6892] WaitSyncSemThread: Thread 6892 started as semaphore monitor thread.
    [Thr 5300] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5300] CPIC (version=700.2006.09.13)
    [Thr 5300] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 5300] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> 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
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 5300] JLaunchISetDebugMode: set debug mode [no]
    [Thr 6352] JLaunchIStartFunc: Thread 6352 started as Java VM thread.
    [Thr 6352] [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]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=4560
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 6352] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 5836] Tue Jun 17 16:30:56 2008
    [Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 5836] JLaunchISetClusterId: set cluster id 13786450
    [Thr 5836] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 5836] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 6128] Tue Jun 17 16:31:06 2008
    [Thr 6128] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 6128] ***********************************************************************
    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.*
    [Thr 6128] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 8152
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:31:10 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 6468] Tue Jun 17 16:31:10 2008
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 6468] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 6468] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 7576] JLaunchRequestFunc: Thread 7576 started as listener thread for np messages.
    [Thr 7312] WaitSyncSemThread: Thread 7312 started as semaphore monitor thread.
    [Thr 6468] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 6468] CPIC (version=700.2006.09.13)
    [Thr 6468] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 6468] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> 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
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 6468] JLaunchISetDebugMode: set debug mode [no]
    [Thr 7456] JLaunchIStartFunc: Thread 7456 started as Java VM thread.
    [Thr 7456] [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]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=8152
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 7456] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 7648] Tue Jun 17 16:31:11 2008
    [Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 7648] JLaunchISetClusterId: set cluster id 13786450
    [Thr 7648] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 7648] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 7432] Tue Jun 17 16:31:21 2008
    [Thr 7432] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 7432] ***********************************************************************
    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.*
    [Thr 7432] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 7280
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:31:25 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 5400] Tue Jun 17 16:31:25 2008
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 5400] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5400] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 4264] WaitSyncSemThread: Thread 4264 started as semaphore monitor thread.
    [Thr 4488] JLaunchRequestFunc: Thread 4488 started as listener thread for np messages.
    [Thr 5400] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5400] CPIC (version=700.2006.09.13)
    [Thr 5400] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 5400] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> 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
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 5400] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4872] JLaunchIStartFunc: Thread 4872 started as Java VM thread.
    [Thr 4872] [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]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=7280

    We installed teh objects through SDM .
    this solved the issue

  • Support Pack upgrade error in Import Phase

    Hello,
    Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
    Could you please help me on this? I tried and still searching solution for this..But no luck...
    Os is : AIX and
    Log File:                /usr/sap/trans/log/SAPIB70013.xxx
    Main import
    Transport request   : SAPKB70013
    System              : xxxx
    tp path             : tp
    Version and release: 372.04.71 700
    child process 934006 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_OBJECT_COLLECTION==========CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1212554 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDR_APPLICATION_WINDOW=====CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1171520 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_EVENT_SOURCE========CI
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1331412 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    insert / update sequence failed due to an error in DBI.
    maybe there's a concurrent process which inserted this table entry at the same time.
    insert / update sequence failed due to an error in DBI.                       
    maybe there's a concurrent process which inserted this table entry at the same time.
    child process 1310922 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_END
    tabname:    WDY_APP_PROPERTY
    len (char): 64
    key:        DEMO_UIEL_DROPDOWN_BY_IDX     DEMO_VIEW
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 018446 - 999999 not imported because the child processes died for unknown reason
    child process 1310924 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_OUTGOING_EVENT======CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1286192 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 009158 - 018411 not imported because the child processes died for unknown reason
    import portion 018412 - 018527 not imported because the child processes died for unknown reason
    import portion 018528 - 999999 not imported because the child processes died for unknown reason
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    Main import
    End date and time : 20100909034914
    Ended with return code:  ===> 12 <===
         |   ######################################                     
    Thanks and Regards,
    Sankar
    SAP BASIS Consultant

    Hi,
    Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
    Runtime Errors         CALL_FUNCTION_NOT_FOUND
    Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
    Date and Time          10.09.2010 09:41:37
    Short text
         Function module "POSS_UIREQ_OPT_SUBMIT" not found.
    What happened?
         The function module "POSS_UIREQ_OPT_SUBMIT" is called,
         but cannot be found in the library.
         Error in the ABAP Application Program
         The current ABAP program "SAPLSTXC" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
          not caught in
         procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         The program "SAPLSTXC" contains the CALL FUNCTION statement.
         The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
         No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
         All function modules are listed in the Function Library (SE37).
    Possible reasons:
    a) Wrong name specified. Pay particular attenti
        upper/lower case and underscores ("_").
        or
    b) Transport error
    c) In the case of an enqueue/dequeue module,
        the lock object may not have been activated
        (ABAP/4 Dictionary).
    When i tried to check function module it is not there..
    Could you please help on this?
    Regards,
    Sankar Basis Consultant

  • SB Audigy Series Support Pack 3.1 (OUTDATED)

    <p align="center">[color="#ff0000"]This software/driver pack is unofficial, not supported by Creative Labs.
    <p align="center">[color="#ff0000"]Use it at your own risk.
    Supports any model of the following?Sound Blaster cards (based on Emu0kx DSP):
    - Audigy
    - Audigy 2
    - Audigy 2 ZS
    - Audigy 4
    For?Audigy SE/LS/Value and Li've! 24-bit cards, <a target="_self" rel="nofollow" href="http://forums.creative.com/creativelabs/board/message?board.id=soundblaster&thread.id=4440"]click here for a compatible version[/url].
    Operating systems supported: 32-bit and 64-bit editions of Windows 7?RTM
    ?Vista?SP2 / XP SP3
    Included in the pack:?
    - Audigy series driver 2.8.00.8 (latest beta)
    - ALchemy .30.00
    - Audio Console .32.02
    - DDL and DTS Connect License Activation 2.00.03 (*)
    - Dolby Digital Li've Pack 3.00.03 (*)
    - DTS Connect Pack .03.04 (*)
    - EAX Console 3.00.56 (Windows XP only)
    - Graphic Equalizer 2.00.65
    - MediaSource DVD-Audio Player 2.00.78
    - SoundFont Bank Manager 3.2.00
    - Speaker Settings 2.00.60
    (*) Purchase and activation required, more info at http://buy.soundblaster.com.
    Does this driver improve sound quality or performance? Are there any tweaks?
    No, this driver does not improve sound quality nor increase performance.
    No, there are no tweaks.
    If someone states that its driver improves sound quality and performance, you are being fooled, cheated.
    It is even worse that the so called tweaks come from a person who is not EVEN technically acknowledged, does NOT know anything about Windows internals, software engineering and?sound?fidelity that all audiophiles always look for.
    If you "feel" the sound better, that is the infamous placebo effect and there is no real proof that any tweaks work.
    In fact, I have yet to see a driver that states in its release notes that it improves sound quality.
    I've disassembled about every single .SYS driver, .DLL libraries and .EXE executables and found nothing.
    There are some undocumented registry values, but nothing related to sound quality or performance.
    Would the so called tweaks even exist, they would be in my Support Packs, you can bet that.
    [img"]http://brztech3.googlepages.com/audcondts.png" height="530" alt="Audio Console: DTS Interacti've in Encoder tab[/img] width="44">[img"]http://brztech3.googlepages.com/spkmshte.png" height="46" alt="Microsoft Audio Home Theater Effects for Speakers[/img] width="44">[img"]http://brztech3.googlepages.com/spdifmshte.png" height="46" alt="Microsoft Audio Home Theater Effects for S/PDIF Out[/img] width="44">
    Fixes and improvements:
    - Enables support for?WASAPI exclusi've-mode event-dri'ven playback, seems to be working just fine
    - Fixes the enhancements errors in Windows?mixer and Windows Media Player.
    - Adds Microsoft Audio Home Theather Effects for both Speakers and S/PDIF Out endpoints.
    - Includes Encoder Switcher to enable DTS Interacti've on Audigy cards.
    - Fixes the Audio Console "Internal application error" when enabling the DDL Encoder on localized installs.
    - Updates Audio Console to display DTS Interacti've in the Encoder tab when Encoder switcher is used.
    - Workarounds a bug that?unexpectedly resets the?speaker configuration.
    - Prevents an issue during installation on Windows 7/Vista that may result in low volume when certain enhancements are enabled.
    - Implements Hardware CMSS Headphone by using a workaround.
    - Updates all InstallShield setup scripts to support Windows 7.
    - Fixes installation INI to properly install applications depending on the detected OS.
    - Removes COM workaround for Equalizer, fixed by Creative.
    - Adds workaround to a memory corruption issue preventing Equalizer from starting on Windows 7/Vista.
    - Updates shared modules, responsi'veness on certain applications is improved.
    - Enables CMSS2 and Stereo Surround.
    - Fixes 32-bit ASIO not working on Windows 7 x64.
    - Fixes Encoder not available on Windows 7 x64 (related to fix above).
    - Modifies default format on Windows 7 / Vista to 24-bit, 48kHz.
    - Properly adds support for 64-bit OpenAL and 64-bit ASIO.
    - Sets default speaker setting to 5. to properly reset configs to their defaults during install (fixes Bass and Treble leves not set to 50% on Windows 7 / Vista).
    Undocumented fixes by Creative (not listed in the release notes):
    - Fixes the Enable Dolby Digital Li've checkbox not staying checked when Audio Console is closed.
    - Fixes Equalizer Out of Memory error.
    - Fixes Equalizer settings being lost on Windows 7 / Vista when speaker configuration is changed.
    - Fixes low volume on Windows 7 / Vista when default format is set to anything higher than 6-bit, 48kHz.
    - Fixes MIDI instruments in Melodic Pool not playing when speaker setting is higher than 2. speakers.
    - Restores missing Microphone option in Surround Mixer (documented).
    - Fixes Microphone mute, volume and +20db boost controls.
    [size="3" color="#000000">?
    [size="3" color="#000000">Release Notes:
    Windows Security warning during driver installation
    When prompted with: "Windows can't verify the publisher of this driver software", choose "Install this driver software anyway".
    OpenAL 2D benchmark in RightMark 3DSound crashes your system
    Due to a driver bug, your system will crash if you run the OpenAL 2D benchmark using 63 buffers. No problem With 62 or fewer buffers. OpenAL 3D and OpenAL 3D + EAX benchmarks are not affected.
    Details: DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D) - ctoss2k.sys
    Microphone issues on Windows 7/Vista 64-bit (x64) with 4GB?of RAM or more
    Audigy driver does not support 64-bit addressing, resulting in random issues with the Microphone (static, robotic or distorted voice, white noise).
    Workarounds:
    - install the 32-bit (x86) version of Windows
    - limit the RAM available to Windows to less than 4GB
    - enable Memore Hole in BIOS Setup, if?your motherboard supports the setting
    6. Speakers?incorrectly available on Windows 7 64-bit (x64)
    Due to a version detection bug in the 64-bit drivers, the FilterSpeakerMode registry setting is ignored, exposing the 6. speakers setting on Windows 7 x64 edition.
    Do not choose that mode as it causes sync issues with Windows mixer.
    MediaSource DVD-Audio Player system requirements
    - 32-bit edition of Windows 7 / Vista / XP
    - any Audigy 2, Audigy 2 ZS or Audigy 4 card
    Built-in Decoder on Windows 7 / Vista (requires Service Pack )
    To use the built-in decoder, make sure it is enabled in Audio Console.
    Select "SPDIF Out (Creative SB Audigy (WDM))" as the output device of your player and then configure the AC3/DTS filter to send the stream through SPDIF.
    When you restart your computer, the Tone settings (Bass and Treble) are not applied.
    Just readjust one of the controls one time per boot.
    Advanced EQ and Special FX not available on Windows 7 / Vista
    These presets don't work on Windows 7 / Vista.
    There is no sound in games with OpenAL support on Windows XP
    Disable Advanced EQ and Special FX selecting "No effect" before running the game or program.
    Equalizer settings are lost
    When you run a game with OpenAL support or using Creative ALchemy, the Equalizer settings are lost.
    Just run Equalizer and the saved setting is loaded automatically.
    Tone settings are reset when speaker configuration is changed
    Bass and treble settings are reset when speaker configuration is changed.
    DTS Encoder Switcher
    The Encoder Switcher can be found in the \EncSwitcher folder in the path where you extracted the Support Pack.
    Thoroughly read the ReadMe.txt file included before using the provided?utilities.
    Hardware CMSS Headphone
    To use the hardware CMSS you need to select "Disable all enhancements" in the "Enhancements" tab on:
    Playback Devices -> Speaker Properties
    Now check the Speaker configuration in "Playback devices".
    If it is Stereo, run Audio Console and change it to 4., 5. or 7. and only after that change it to Headphones.
    This procedure ensures that CMSS() will work after a Windows restart, otherwise only CMSS2 will work.
    Microsoft Audio Home Theater Effects
    This driver adds the following audio effects, which are available depending on the current speaker configuration:
    - Bass Management
    - Speaker Fill
    - Room Correction
    - Loudness Equalization
    - Bass Boost
    - Virtual Surround
    - Low Frequency Protection
    Some effects are also available for the "SPDIF Out" device.
    Some Microsoft effects have priority over Creative CMSS effects and will disable the later.
    Windows MIDI Device Configuration Utility
    Use this utility to change the MIDI playback device for 32-bit and 64-bit applications.
    Download:
    New version available here:
    http://forums.creative.com/creativelabs/board/message?board.id=soundblaster&thread.id=46907?
    All files are property of Creative Technology Ltd, unless otherwise noted.

    IRe: SB Audigy Series Support Pack 3.0 + DTS Encoder Switcher (08/28/2009).
    blunden wrote:
    EddieObscurant: 4. works fine for me in AC3. I use AC3filter though and it has it's own speaker settings. Perhaps that helps until the next release.
    daniel_k: I uploaded it to 4shared.com and MediaFire for you since I don't really like Rapidshare. I hope you don't mind.
    http://www.4shared.com/file/302793/e9678376/Audigy_SupportPack_3_0.html
    http://www.mediafire.com/download.php?rjmznqa2oy
    Sure I don't mind, thanks for helping, but I've?just uploaded an updated package, version 3..
    Fixes an issue that prevents Speaker Fill from working.
    There is also a hotfix in the main post, so those who have already installed Support Pack 3.0 don't need to reinstall.

  • Support packs for CI + App servers

    HI,
    I worked mostly with Central Instance / Oracle DB only. I have done upgrade for Kernel / Oracle-Opatches and ABAP/ JAVA support packs. Now I have to implement these in production environment where it has one central instance and 3 app servers. I would lilke to know, what difference it makes, for Kernel upgrade / Oracle Patches / ABAP and Java support packs. What should I take care in terms of stopping ./ starting services
    Would appreciate your feedback.,
    Thanks,
    Raj

    Hi Raj,
    For Application server what type of scenior you are using.
    Did you made share of /usr/sap/ or /sapmnt to you application sever.
    if yes, then you have to just upgrade the kernal in CI & not in Apps
    If no, then you have to manually upgrade the kernal on CI & apps.
    Thanks
    Anil

  • Error occured while tranferring file in support pack

    I am Applying support pack in my QAS Server. When I have apply Support Pack of ABAP from SAPKA70009 to SAPKA70012 . It proper work. But when I am applying SAPKA70013
    via Frontend it give messege.
    An error occured while tranferring file
    'E;\sapdownload\SupportPack\KA70013.CAR'from the
    frontend computer.
    In my PC from where i am applying Patch . All drive space is ok and In my QAS server all file system is OK.
    Where is the problem.
    Thanks
    manu

    quality:qasadm 4> SAPCAR -xvf KA70013.CAR
    processing archive KA70013.CAR...
    x EPS/in/CSN0120061532_0027618.ATT
    x EPS/in/CSN0120061532_0027618.PAT
    what is the location of this extracted file? just move the extracted file into /usr/sap/trans/EPS/in then
    Now When I login in QAS server in Client 000 via DDIC.
    When I run SPAM and Load package from Application Server
    It ask SPAM Confirm Load
    path of EPS inbox :/usr/sap/trans/EPS/in
    Do you want to Upload OCS package from EPS inbox
    I press Yes
    Regards
    Subhash

  • Error importing support pack SAPKH60011 (SAP_APPL)

    Dear All,
       I am faceing one error when applying support pack SAPKH60011 can not apply showing error " The import was stopped since an error occurred during tha phase IMPORT _PROPER ....". for details i here attached screenshot .
    Pls. reply ,
    Thanks and regards,
    Mayur

    Hi Mayur,
    You need to check the latest alog, ulog and slog.
    Check the main import log SAPI<package name> which should be in usr/sap/trans/log
    This will cotnain details of why the import failed.
    It it failed due to a deadlock occuring which can occur if someone is using the system while import is occuring, you should restart the database to clear any locks before attmpting the import again.
    Another cause of failure during import can be the use of out of date transport tools. Please ensure you are using the latest tp and R3trans available for your release from the service marketplace.
    Are you still able to access the system and repeat the import via SPAM?
    If every transaction is resulting in a dump and Syntax errors, then please open a message with SAP and provide the alog, ulog and slog along with the main import log and screenshots of the results of
    tp showbuffer <sid> pf=<path to transport profile> tag=SPAM
    and screenshots of the contents of usr/sap/trans/tmp
    for further analysis. Also, please do NOT make any manual commands or changes to the buffer or it can make the situation worse.
    Ensure if the import has failed, that the related SAPKK<package name> is renamed / moved from usr/sap/trans/tmp if it is still there from the failed import attempt. If they are still there when you try a new import, the slog will filll with entries of
    warning file ...... is already in use, waiting 30 seconds
    and the import will not progress.
    These files will be created once the new import is started.
    When repeating the import, please monitor the SLOG entries and see that usr/sap/trans/log and usr/sap/trans/tmp are being updated regularly, this will allow you to see the progress of the import.
    Please update with the contents of SAPI...... if the import still fails.
    Best regards,
    Paul

Maybe you are looking for