Support Pack SAPKB70012 NW2004s giving ABAP dumps

Question

Hello All,
We are trying to apply Basis Support Pack 12 NW2004s in one of our systems. The support packed stoped in Import Proper step becuse of wp max runtime reached. So now when I try to kick it of it gives me the follwoing ABAP dump.
Runtime Errors         SYNTAX_ERROR
Date and Time          05/30/2007 14:12:00
Short text
     Syntax error in program "SAPLSCP2 ".
What happened?
     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.
     The following syntax error occurred in program "SAPLSCP2 " in include
      "CL_SALV_FORM_ELEMENT==========CU " in
     line 13:
     "The type "IF_SALV_FORM_CONFIG" is unknown."
     The include has been created and last changed by:
     Created by: "SAP "
     Last changed by: "SAP "
Error analysis
     The following syntax error was found in the program SAPLSCP2 :
     "The type "IF_SALV_FORM_CONFIG" is unknown."
Trigger Location of Runtime Error
    Program                                 SAPLSTXC
    Include                                 LSTXCFFO
    Row                                     518
    Module type                             (FORM)
    Module Name                             FO_DETERMINE_CODEPAGE
Source Code Extract
Line  SourceCde
  488 data:    cp_c4(4) type c,
  489          current_dynamic_codepage like tcp00-cpcodepage.
  490
  491   perform fo_determine_codepage using    language
  492                                 changing codepage.
  493
  494 * only change locale if codepage is different to application server
  495 * get effective system codepage
  496   call 'CUR_LCL' id 'CODEPAGE' field cp_c4.
  497   current_dynamic_codepage = cp_c4.
  498   if codepage <> current_dynamic_codepage.
  499 * set locale language language.
500     perform nls_switch_language using language.
501   endif.
502
503 endform.
504
505
506 form fo_determine_codepage using    p_lang like tcp09-lang
507                            changing p_cp   like tcp09-cpcodepage.
508 statics: begin of codepage_tab occurs 10,
509            language like tcp09-lang,
510            codepage like tcp09-cpcodepage,
511          end of codepage_tab.
512
513   read table codepage_tab with key language = p_lang.
514   if sy-subrc = 0.
515     p_cp = codepage_tab-codepage.
516   else.
517     codepage_tab-language = p_lang.
>>>     call function 'SCP_CODEPAGE_FOR_LANGUAGE'
519          exporting
520               language    = codepage_tab-language
521          importing
522               codepage    = codepage_tab-codepage
523          exceptions
524               no_codepage = 1
525               others      = 2.
526     if sy-subrc <> 0.
527       perform fatal.
528       message a464(td) with codepage_tab-language raising others.
529     endif.
530     append codepage_tab.
531     p_cp = codepage_tab-codepage.
532   endif.
533
534 endform.
535
536
537 ************************************************************************
On every transaction that we try to execute we get the same dump.
Any help would greatly be appreciated.
Thanks
NSQ

Answer 1

What is the status of this thread? Does the error still being encountered? If not, could you provide the resolution so that all the readers of this thread? If it is still being encountered and the last resort is to restore, you could probably try the command: tp r3i <SP> <SID> pf=e:\usr\sap\trans\bin\tp_domain_<SID>.pfl tag=spam. Since there nothing to lose, prior to performing the restoration proper, you could probably try that command.
Actually, the resolution for the error being encountered is in SAPKB70013 NW2004s. We also encountered this problem and with patience on our side, we just waited for a couple of days or so for the SP Level 12 to complete and then, its all ok. However, SAPKB70014 also has a similar error being brought upon by SAPKB70012, again, patience needs to come in so as not to have any problems. Furthermore, note that since these OCS patches (12 and 14), have long runtime, it would be best to make it as a best practice to run SP application in background.