Limitations of upgrading from ERP 2004 to 2005

We are evaluation completing an upgrade from ERP 2004 to 2005. However, we found a limitation in note 879335 regarding upgrading the portal.
We have an Enterprise Portal instance that is separate from the SAP ECC J2EE add-in. The ESS components including XSS run on the J2EE add-in.
According to this note, we cannot upgrade the XSS component on the J2EE add-in because it
is not running on EP. Does this mean we need to undeploy the XSS components and then upgrade the J2EE and then install the XSS component? or Do we need to import the XSS component on EP and then
upgrade?
Why is this a limitation?

I have isolated the issue further. In the following code fragment the event is being fired twice the first time and never again:
          If pVal.FormType = 133 And pVal.EventType = SAPbouiCOM.BoEventTypes.et_FORM_LOAD Then
               '// get the event sending form
               'SBO_Application.MessageBox("Hello world")
               oForm = SBO_Application.Forms.GetFormByTypeAndCount(pVal.FormType, pVal.FormTypeCount)
               oNewItem = oForm.Items.Add("Button1", SAPbouiCOM.BoFormItemTypes.it_BUTTON)
               oNewItem.Left = 285
               oNewItem.Top = 382
               oNewItem.Width = 100
               oNewItem.Height = 19
               oNewItem.FromPane = 0
               oNewItem.ToPane = 1
               oButton = oNewItem.Specific
               oButton.Caption = "New Button"
          End If
End Sub
The code is an adaptation of the SDK VB.NET sample ('11.SystemFormManipulation'), which is supplied with the latest version of the SDK installation.
The big question is why is the event being fired twice.

