- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- SUMv09 going to CRM7.0EHP3 sps03
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
SUMv09 going to CRM7.0EHP3 sps03
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 02-12-2014 3:47 AM
Hello All!
We are currently at NW7.40 CRM EHP3 SPS02. I'm using the SUM SP09 to get to CRM EHP SPS03.
OS = AIX 6.1
KERNEL = 741_REL
tp = v18 (latest as of today)
R3trans = v20 (latest as of today)
I'm in the Execution PHase, specifically at step MAIN_NEWBAS/XPRAS_AIMMRG. It fails with
Checks after phase MAIN_NEWBAS/XPRAS_AIMMRG were negative!
Last error code set: Detected 1 aborted activities in 'XPRASUPG.ELG'<br/> Calling '/usr/sap/CDM/DVEBMGS00/exe/tp' failed with return code 8, check /sapmedia/CDM/SUM/abap/log/SAPup.ECO for details
ERROR:
Detected the following errors:
/sapmedia/CDM/SUM/abap/log/SAPL-XXX13INCTSPLGN.CDM:
4 ETW000 buffersync : NO
4 ETW000 clients : default
4 ETW000 commit : -1
4 ETW000 table cache : dynamic
4 ETW000
2EETW152 Cannot open file "/sapmedia/CDM/SUM/abap/data/R-XXX13INCTSPLGN.SAP".
# /sapmedia/CDM/SUM/abap/log/SAPR740XPRA90000200.CDM:
1 ETP109 version and release : "380.10.13" "741"
1 ETP198
2 EPU126XPost-import methods for change/transport request: "SAPK740XPRA90000200"
4 EPU111 on the application server: "xs-bhm-ccd-1"
2 EPU122XPost-import method "/CTSPLUG/ACT_AFTER_IMP" started for "PLGD" "L", date and time: "20140211210801"
2EE 000 Unknown message with " " " " " " " "
2EEPU133 Errors occurred during post-handling "/CTSPLUG/ACT_AFTER_IMP" for "PLGD" "L"
Please see XPRASUPG.html for more information.
Below is the XPRASUPG.ELG file:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CMDFILE IMPORT ERRORS and RETURN CODE in SAPL-XXX13INCTSPLGN.CDM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4 ETW000 buffersync : NO
4 ETW000 clients : default
4 ETW000 commit : -1
4 ETW000 table cache : dynamic
4 ETW000
2EETW152 Cannot open file "/sapmedia/CDM/SUM/abap/data/R-XXX13INCTSPLGN.SAP".
1 ETP111 exit code : "12"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR740XPRA90000200.CDM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP109 version and release : "380.10.13" "741"
1 ETP198
2 EPU126XPost-import methods for change/transport request: "SAPK740XPRA90000200"
4 EPU111 on the application server: "xs-bhm-ccd-1"
2 EPU122XPost-import method "/CTSPLUG/ACT_AFTER_IMP" started for "PLGD" "L", date and time: "20140211210801"
2EE 000 Unknown message with " " " " " " " "
2EEPU133 Errors occurred during post-handling "/CTSPLUG/ACT_AFTER_IMP" for "PLGD" "L"
3 EPU135 "/CTSPLUG/ACT_AFTER_IMP" belongs to package "/CTSPLUG/CCTSACTIVATION"
2EEPU136 The errors affect the following components:
2EEPU137 "BC-CTS-TMS" ("Transport Management System")
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
SAPup.ECO
EXECUTING /usr/sap/CDM/DVEBMGS00/exe/tp pf=/sapmedia/CDM/SUM/abap/var/XPRASUPG.TPP put CDM
This is tp version 380.10.13 (release 741, unicode enabled)
Looking for effective putsteps ... ... ready (looking for putsteps)
tp finished with return code: 8
THe main problem, seems to be shown in the SAPL-XXX13INCTSPLGN.CDM log,
where it is looking for a data file that isn't there.......
I don't know why it "thinks" it should be there at all....
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 11.02.2014 - 21:22:46
4 ETW000 function : CREATECOFILE
4 ETW000 data file : /sapmedia/CDM/SUM/abap/data/R-XXX13INCTSPLGN.SAP
4 ETW000 buffersync : NO
4 ETW000 clients : default
4 ETW000 commit : -1
4 ETW000 table cache : dynamic
4 ETW000
2EETW152 Cannot open file "/sapmedia/CDM/SUM/abap/data/R-XXX13INCTSPLGN.SAP".
1 ETP179 CREATE COFILE FROM DATAFILE
1 ETP110 end date and time : "20140211212246"
1 ETP111 exit code : "12"
1 ETP199 ######################################
I found a few notes that dance around the issue:
1665940 - Installing/Updating SAP CTS Plug-In 2.0
1825812 - Application not available; contact SAP
They both mention an activation error.
I was able to log in to CDM:000 as DDIC.
I attempted to run SA38 program /CTSPLUG/CTS_ACTIVATION
but then I see the error "Update transport tools tp and R3trans"
But we are at the absolute latest versions of TP/R3trans for 721EXT
The most interesting thing to me, is that we're not even really
updating CTS_PLUG 200 0010 SAPK-20010INCTSPLUG
We're already at 200 Patch 0010. We were before we started these
patches, and yet, that seems to be where I'm stuck.
I fully read this note, but there's no mention of my specific error:
1843776 - Central Note - Software Update Manager 1.0 SP09
I'm going to open an incident too, but was hoping someone had come across this.
THanks, as always,
NICK
- SAP Managed Tags:
- SAP NetWeaver Application Server
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
That note could help...
1968877 - Data file for R- XXX13INCTSPLGN.SAP missing during upgrade
If file R-XXX13INCTSPLGN.SAP exists under folder <DIR_PUT>\data, make sure user <sid>adm has read and write permission to the file and folder <DIR_PUT>\data
Uncar the file SAPK-200009INCTSPLUG.SAR then put the uncared file to <DIR_TRANS>\EPS\in folder. After that go to SPAM->Utilities->Disassemble support packages.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hey Yves,
I read that note, many thanks. for sure we do not have a permissions issue. And I searched the entire OS and I can't find the file, so I know it isn't in the wrong place.
That being said, I am not trying to go to SP09 for the CTS PLUGIN anyway. In fact, I'm already at SP10, i'm not tyring to update it at all. The SP09 EPS/in files are there, and the system knows about them as well as the SP10
SAP actually gave me a new note that was supposed to address the issue:
1978218 - CTSPLUG 200 SP10 Upgrade fails
But I followed it and when I run the program attached, it fails with a dump...(below)
Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_UNKNOWN
ABAP Program Z_UNPACK_CTSPLUG
Application Component Not assigned
Date and Time 12.02.2014 10:40:31
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short Text |
| Message type " " is unknown. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "Z_UNPACK_CTSPLUG" had to be terminated because it has |
| come across a statement that unfortunately cannot be executed. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| Note down which actions and inputs caused the error. |
| |
| |
| To process the problem further, contact you SAP system |
| administrator. |
| |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis |
| Only message types A, E, I, W, S, and X are allowed. |
| There is probably an error in the program |
| "Z_UNPACK_CTSPLUG". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| Probably the only way to eliminate the error is to correct the program. |
| - |
| If the error occurs in a non-modfied SAP program, you might be able to |
| find a solution in the SAP Notes system. If you have access to the SAP |
| Notes system, check there first using the following keywords: |
| |
| "MESSAGE_TYPE_UNKNOWN" |
| "Z_UNPACK_CTSPLUG" bzw. Z_UNPACK_CTSPLUG |
| "START-OF-SELECTION" |
| If you cannot solve the problem yourself, please send the following |
| information to SAP: |
| |
| 1. This description of the problem (short dump) |
| To do this, choose System -> List -> Save -> Local File (unconverted) |
| on the screen you are in now. |
| |
| 2. A suitable system log |
| To do this, call the system log in transaction SM21. Restrict the time |
| interval to ten minutes before the short dump and five minutes after |
| it. In the display, choose System -> List -> Save -> Local File |
| (unconverted). |
| |
| 3. If these are programs of your own, or modified SAP programs: Source |
| code of these programs |
| To do this, choose More Utilities -> Upload/Download -> Download in |
| the Editor. |
| |
| 4. Details regarding the conditions under which the error occurred or |
| which actions and input caused the error. |
----------------------------------------------------------------------------------------------------
| Language key.......... E |
| Transaction......... SE38 |
| Transaction ID...... 52FB06E7766E1F30E10080000AE20184 |
| |
| EPP whole context ID...... 8EF52D95010F1EE3A5807A5DF69E5631 |
| EPP connection ID........ 00000000000000000000000000000000 |
| EPP call counter......... 0 |
| |
| Program.............. Z_UNPACK_CTSPLUG |
| Screen.............. SAPMSSY0 1000 |
| Screen line.......... 6 |
| Active debugger..... "(TPDA)" |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| The termination occurred in ABAP program "Z_UNPACK_CTSPLUG", in |
| "START-OF-SELECTION". The main program |
| was "Z_UNPACK_CTSPLUG". |
| |
| In the source code, the termination point is in line 85 of (Include) |
| program "Z_UNPACK_CTSPLUG". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 55| iv_eps_file = eps_filename |
| 56| iv_eps_dir = eps_dir |
| 57| exceptions |
| 58| cannot_determine_r_data_file = 1 |
| 59| cannot_get_package_file = 2 |
| 60| cannot_open_package_file = 3 |
| 61| patch_format_error = 4 |
| 62| cannot_disassemble_r_data_file = 5 |
| 63| cannot_disassemble_d_data_file = 6 |
| 64| cannot_open_cofile = 7 |
| 65| cannot_open_r_data_file = 8 |
| 66| patch_unknown_block = 9 |
| 67| cannot_determine_d_data_file = 10 |
| 68| cannot_open_d_data_file = 11 |
| 69| cannot_store_separator = 12 |
| 70| wrong_directory_type = 13 |
| 71| cannot_store_attributes = 14 |
| 72| no_params_for_createcofile = 15 |
| 73| cannot_call_tp_createcofile = 16 |
| 74| cannot_determine_cofile = 17 |
| 75| wrong_eps_file_name = 18 |
| 76| unknown_seq_type = 19 |
| 77| table_pat13_not_in_system = 20 |
| 78| cannot_build_allow_file_name = 21 |
| 79| cannot_open_allow_file = 22 |
| 80| cannot_disassemble_allow_file = 23 |
| 81| table_patacp_not_in_system = 24 |
| 82| package_file_error = 25 |
| 83| others = 26. |
| 84|if sy-subrc <> 0 and sy-subrc <> 16. |
|>>>>>| MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno |
| 86| WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. |
| 87|endif. |
| 88| |
| 89| |
| 90|concatenate '-Dctc=0 -s' sy-sysid into tp_options separated by ' '. |
| 91|call function 'TRINT_TP_INTERFACE' |
| 92| exporting |
| 93| iv_tp_command = 'CREATECOFILE' |
| 94| iv_transport_request = plugin_name |
| 95| iv_tp_options = tp_options |
| 96| importing |
| 97| ev_tp_return_code = tp_rc |
| 98| exceptions |
| 99| unsupported_tp_command = 1 |
| 100| invalid_tp_command = 2 |
| 101| missing_parameter = 3 |
| 102| invalid_parameter = 4 |
| 103| get_tpparam_failed = 5 |
| 104| update_tp_destination_failed = 6 |
----------------------------------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
Well, I'm afraid I won't be able to help you as it seems to be an unexpected error in function SPDA_PATCH_DISASSEMBLER.
Maybe you can check in the last part of the dump if you are able to grap the value for sy-msg* variables and see if it can help to find what fires that message.
Check also TP log as this function is calling TP.
Regards
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I finally got my OSS message answered. In the end, I had another system that was up, and not in any kind of "downtime" phase. so I downloaded the program from note
and ran it on my ECC6.0EHP6 system. that generated a bunch of data files in the /usr/sap/trans/data.
and I copied the one I needed over to my system.
Still, I failed later on and SAP had to do "something" to the buffer. Im assuming like from this POST:
http://scn.sap.com/thread/3219014
Bottom line, I got through it.
and for those reading this, the moral of the story is don't put CTS_PLUGIN on your system if you can avoid it. but if you do, run the program from 197218 in advance, and get those data files.
If you are where I was, you'll need to open a message in the BC-CTS-TMS-CTR app area.
good luck
NICK
Answers (0)
| User | Count |
|---|---|
| 83 | |
| 10 | |
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.