Similar Messages

  • Failed to upgrade from ERP 6.0 EHP4 to EHP5

    Dear SAP Gurus,
    we are running ERP 6.00 with EHP4 (HCM-component) based on Windows 2003
    SP2 X64 and SQL Server 2005 SP4 (64-bit).
    We are using SAP Kernel Unicode 7.01 PL 133 (64-bit).
    We intend to upgrade from EHP4 to EHP5.
    Upon running SAPehpi, we encountered issue which stopped us from
    proceeding with the upgrade.
    Case 1: Direct upgrade to 605
    The upgrade failed on PREP_INPUT/VERSCHK_INI with error message: The
    following combination is not supported (SAP_APPL 600, SAP_BASIS 701,
    SAP_ABA 701).
    Case 2: Upgrade SAP_APPL component from 600 to 604 (due to the above
    error message)
    The upgrade failed on PREP_INPUT/VERSCHK_INI with error message:
    Release '701' of component SAP_BASIS is too new.
    Case 3: upgrade via SAINT is not supported by SAP. When uploading the
    Stack XML file, we got error saying that the stack is not supported.
    Attached is the complete list of the current SP Level of Installed
    components.
    Please advise on how we can perform the upgrade to EHP5.
    Many thanks in advance.
    regards,
    Denny

    The thing is Solution Manager was able to produce the XML file during the previous upgrade to 604 (the one without SAP_APPL 604).
    So how can it not be supported by SAP?
    If it is not supported by SAP, how can I proceed from here?
    Component Software C SP-Level Support Package Short description of the component
    SAP_ABA 701 0007 SAPKA70107 Cross-Application Component
    SAP_BASIS 701 0007 SAPKB70107 SAP Basis Component
    PI_BASIS 701 0007 SAPK-70107INPIBASIS Basis Plug-In
    ST-PI 2008_1_700 0003 SAPKITLRD3 SAP Solution Tools Plug-In
    SAP_BS_FND 701 0008 SAPK-70108INSAPBSFND SAP Business Suite Foundation
    SAP_BW 701 0007 SAPKW70107 SAP Business Warehouse
    SAP_AP 700 0021 SAPKNA7021 SAP Application Platform
    WEBCUIF 700 0008 SAPK-70008INWEBCUIF SAP WEBCUIF 700
    SAP_APPL 600 0018 SAPKH60018 Logistics and Accounting
    SAP_HR 604 0035 SAPKE60435 Human Resources
    EA-IPPE 400 0018 SAPKGPID18 SAP iPPE
    EA-APPL 600 0018 SAPKGPAD18 SAP Enterprise Extension PLM, SCM, Financials
    EA-DFPS 600 0018 SAPKGPDD18 SAP Enterprise Extension Defense Forces & Public Security
    EA-FINSERV 600 0018 SAPKGPFD18 SAP Enterprise Extension Financial Services
    EA-GLTRADE 600 0018 SAPKGPGD18 SAP Enterprise Extension Global Trade
    EA-HR 604 0035 SAPK-60435INEAHR SAP Enterprise Extension HR
    EA-PS 600 0018 SAPKGPPD18 SAP Enterprise Extension Public Services
    EA-RETAIL 600 0018 SAPKGPRD18 SAP Enterprise Extension Retail
    FINBASIS 600 0018 SAPK-60018INFINBASIS Fin. Basis
    ECC-DIMP 600 0018 SAPK-60018INECCDIMP DIMP
    ERECRUIT 600 0018 SAPK-60018INERECRUIT E-Recruiting
    FI-CA 600 0018 SAPK-60018INFICA FI-CA
    FI-CAX 600 0018 SAPK-60018INFICAX FI-CA Extended
    INSURANCE 600 0018 SAPK-60018ININSURANC SAP Insurance
    IS-CWM 600 0018 SAPK-60018INISCWM Industry Solution Catch Weight Management
    IS-H 600 0023 SAPK-60023INISH SAP Healthcare
    IS-M 600 0018 SAPK-60018INISM SAP MEDIA
    IS-OIL 600 0018 SAPK-60018INISOIL IS-OIL
    IS-PS-CA 600 0018 SAPK-60018INISPSCA IS-PUBLIC SECTOR CONTRACT ACCOUNTING
    IS-UT 600 0018 SAPK-60018INISUT SAP Utilities/Telecommunication
    LSOFE 600 0018 SAPK-60018INLSOFE SAP Learning Solution Front-End
    SEM-BW 600 0018 SAPKGS6018 SEM-BW: Strategic Enterprise Management
    ST-A/PI 01M_ECC600 0001 SAPKITAR7F Application Servicetools for ECC 600-605
    VIRSAHR 530_700 0012 SAPK-53312INVIRSAHR SAP GRC Access Controls 5.3 for 700 HR S
    VIRSANH 530_700 0014 SAPK-53314INVIRSANH SAP GRC Access Controls 5.3 for 700 HR a

  • Upgrade from ERP 5.0 to ERP 6.0 EHP 4 SP5 - phase START_SHDI_FIRST

    operating system: iSeries V6R1
    (this one is probably for Volker Güldenpfennig...a Happy New Year from Germany!)
    SID: AP4
    instance number normal: 00
    instance number shadow: 08
    hostname: ap400c
    error in phase MAIN_SHADOW/START_SHDI_FIRST:
    shadow instance does not start
    effect: The subsystem R3_08 ist started immediately but no process at all appears in WRKACTJOB.
    The upgrade program hangs for about 5 minutes and then shows the error message below.
    SAP note 525677 is already known but does not help.
    error message:
    To analyse the errors during start of shadow instance,
           view files 'STARTSFI.LOG' and 'DEVTRACE.LOG'
           in directory '/usr/sap/AP4/upg/abap/log'
           Repeat phase until shadow instance is started
           and you can log on instance number '08'.
    STARTSFI.LOG:
    BUT: The file DEVTRACE does not exist at all !!!
    From previous upgrades I knew that this phase brings quite some trouble so I already did this:
    - giving special right *ALLOBJ to user AP408 and AP4ADM (with WRKUSRPRF)
    - SAP note 1168235, page 9: file /usr/sap//upg/abap/SYS/global/ms_acl_info
        1.) deleted
        2.) qualified hostname (HOST=ap400c.apetito.de) used
        3.) (HOST=*) used
    Before restarting the phase I always ended the subsystem as QSECOFR with ENDSBS SBS(R3_08) OPTION(*IMMED).
    showipc 08 shows no entries.
    THIS IS THE INTERESTING PART!!!
    After some deeper investigation I found this:
    In /usr/sap/AP4/upg/abap/bin/SHADOW.TPP there are these lines:
    AP4/startsap    = /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm/startsap  SID(AP4) INSTANCE(08) PROFILE
    ('/usr/sap/AP4/upg/abap/AP4/SYS/profile/START_DVEBMGS08_ap400c') DVEBMGS08
    AP4/stopsap     = /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm/stopsap  SID(AP4) INSTANCE(08) WAIT(*YES) WAITTIME(600) DVEBMGS08
    but the directory .../homeshd/ap4adm does not exist all (sounds very UNIX-like to me).
    I changed the SHADOW.TPP file and used "/usr/sap/AP4/upg/abap/exe/startsap" and "/usr/sap/AP4/upg/abap/exe/stopsap"
    but this file seems to be created every time this phase starts.
    So I copied the two programs "startsap" and "stopsap" from /usr/sap/AP4/upg/abap/exe to the manually created directory
    /usr/sap/AP4/upg/abap/AP4/homeshd/ap4adm
    Any ideas? (Maybe the R3INLPGM sucks...?)
    Kind regards
    Rüdiger Höckel
    Edited by: Rüdiger Höckel on Jan 8, 2010 5:39 PM

    Rudiger,
    Hello from cold Minnesota, USA!  We are also upgrading from ERP2004 to ERP 6.0 EHP 4 SP4 on IBM i V6R1 and had a similar START_SHDI_FIRST issue that may be relevant to your problem.
    As in your post no shadow system jobs appeared in WRKACTJOB and no DEVTRACE file was created.  After after some time an RFC category message was shown in the upgrade GUI but turned out not relevent for us.
    A QZSHSH control job launches two (2) SBMJOB commands calling R3INLPGM with parameters to start the shadow instance.  In our case these SBMJOB commands were failing because the SAPINLPGM program invoked by this process wasn't found in library SAP<SID>70UP.  I copied the missing SAPINLPGM program from library SAP<SID>70U to SAP<SID>70UP and restarted the upgrade GUI and the shadow instance then started as expected without further issue.
    If this doesn't solve the problem try temporarily changing your shadow instance ("R3_08") job description (*JOBD) in R3<SID>400 to better trace the failing SBMJOB commands--> CHGJOBD JOBD(R3_08) .... LOG(4 00 SECLVL) LOGCLPGM(YES).  Then rerun the upgrade GUI and after the "start failure" message appears check the QEZJOBLOG (or your default) outqueue for the SBMJOB process SAPSTART and SAPSTRSRV joblogs and see why these are not launching correctly.
    Also should you run into the "Symbol o4_getpwnam (number xxx) not exported..." obscure error updating tp and retrans to current patch levels in the ECC5 (640) system took care of that issue for us.
    HTH and best of luck with your upgrade(s) :>
    Scott

  • Upgrade from SQL 2000 to 2005

    In our test environment, we are on 2005 SP01 PL34, and are
    upgrading SQL Enterprise Edition from the 2000 to the 2005 SP2 edition.
    The SQL upgrade advisor has given some error messages
    in relation to SAP tables, as per below. Should we be concerned about
    these, or will they have any effect on upgrading from SAP B1 2005 to
    2007 versions?
    Remove references to undocumented system tables
    Many system tables that were undocumented in prior releases have changed or no longer exist; therefore, using these tables may cause errors after upgrading to SQL server 2005.
    Affected tables
    Object Name : TmSP_GetDbSizeByDrives
    Object Type : P
    System Table : spt_value
    Object Name : TmSP_CheckDiskSpace
    The above messages point to SAP stored procedures.

    I believe all those SP are temporary SP for you previous upgrade.  Therefore. it should be no problem to upgrade your test database first.  You have to back up the pre upgrade database anyway,  you should be safe.
    Thanks,
    Gordon

  • Upgrade from MX 2004 to 11

    I have just purchased the Windows upgrade from Director MX
    2004 to Director 11.
    Will running this upgrade obliterate Director MX 2004 and
    replace it with Director 11?
    Or will I still have a working copy of Director MX 2004 as
    well?
    The reason that I ask is that I am not entirely certain that
    my computer has the needed horsepower to run Director 11, and in
    that tragic event, I'd like to be able to fall back to Director MX
    2004 until such a time when extra horsepower can be added.
    Cliff

    The upgrade will keep older versions intact - and there will
    be no conflicts
    in running multiple Directors. I have both Director MX 2004
    and Director 11
    running fine on the same system.
    "Cliff Johnson" <[email protected]> wrote in
    message
    news:gich2u$ilq$[email protected]..
    >I have just purchased the Windows upgrade from Director
    MX 2004 to Director
    >11.
    >
    > Will running this upgrade obliterate Director MX 2004
    and replace it with
    > Director 11?
    >
    > Or will I still have a working copy of Director MX 2004
    as well?
    >
    > The reason that I ask is that I am not entirely certain
    that my computer
    > has
    > the needed horsepower to run Director 11, and in that
    tragic event, I'd
    > like to
    > be able to fall back to Director MX 2004 until such a
    time when extra
    > horsepower can be added.
    >
    > Cliff
    >

  • Upgrade from ERP 6.0 with AFS 6.0 to ERP EHP4 - AFS 6.4

    Dear all,
    I've upgraded our Solution Manager to latest maintenance (all latest release/all latest Sp/all Oss notes)
    I 'm unable to have a queue with EHP4 - Afs 6.4 from Solution Manager
    If I define a system as SAP ERP 6 with Afs, the sol. man. give me the option to upgrade to EHP4 but 'forget' AFS 6.4.
    If I define a system as Afs Server 6, the sol. man doesn't show me the option to upgrade to EHP4.
    Any Idea to exit from this stall condition ?
    If I choose the option SAP ERP 6.0 to upgrade to EHP4, SAPHEPI will ask me the AFS upgrade CD and all AFS Sp ?
    My target is:
    - ERP 6.0 SPS 16 with AFS SP8 + ERP 6 EHP4 SPS 4 with AFS 6.4 SP 2, the max possibile now.
    Thanks tho who will try to help me.
    Regards

    Hi Reena
    Yes, you can upgrade the system to ECC 6 EHP 6 or 7,
    before that is any other SAP system are connected to ECC6 ?
    If it is yes, Kindly refer the SAP Note, & you require to check those SAP version are supported to ECC 6 EHP 7 ?
    1388258 - Version Interoperability within the SAP Business Suite
    BR
    SS

  • Upgrade from ERP 5.0 to ERP 6.0 SR3

    Hi,
    i got problem, and i can't find any solution in sdn or other internet sources. I downloaded all the DVD's for the upgrade, and when i start from MASTER UPGRADE DVD, command: STARTUP jce_policy_zip=jce_policy_zip=<path to JCE policy archive>
    system gives me a message:
    Checking if C++ runtime is installed ...
    Running MIDBOOT to unpack and startup...
    /usr/lib/pa20_64/dld.sl: Unable to find library 'ibnsl.1'.
    Killed
    I asked OS and Database administrators, should HP-UX system have any libraries that starts not from L character, they told me that there is an error in UPGRADE MASTER DVD
    i tried find the solution in SAP notes or just google, but there is nothing for this problem. Can anyone help me please?
    OS: HP-UX PARISC
    Version: 11.11
    Database: Oracle 10.2.0.4

    Hi All,
    i can't pass the step Initialization in PREPARE, here is the result of CHECKS.LOG:
    #=======================================================================
    Starting new execution of PREPARE modules
         Initialization
    at 20100217115713.
    #=======================================================================
       #====================================================#
    Requests and information for module Initialization #
       #====================================================#
    INFO:    The version check of the R3trans in your active SAP kernel
             determined that it has a sufficient level.
             No update of R3trans is necessary.
    INFO:    The version check of the disp+work in your active SAP kernel
             determined that it has a sufficient level.
             No update of disp+work is necessary.
    INFO:    The version check of the tp in your active SAP kernel
             determined that it has a sufficient level.
             No update of tp is necessary.
    WARNING: The version 2006_1_640 of the Add-on PI_BASIS is too high for this upgrade (> 2005_1_700).
             To avoid loss of data it is necessary to include the latest available version for the Add-on
             in the IS_SELECT phase.
             Please refer to Add-on note 555060 for further information.
    WARNING: The version 2008_1_640 of the Add-on ST-PI is too high for this upgrade (> 2005_1_700).
             To avoid loss of data it is necessary to include the latest available version for the Add-on
             in the IS_SELECT phase.
             Please refer to Add-on note 69455 for further information.
    INFO:       The upgrade strategy for the addon C-CEE
                is described in note: 520991
    INFO:       The upgrade strategy for the addon DMIS
                is described in note: 1000578
    INFO:       The upgrade strategy for the addon HR-CEE
                is described in note: 572252
    INFO:       The upgrade strategy for the addon HR-CEECBG
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECCO
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECCZ
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECHR
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECHU
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECPL
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECRO
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECRU
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECSI
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECSK
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECTR
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEECUA
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEEGXX
                is described in note: 632429
    INFO:       The upgrade strategy for the addon HR-CEERXX
                is described in note: 632429
    INFO:       The upgrade strategy for the addon NMI_CONT
                is described in note: 632429
    INFO:       The upgrade strategy for the addon PI
                is described in note: 700779
    INFO:       The upgrade strategy for the addon PI_BASIS
                is described in note: 555060
    INFO:       The upgrade strategy for the addon SAP_BW
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCAR
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCAT
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCAU
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCBE
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCBR
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCCA
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCCH
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCCN
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCDE
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCDK
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCES
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCFI
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCFR
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCGB
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCHK
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCID
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCIE
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCIN
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCIT
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCJP
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCKR
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCMX
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCMY
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCNL
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCNO
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCNZ
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCPH
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCPT
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCSE
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCSG
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCTH
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCTW
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCUS
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCVE
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRCZA
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRGXX
                is described in note: 632429
    INFO:       The upgrade strategy for the addon SAP_HRRXX
                is described in note: 632429
    INFO:       The upgrade strategy for the addon ST-A/PI
                is described in note: 69455
    INFO:       The upgrade strategy for the addon ST-PI
                is described in note: 539977
    INFO:       You have installed the add-on CEEFISI in your system
    INFO:       Please read note 574102 and 584396 carefully before continuing
    INFO:       You have installed the add-on C-CEE in your system
    INFO:       Please read note 574102 and 584396 carefully before continuing
    INFO:       You have installed the add-on CEEFIHR in your system
    INFO:       Please read note 574102 and 585119 carefully before continuing
    INFO:       You have installed the add-on C-CEE in your system
    INFO:       Please read note 574102 and 585119 carefully before continuing
    INFO:       You have installed the add-on C-CEE in your system
    INFO:       Please read note 574102 and 585195 carefully before continuing
    INFO:       You have installed the add-on CEEFIRO in your system
    INFO:       Please read note 585804 and 574102 carefully before continuing
    INFO:       You have installed the add-on C-CEE in your system
    INFO:       Please read note 585804 and 574102 carefully before continuing
       #===========================================================#
    PREPARE module Initialization finished with status failed #
       #===========================================================#
    #====================================================
    Execution of all selected PREPARE modules finished.
    #====================================================
    ==================================================================================================
    i readed all the notes, and all required addons are installed, what can i do to pass normally step Initialization in PREPARE?

  • Upgrade from ERP 5.0 to ERP 6.0 EHP 4 SP5 phase KX_SWITCH_1

    operating system: iSeries V6R1
    SID: AP4
    instance number normal: 00
    instance number shadow: 08
    hostname: ap400c
    non-unicode system
    kernel 6.40 non-unicode -> 7.01 non-unicode
    error in phase MAIN_SHADOW/KX_SWITCH_1:
    Last error code set:
    Error message CPF0006 running 'LODSAPKRN DEV(STMF) MNTPNT(UPG '/usr/sap/AP4/SYS/exe/run') KRNLIB(SAPAP470U) APYR3KRN(NO) USERDEF(NO) ONESTEP(*NO) STATFILE('/usr/sap/AP4/upg/abap/log/APYSAPKRN.LOG')'
    note: The mentioned log file is NOT created.
    I have uploaded the relevant logs here:
    http://www.mediafire.com/?knzmiwgkmzn
    Log file KX_SW1.LOG doesn't say that much,
    more interesting is file KX_SW1.SAV in which you can see
    that the kernel library has been filled with lots of files.
    The detail error message can only be seen directly on the iSeries
    when looking at the detailed job log of the SAPUP process:
    BuildO4affileFromDir: Could not process PASE.SAR successfully. 
    BuildLibFromDir: Error creating IFS file container in targetlib.
    LodSapKit: PANIC: Could not finish library SAPAP470U.          
    Failed to load first part of SAP kernel.                       
    and before...
    a STOPSAPCL                                           
    SAPCAR: file 'STOPSAPCL' is inaccessible (broken link)
    Then I tried to run the LODSAPKRN command manually as user AP4OFR
    but now this user cannot log on anymore:
    R3AP4400/R3INLPGM: Cannot determine kernel library for SID AP4  (A.....dd) .                                                 
    As listed in my previous message (error in START_SHDI_FIRST)
    I copied the program SAPINLPGM from library SAP70UP.
    After the new error occured I tried the following steps without success:
    copied the program R3INLPGM from library SAP<SID>70U to SAP<SID>70UP
    on the kernel DVD (that I copied to hard disc) I replaced the files SAPEXEDB.SAR and SAPEXE.SAR (old patch from 2009-04-01)
      with SAPnet patch #66
    because of SAP note 1178421 I also exchanged ILE.SAR with SAPnet patch #74 at these locations:
       /usr/sap/trans/media/51036769/DATA_UNITS/K_701_N_OS400_PPC64/DBINDEP
      and the extracted files ILE_TOOLS (130.492 KB) and iletools (33 KB) at these locations:
       /usr/sap/AP4/upg/abap/exe and /usr/sap/AP4/upg/abap/exenew
    Kind regards from Germany,
       Rüdiger Höckel
    Edited by: Rüdiger Höckel on Jan 14, 2010 11:05 AM

    REMINDER: SID = AP4
    in /tmp are two files: SAPEXE.SAR and SAPEXEDB.SAR (SAPnet kernel 701 64bit non-unicode patch #66)
    Manually building the kernel library SAPAP470U from scratch is successfull:
    as user QSECOFR:
    CLRLIB SAPAP470U
    CLRLIB QTEMP
    ADDLIBLE SAPUP
    LODSAPKRN DEV(STMF) MNTPNT('/tmp') KRNLIB(SAPAP470U) USERDEF(YES) LIST('/tmp/parts')
    EDTLIBL   (-> remove SAPUP from list, only kernel library in list is SAPAP470U)
    FIXR3OWNS LIB(SAPAP470U) OBJ(*ALL)
    APYSAP TYPE(*KERNEL) SID(AP4) DSTLIB(SAPAP470U)
    NOW the user AP4OFR is able to log on again!
    repeating the phase KX_SWITCH_1 leads to this error in process SAPup (iSeries joblog):
    (maybe there is a way to ignore the phase???)
    Objekt TS000065D7 in R3400 Art *OUTQ wurde gelöscht.             
    BuildO4affileFromDir: SAPCAR error message processing            
      /usr/sap/AP4/SYS/exe/run/PASE.SAR:
    spooled file: QPRINT -
    a KERNELLIB                                                      
    SAPCAR: error creating file object for XDNXDAAPI (error 100).    
    Eigentumsrecht für Objekt TS000065D7 in R3400 Art *OUTQ geändert.
    Objekt TS000065D7 der Art *OUTQ in Bibliothek R3400 erstellt.    
    Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
    Verbindung hinzugefügt.                                          
    Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
    Eigentumsrecht für Objekt TS000000 in QTEMP Art *USRSPC geändert.
    2 Sätze in Datei X26071 in QTEMP kopiert.                        
    Eigentumsrecht für Objekt GETOBJINF in QTEMP Art *USRSPC geändert.
    1 Einträge gelöscht. 0 Einträge nicht gelöscht.                  
    Objekt TS000065D7 in R3400 Art *OUTQ wurde gelöscht.             
    BuildO4affileFromDir: SAPCAR error message processing            
      /usr/sap/AP4/SYS/exe/run/PASE.SAR:                             
    spooled file: QPRINT -
    a KERNELLIB                                                      
    SAPCAR: error creating file object for XDNXDAAPI (error 100).    
    Aktuelles Verzeichnis geändert.                                  
    BuildO4affileFromDir: Could not process PASE.SAR successfully.   
    BuildLibFromDir: Error creating IFS file container in targetlib. 
    LodSapKit: PANIC: Could not finish library SAPAP470U.            
    Failed to load first part of SAP kernel.                         
    Im Befehl ist ein Fehler aufgetreten.

  • Document Problems when upgrading B1 from 2004 to 2005

    When upgrading from B1 2004 to b1 2005 any documents over 2 pages cause B1 to crash - anyone found the same problem or a solution.

    Hi clive
    When you say it crashes, does it just close and no error. i've came across that problem when making complex documents. If you have made your document as an A4 document, check what the default printer is? Go to file->page setup  .You'll see the printer it will print with and it's page size (letter,A4,etc). Make sure that is the same as the one you have set in the pld in the document.
    Hope this helps

  • Upgrade from 2005 and 2008 R2 to 2012 SP2

    My project is getting ready to upgrade from SQL Server versions 2005 and 2008 R2 to SQL Server 2012.
    Is there any known issues that we should look out for?
    For SQL Server 2005, we are only running the Database Engine, Full text search and SQL Server Agent. 
    For SQL Server 2008 R2 we are running Database Engine, Full Text Search, SQL Server Agent, Analysis Services, Reporting Services, and Integration Services.
    DJ

    Hello,
    A new full-text search service was introduced on SQL Server 2008, so about upgrading full-text search from SQL Server 2005 to SQL Server
    2012, please read the following article:
    http://msdn.microsoft.com/en-us/library/ms142490(v=sql.110).aspx
    On the post-installation tasks, please repopulate the full-text catalogs.
    To what edition of SQL Server 2012 you are upgrading? Do you know about the core-based Enterprise licensing
    Have you run Upgrade Advisor? Please read the following technical article too:
    http://download.microsoft.com/download/9/5/3/9533501A-6F3E-4D03-A6A3-359AF6A79877/SQL_Server_2012_Upgrade_Technical_Reference_Guide_White_Paper.pdf
    About Analysis Services, please read the following:
    http://technet.microsoft.com/en-us/library/ms143742(v=sql.110).aspx
    http://technet.microsoft.com/en-us/library/ms143229(v=sql.110).aspx
    http://technet.microsoft.com/en-us/library/ms143682(v=sql.110).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • MySAP ERP 2004 / 2005

    What new features are offered by mySAP ERP 2004 in MM module.
    I have checked the release note but it speaks about FM and its integration , utility in MM and also few new BADIs.
    Pl point out any <b>other new functionality</b> which was not there in earlier version and is now available in mySAP ERP 2004 or 2005 ???
    Thanks

    Hi Sagar,
    Difference between version on functionalities you can find on the following link.
    Give the source version (i.e. 4.6 C) and select the target version (i.e. ECC 6.0)
    http://solutionbrowser.erp.sap.fmpmedia.com/
    Release notes :
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/content.htm
    Hope this helps.
    Reward if useful
    Aasif

  • Is mySAP ERP 2004 is UNICODE compliant

    Dear Friends,
      We are planning to upgrade from 4.6c to mySAP ERP 2004.I would like to clarify is mySAP ERP 2004 is unicode compliant or not.Asking this I mean all the data will be organized in unicode format in the new system when we are migrating or not.
    I would be happy if some one can let me know efforts that are need to upgrade from mySAP ERP 2004 to 2005.
    Thanks & Regards
    Mrutyunjay

    Unicode and non Unicode systems can co-exist in the same server, indeed. I have done it several times without any issues. Is it a fresh installation or a conversion? Make sure that you follow the SAP recommendations for additional CPU/RAM/disk space if you convert
    HTH
    Andreas

  • UpGrade failed 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1.

    Hi, I've tried an UpGrade from 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1. (SAP media ID 51039339)
    The setup failed by execution of 'sqlagent100_msdb_upgrade.sql' with error code 574.
    I found the following KB articele http://support.microsoft.com/kb/960781 and this blog http://blogs.msdn.com/b/psssql/archive/2008/09/10/upgrade-for-sql-server-2008-can-fail-if-you-have-renamed-the-sa-account.aspx.
    I could start the service and execute the proposed statement to my named instance as followes:
    ...Binnsqlservr.exe" -sSAPQPT -c -f -T 3608
    <-- message if sqlcmd is active:
    2011-05-20 16:13:46.88 spid51 Starting up database 'QPT'.
    2011-05-20 16:13:47.89 spid51 CHECKDB for database 'QPT' finished without e
    rrors on 2011-05-15 09:00:06.870 (local time). This is an informational message
    only; no user action is required.
    sqlcmd -S tpzsqp01SAPQPT -E -A -Q"alter login <sys-admin> with name = sa"
    <-- this gives no feedback to the console...
    After this I've used the Repair function of the SQL 2008 setup, but it failed on the same scipt 'sqlagent100_msdb_upgrade.sql'.
    I've also tried to change the sa password
    sqlcmd -S tpzsqp01SAPQPT -E -A -Q"ALTER LOGIN sa WITH PASS
    WORD = 'xxx' UNLOCK;"
    But I'm not able to connect to the server via TCP
    C:Windowssystem32>sqlcmd -U sa
    Password: HResult 0x274D, Level 16, State 1
    TCP Provider: No connection could be made because the target machine actively re
    fused it.
    Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
    shing a connection to the server. When connecting to SQL Server 2005, this failu
    re may be caused by the fact that under the default settings SQL Server does not
    allow remote connections..
    Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
    At the moment I don't know what is wrong with the master db and why the setup can not connect with the sa account... we did not change this account in the past?! I've done the setup and this failed with the same error as described in http://support.microsoft.com/kb/960781. I've followed up this KB article but it did not solve the problem. The problem is still available.
    Error messages by setup are:
    Detail.txt
    2011-05-20 10:26:03 Slp: Error result: -2061893608
    2011-05-20 10:26:03 Slp: Result facility code: 1306
    2011-05-20 10:26:03 Slp: Result error code: 24
    SQLServer_ERRORLOG_2011-05-20T09.47.03.txt
    cript level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
    Detailed results:
    Feature: Database Engine Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Failed: see details below
    Configuration error code: 0x4BDAF9BA@1306@24
    Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
    Configuration log: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.txt
    Feature: SQL Server Replication
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Failed: see details below
    Configuration error code: 0x4BDAF9BA@1306@24
    Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
    Configuration log: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.txt
    Feature: Full-Text Search
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Failed: see details below
    Configuration error code: 0x4BDAF9BA@1306@24
    Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
    Configuration log: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.txt
    Edited by: René Schulz on May 24, 2011 9:23 AM

    for further ideas with trace flag -T3601; the upgrade script seems to have a problem with RECONFIGURE ??? :
    /* DMF Post-upgrade steps */
    -- >>> CTP5 -> CTP6 Upgrade
    -- Restoring previously saved data and converting TargetSets to ObjectSets
    IF (OBJECT_ID('dbo.dmf_upgrade', 'U') IS NOT NULL)
    BEGIN
    BEGIN TRANSACTION
    -- Restore policies
    SET IDENTITY_INSERT dbo.syspolicy_policies_internal ON
    INSERT dbo.syspolicy_policies_internal (policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified)
    SELECT policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified
    FROM msdb.dbo.tmp_syspolicy_policies_internal
    SET IDENTITY_INSERT dbo.syspolicy_policies_internal OFF
    -- Restore Health state
    SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal ON
    INSERT dbo.syspolicy_system_health_state_internal (health_state_id,policy_id,last_run_date,target_query_expression_with_id,target_query_expression,result)
    SELECT * FROM msdb.dbo.tmp_syspolicy_system_health_state_internal
    SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal OFF
    -- Restore Execution history
    SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal ON
    INSERT dbo.syspolicy_policy_execution_history_internal (history_id,policy_id,start_date,end_date,result,is_full_run,exception_message,exception)
    SELECT * FROM msdb.dbo.tmp_syspolicy_policy_execution_history_internal
    SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal OFF
    SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_details_internal ON
    INSERT dbo.syspolicy_policy_execution_history_details_internal (detail_id,history_id,target_query_expression,target_query...
    2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2011-05-23 14:03:53.30 spid7s Error: 574, Severity: 16, State: 0.
    2011-05-23 14:03:53.30 spid7s CONFIG statement cannot be used inside a user transaction.
    2011-05-23 14:03:53.30 spid7s Error: 912, Severity: 21, State: 2.

  • Precautions upgrading from MX2004 to DW8

    Hiya there
    Can someone point me to a set of guidelines that are best for
    upgrading from
    DWMX 2004 to DW8
    i.e. backing up site definitions and folders, telling
    DWMX2004 that I'm
    changing to a new version etc etc?
    Thanks
    Jos

    If you want to back up site definitions, you can either use
    the DW SITE |
    Export option to export them, or this excellent utility -
    http://mm-exporter.joexx.de
    Other than that, leave DMX2004 installed, and install DW8 -
    all sites and
    extensions should migrate. When you have verified that that
    is the case,
    then you can uninstall DMX2004.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Jos Medinger" <[email protected]> wrote in
    message
    news:ekjpcf$68o$[email protected]..
    > Hiya there
    >
    > Can someone point me to a set of guidelines that are
    best for upgrading
    > from DWMX 2004 to DW8
    >
    > i.e. backing up site definitions and folders, telling
    DWMX2004 that I'm
    > changing to a new version etc etc?
    >
    > Thanks
    >
    > Jos
    >

  • RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005

    Hi there
    I need help as we are planning to upgrade from R/3 4.6C to my SAP ERP 2005, I need the help in the context that
    . How much it will effect the prevoius functionalities, business processes user exits, reports, transactions and etc which thing one should have to keep in mind I need an general overview on this.
    2. What is the SAP best practice for Upgrade.
    3. Which things should be consider before upgrade.
    Thanks and Kind Regards
    Sohail

    Hi Sohail,
    For functional improvement between the releases you can find information in the release notes for example http://service.sap.com/releasenotes
    Also you can find http://service.sap.com/upgrade for very useful entrypoint for any information regarding upgrade.
    For more information, please check this links.
    http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
    http://www.sap.com/solutions/business-suite/erp/index.epx
    https://websmp103.sap-ag.de/~form/handler?_APP=00200682500000001266&_EVENT=DISPLAY
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

Maybe you are looking for

  • How can I host multiple domains on a single Mac?

    It's actually a little more complicated than that. I have a site, let's call it site.com, and it's hosted just fine on my Mac Mini, accessible via the Internet and everything. I want to use the .co domain of my site, which is pointed to the same IP a

  • Shipping Point copy problem from  F2 to RK

    Hi While copying from  F2 to RK Shipping Point is not copying which is there in F2, again it is re detrmining in RK. f e.g  1000 plant is having 2 shipping points like 1001 (default) 1002 (manual) 1003(manual) while creating Sales Order system determ

  • Dsccsetup initialization problem

    Hello, I am facing problem in initialization of dsccsetup. I have DSEE 6.3 zip distribution on Solaris 10 x86 machines. Please see below execution followed: root@dr1 # ./dsccsetup status Sun Java (TM) Web Console is not installed DSCC Agent is not re

  • Merging cells in Tableview

    Hi, I am creating a tableview in which I would like to merge few cells for few of the rows (based on some condition). I am also trying to make use of Table Iterator for the same but not getting proper clue. Can someone please help. Thanks and regards

  • New session id from tomcat

    I have .jsp page.I use tomcat server .When session is valid and i print sessionid in jsp using function session.getId() it print session id but when session is expire then new session id is printed .I didn't understand why this behavior.I set session