Error in Preprocessing Roadmap step JOB_RSUPDTEC_SHD aborted

Dear All,
We are upgrading our server from R3 4.7 to ECC 6 EhP4. Our OS is AIX and database is DB2 9.5.
during Preprocessing Roadmap step JOB_RSUPDTEC_SHD aborted. This job run in phase JOB_RSUPDTEC_SHD on shadow system. We are getting the dump in shadow system
Runtime Errors         DATA_LENGTH_0
Exception              CX_SY_RANGE_OUT_OF_BOUNDS
                                                                                |
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
caught in
procedure "MODIFY_TABSPACE_DB6" "(FORM)", 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:
In the executed program "RSUPDTEC", the system attempted to access the field
"DATA_TBSP_NAME" using the length 0.
However, a partial field access with the length specification 0 is not
|    allowed.
We have upgraded our kernel, dp_wp, R3trans, tp of 620 and 701 to latest avaliable. But still the problem cannot shortout.
ON seeing SAPUP log file PSUPDTECSHD.LOG we got this information
4 ETQ260 Starting batchjob "RSUPDTEC"
4 ETQ010 Date & Time: 20101018143359
4 ETQ260 Starting batchjob "RSUPDTEC"
4 ETQ230 Starting RFC Login to: System = "PRD", GwHost = "haeccsbx", GwService = "sapgw01"
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ233 Calling function module "subst_start_batchjob" by RFC
4 ETQ399 JOBNAME='RSUPDTEC', REPNAME='RSUPDTEC', VARNAME='', BATCHHOST='haeccsbx', IV_SCHEDEVER=' '
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20101018143409
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
1EETQ242 Error code "-1" during analysis of logfiles matching "RSUPDTEC\.PRD"
2EETQ262 Batchjob "RSUPDTEC" aborted
4 ETQ359 RFC Login to: System="PRD", Nr="01", GwHost="haeccsbx", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2WETQ360 RFC of "subst_list_sys_logs" failed:
2WETQ361 code/exception : DUMP_ERROR
4 ETQ359 RFC Login to: System="PRD", Nr="01", GwHost="haeccsbx", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
By analysis its seem that this is data length error but not able to understand how to solve this as we are using standared sap method of upgrade.

Hi Pritpal,
Please check note 1474361
Also you can update the system with latest database library dbdb6slib.The library has to be updated
for the SHADOW system in directory <upgdir>/abap/exe (and
<upgdir>/abap/exe_new as well) .Put the 7.01 version of library.
Regards
Ashok Dalai

Similar Messages

Error during the PREP_INPUT/KX_CPYORG in the EXTRACTION roadmap step

Dear Gurus,
We are on SUSELinux 10 SP2
Oracle 10.4 and
I am in the process of applying EhP4 on top of my ECC 6.0 SR3 server and i m in the Extraction roadmap step and at a phase PREP_INPUT/KX_CPYORG which gives me the following error
Severe error(s) occured in phase PREP_INPUT/KX_CPYORG! on my SAPEhPGUi screen and no log gives a clear explaination of this error, i have checked the log KX_CPYORG.LOG and it is as below
======================================================================================================
2 ETQ399 Reading list file '/usr/sap/KDV/SYS/exe/run/dbatoolsora.lst'
3 ETQ399 Copying file 'dbatoolsora.lst'.
3 ETQ399 Copying file 'brarchive'.
3 ETQ399 Copying file 'brbackup'.
3 ETQ399 Copying file 'brconnect'.
3 ETQ399 Copying file 'brrecover'.
3 ETQ399 Copying file 'brrestore'.
3 ETQ399 Copying file 'brspace'.
3 ETQ399 Copying file 'brtools'.
3 ETQ399 Copying file 'initSID.sap'.
3 ETQ399 Copying file 'sapconn_role.sql'.
3 ETQ399 Copying file 'sapdba_role.sql'.
3 ETQ399 Copying file 'libsbt.so'.
1 ETQ399 Copied 784 files.
1 ETQ399 Failed to copy 1 files.
But doesnt say which file..
======================================================================================================
Apart from that i have also checked the log file SAPehpichk.log, which is as below
CURRENTPHASE PREP_INPUT/KX_CPYORG
...started at 20091004010834
Using phase log file 'KX_CPYORG.LOG'.
Kernel is replicated from /usr/sap/KDV/SYS/exe/run.
...begin dialogue at 20091004010846
======================================================================================================
i have also checked the files and the size of the /usr/sap/KDV/SYS/exe and /ehp4/EhPInstaller/EHPI/abap/exe folders and they look alike and no size difference among them.
Can anyone please help me come out of this situation.
I have re-run the Phase (repeated) many a times with no luck.
Awaiting any inputs on the same,
Million thanks in advance,
Baso

Dear All,
The issue is resolved and i did the following
1) Cancelled the Ehp4 installation
2) Deleted EHPI directory
3) Downloaded latest EhPI (which is released on 1 Oct)
4) Restarted the EhP4 installation
5) Changed the icmbnd file permissions in the source directory to 777 and owner to SIDadm
6) Copied it manually with the same permissions into the target exe directory (ehp4/EHPI/abap/exe)
7) After the phase reset the file permissions back to original in the source directory (/usr/sap/SID/SYS/exe/run)
Only one good suggestion is download the latest EhP installer
Hope this helps
Thanks to all
Regards
Hunky

Select_step problem in a dynamic Multiple RoadMap Step

Hi everybody,
I am working with a roadmap that dynamically assigns the number of steps from a data source assign to the multiple roadmap step. When I selected a step I am not being able to change the focus and yellow color to it. I already know which step the user selected by reading the context element assign to the multiple roadmap step, but what do I need to do in order to change the focus and color of it?.
I read other post that describe the same issue, and the answer was to change the lead selection of the roadmap, but when I tried to do it I receive a dump saying that I cannot change the lead selection.
This answered post [Re: Multipleroadmapstep Problem|] describes perfectly my problem and I already post the same question on it, but I think nobody reads it because the status of the post is answered..
Regards,
Eric
Edited by: Eric Hernandez Pardo on Aug 14, 2009 6:41 PM
Edited by: Eric Hernandez Pardo on Aug 17, 2009 12:36 PM

Hi Arpan,
I'm getting the dump exactly at this point " lo_nd_roadmap->set_lead_selection_index( vl_index )". I maded a few test based on your comment, with and without the '-index value' and also changing the context node bind to the selected_step, when I use the context_node "mrs" (this context is bound to the multiple roadmap step) like the code above I get no errors at all, but the step is not getting mark, neither changes its color. In this case I get the dump if I added the '-2'.
If I bind another context to the selected_step of the roadmap and do the same procedure (replacing the wdctx_mrs for the new context) I get a dump at " lo_nd_roadmap->set_lead_selection_index( vl_index )" with the '2' or '-2' values.
Any sugestions?
DATA: lo_nd_roadmap     TYPE REF TO if_wd_context_node,
        lo_el_roadmap     TYPE REF TO if_wd_context_element.
* navigate from <CONTEXT> to <MAIN> via lead selection
lo_nd_roadmap = wd_context->get_child_node( name = wd_this->wdctx_mrs ).
* get element via lead selection
lo_el_roadmap = lo_nd_roadmap->get_element( ).
data: vl_element Type Ref To IF_WD_CONTEXT_ELEMENT,
      vl_index type sy-tabix.
CALL METHOD lo_nd_roadmap->get_lead_selection_index
receiving
    index = vl_index.
vl_index = sl_roadmap-step_id.
lo_nd_roadmap->set_lead_selection_index( vl_index ).
Regards,
Eric

Error: Binding from workflow to workitem aborted

Hi ,
I am getting an error in binding which I am not able to resolve. Let me try to explain the scenario first.
1) In the workflow a container element is existing with the name ZBUS2081 which is having reference to object type BUS2081.
2) BUS2081 is having an <b>attribute</b> "Company code" which is again having reference to object type BUS0002. BUS0002 has a key field "CompanyCodeId" which is having reference to database table T001-BUKRS.
3) In a particular step of the workflow there is a binding between ZBUS2081.Companycode.CompanyCodeId ->CCODE where CCODE is a task container element having dictionary reference T001-BUKRS.
4) When the workflow is executing it is giving error in this particular step. The error description are "Binding from workflow to workitem aborted" "ZBUS2081.Companycode.CompanycodeId of binding assignment is not available " Error when determining attribute COMPANYCODE of object"
5) When I check the container in the technical details I see that ZBUS2081.Companycode.CompanycodeId is set to a value. I also checked the corresponding database table for the invoice document and found that this value is existing.
Can anybody please help me on this as to why this binding error is occuring?
Thanks in advance,
Abhishek

Hi Kjetil,
the workflow started when a document is parked. Its triggering event is BUS2081-Parked. Even I was thinking in the same lines that may be the workflow is trying to access database information which has not been updated at that moment.
When I checked the attribute Companycode of object BUS2081 I even found that the source is set to "Database field" and not "Virtual".
But when I check the workflow container ZBUS2081.Companycode.CompanycodeId is having the correct value. This means the data <b>has</b> been fetched correctly from the database.
Hence I feel if we cannot use an attribute with object reference directly in the binding, rather use a container operation to assign the value to another workflow container element and then use this element in the binding.
Any inputs from any body to confirm this are welcome.
regards,
Abhishek

Error occurred in deployment step 'Add Solution': A timeout has occurred while invoking commands in SharePoint host process.

Hi,
I am deplyoing a solution which has custom web parts- vwp- appln pages, event receivers.
It was working fine till last week. I was able to deploy the solution and able to see the web parts and func. was working.
But now from the last 2 days onwards, when I tried to depoy this soution, I am getting the error
"Error occurred in deployment step 'Add Solution': A timeout has occurred while invoking commands in SharePoint host process "
may i know why am getting this error.
note: my dev machine- Win Srvr 2012 - VS 2012- SP 2013 - SP D 2013 was having soem issues with the space in C drive.
once i have done the index reset few months back and i started getting space in C:\ Drive is 0 bytes.
so what my infra. team has done is , increased the space in drive to 150 GB[ it was a VM ].
help is appreciated !

What is current disk space on your drives
Delete ULS logs and other log files from server id not needed
could be related to ChannelOperationTimeout
http://msdn.microsoft.com/en-us/library/ee471440(v=vs.100).aspx
Also, don't forget to restart Visual Studio
Goto the following regustry key: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools
Add the following as a DWORD (wont be there by default)
ChannelOperationTimeout
REG_DWORD that specifies the time, in seconds, that Visual Studio waits for a SharePoint command to execute. If the command does not execute in time, a SharePointConnectionException is thrown.
The default is 120 seconds.
http://social.technet.microsoft.com/wiki/contents/articles/21052.como-resolver-o-erro-error-occurred-in-deployment-step-activate-features-a-timeout-has-occurred-while-invoking-commands-in-sharepoint-host-process-pt-br.aspx
If this helped you resolve your issue, please mark it Answered

Error occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.

Error 1 Error occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.
0 0 myProjectAssetsLists
am getting the above error when i deploy my farm solution which is actually a "farm solution import package" template.
i am deploying this to a new site collection and once its features are activated this will provision few doc libs and splists in the targeted site.
any help is appreciated.

try below link:
http://msdn.microsoft.com/en-us/library/ee471440.aspx
http://sujeetrec.blogspot.in/2013/12/sharepoint-2010-deployment-timing-out.html
Increase the timeout that Visual Studio waits for SharePoint to deploy a feature:
Create: [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools] ChannelOperationTimeout DWORD
The value is a timeout in seconds. The default is 120 (2 minutes).
Full details on this switch and others are here:
http://msdn.microsoft.com/en-us/library/ee471440.aspx

Error in preprocessing phase

Hi All ,
We are facing error in preprocessing phase of upgrade to EHP 7 ,Let me know if anyone can help us in this critical situation
System details:Oracle 11gr2,Linux x86-64 ,
Below is the error :
During the phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RFCDEST_CREATE_S2OX in
Pre-processing of the SUM we are facing below error.
1 ETQ233 Calling function module "FUNCTION_EXISTS" by RFC
2 ETQ373 parameter "FUNCNAME" = "RFC_DESTINATION_CREATE"
1 ETQ234 Call of function module "FUNCTION_EXISTS" by RFC succeeded
4 ETQ010 Date & Time: 20140912043336
1 ETQ359 RFC Login to: System="XXX", AsHost="sapXXXpas" Nr="12",
GwHost="sapa10pas", GwService="sapgwZZ"
2 ETQ232 RFC Login succeeded
4 ETQ010 Date & Time: 20140912043336
1 ETQ233 Calling function module "RFC_DESTINATION_CREATE" by RFC
2 ETQ373 parameter "DESTINATION_NAME" = "SAP_UPGRADE_ORIG_SYSTEM"
2 ETQ373 parameter "USER" = "DDIC"
2 ETQ373 parameter "HOST" = "sapXXXpas"
2 ETQ373 parameter "SYSTEMNR" = "11"
2 ETQ373 parameter "CHECK" = "X"
1EETQ235 Call of function module "RFC_DESTINATION_CREATE" by RFC failed
(error-status "3")
2EETQ360 RFC of "RFC_DESTINATION_CREATE" failed:
2EETQ361 code/exception : 3
2EETQ362 key : CALL_FUNCTION_NO_DEST
2EETQ399 RFC destination SAP_UPGRADE_ORIG_SYSTEM does not exist.
Regards
Bharat
Mob No: 91 9008804153

Hi Reagan ,
The issue was taken to SAP development security team :::Below is the weird issue ::
Firstly ,for the authorizations to work correctly, all authorization tables must be in a consistent state as below :
ust04, ust10c, ust10s, ust12, usrbf2, usrbf3.
If we want to maintain authorizations, also usr04, usr10, usr12 are required.
But here , a mismatch of tables usrbf2 and usrbf3 in 2 instances are the reason for the stuck in the upgrade :::
SQL> select count(*) from sapsr3.USRBF2 where MANDT = '000' and BNAME =
'DDIC';
COUNT(*)
2997
SQL> select count(*) from sapsr3.USRBF3 where MANDT = '000' and BNAME =
'DDIC';
COUNT(*)
1
SQL>
SQL> select count(*) from sapsr3shd.USRBF2 where MANDT = '000' and
BNAME =
'DDIC';
COUNT(*)
673
SQL> select count(*) from sapsr3shd.USRBF3 where MANDT = '000' and
BNAME =
'DDIC';
COUNT(*)
1
This issue was resolved by SAP and then upgrade went fine ,This is not an issue with password of DDIC !!!!!
Regards
Ram

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

Error occurred in deployment step 'Add Solution': A feature with ID '' has already been installed in this farm. Use the force attribute to explicitly re-install the feature.

Hi I am getting the error
Error occurred in deployment step 'Add Solution': A feature with ID 10495515-2482-41fd-98eb-3c87f739f54b has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
when trying to deploy web parts
question 1 - how do i use the force attribute when deploying from visual studio
question 2 - am i deplying it to the right place, if i deply it to the
url:port that points to my central admin tool it deploys but i cant seem to see it in any of my webs in my site collection, if i deploy it to the
url:port that points to my site collection I get this error.
im new to all this by the way :)
thanks in advance

If you are deploying from Visual Studio then please follow this post:
http://sharepointfordeveloper.blogspot.com/2014/03/solved-visual-studio-issue-error.html
Open the visual Studio and navigate to the feature XML file and add the bellow attribute.
AlwaysForceInstall="TRUE"
The <FeatureName>.Template.Xml output would be some think link this.
<?xml
version="1.0"
encoding="utf-8"
?><Feature
xmlns="http://schemas.microsoft.com/sharepoint/"
AlwaysForceInstall="TRUE"></Feature>

Error while creating model classes, operation aborted in NWDS

Hi All,
When i select Adaptive rfc 2 model and then search for the RFC, when i select RFC and click on next i get an error while importing :
Error while creating model classes, operation aborted.
It is working fine in visual composer and i have activated function module, RFC but getting same error. It is also working in web service navigator also.
Can any one help me out??
Regards,
Pradeep kumar
Edited by: pradeep_546 on Feb 17, 2011 9:35 PM
Edited by: pradeep_546 on Feb 17, 2011 9:36 PM
Edited by: pradeep_546 on Feb 17, 2011 9:37 PM

Hai guys thanks for reply
Tushar,
I am using NWDS 7.2, ce7.2 server, ECC 6.0.
Amit,
I have tested the JCO destinations they are working fine and i created a new pair of JCO destinations but unable to import the Adaptive RFC2 Model gives same error but Adaptive webservices are working fine in my NWDS7.2
Deepak,
I am unable to create model in other projects also.
I have sufficient amount of memory in my drive.
I have imported the DC to other NWDS but it gives same error.
Thanks for all,
Regards,
Pradeep Kumar G
Edited by: pradeep_546 on Feb 18, 2011 3:05 PM

Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.

Installed SP 2013 Foundation in my Hyper-V machine
Created and done all the steps mentioned here http://blogs.msdn.com/b/shariq/archive/2013/05/07/how-to-set-up-high-trust-apps-for-sharepoint-2013-amp-troubleshooting-tips.aspx && http://msdn.microsoft.com/en-us/library/office/fp179901%28v=office.15%29.aspx
for self signed certificate
copied those two certificates in my local machine(base machine) D drive
(D:\Cert)
Both VM and base machine are in same domain
Installed VS 2013 in my base machine and create a Provided hosted app with the copied certificates, (For creation i followed the above mentioned URL)
Just created and hit F5 to run in my base machine, but getting this error
Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.
Please help me to resolve this issue, trying to figure out from last 2 days
Thanks in Advance
Arun

Hi Harminder,
This happens because an app has already been deployed and you are deploying it again using the same version.
Resolution:
Open the AppManifest.xml file and change the version.
Vivek Jagga - MCTS SharePoint
SharePointExcellence

Deploying simple SharePoint 2013 feature causing error: "Error occurred in deployment step 'Add Solution': An unknown exception occurred while executing a sandboxed code solution request in the worker process."

When trying to deploy a sandboxed solution containing only a feature with a simple associated event receiver from VS 2013, I'm getting the following error:
Error occurred in deployment step 'Add Solution': An unknown exception occurred while executing a sandboxed code solution request in the worker process.\r\n|0
I'm working in Visual Studio 2013, deploying to SharePoint 2013.
The SharePoint project is very basic. I've only added a feature and an associated event receiver. It works without the event receiver. Then after I simply add the event receiver I get the error.
I've tried deploying directly from VS 2013 as well as publishing to a .WSP and uploading via web interface. Same error reported using both methods. I'm doing this using an Administrator account that I've confirmed is a site collection administrator.
Additionally, I've found that if I change Sandboxed Solution to False, deploy it, retract it, then change Sandboxed Solution back to True, then I can successfully deploy it. But this doesn't seem to be a permanent solution as the error will resurface a day
or two later...

Hi Steve,
Are you running your SharePoint 2013 on domain controller?
http://www.learningsharepoint.com/2013/08/09/sharepoint-2013-error-an-unknown-exception-occurred-while-executing-a-sandboxed-code-solution-request-in-the-worker-process-rn0/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/b7408608-c21b-45d9-bc16-e6afff510cd2/installed-sharepoint-2013-foundation-on-window-2010-server-issues-activating-sandbox-solutions?forum=sharepointadmin
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

"Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it." occurs while deploying from Visual studio

HI,
I get this error "Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it. " when deploying my project from visual studio 2010 to
SharePoint 2010 site. I tried restarting IIS, but it didn't help. This application used to work fine until the server crashed during the deployment process. All the other applications on the same server works fine also. Any ideas how to fix this issue?
Thanks in advance,
AM

Hi
AM ,
Thank you for your posting!
According to your error message, it says your solution does not have a WSP file associated with it. Take a look at the file system. After you Right Click -> Deploy Solution on the VS Solution, there
should be a .wsp file at <Solution Directory>\bin\<debug|release>.
Also the error can be occurring when the developer try to deploy solutions over pre-existing solutions with material changed in the solution. Go to your Central Administration Site and then
Operations and then Solution Management. Make sure that there not already a solution with the same name deployed or installed there. If there is, remove it and try deploying again.
And you could look in logs and find if there is a below error in ULS log (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).
Thank you for your understanding and support.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Releasing transport request has an error during the 'export' step.

Hello Everyone,
My environment is ERP 6.0 EHP6, AIX 6.3, Oracle 11g.
We have a transport request that was created in our development system by deleting some obsolete roles. When we try to release the transport request to our q/a system it terminates with errors in the export step.
The errors are.
   End of export R3TRTABUUSR10
   no E071K or E071K_STR entries found for R3TRTABUUSR11
   Start export R3TRTABUUSR12 ...
   no E071K or E071K_STR entries found for R3TRTABUUSR13
Of course we cannot create a new transport request because the roles were deleted.
Can someone please explain to me what could have cause this type of error and possibly how to resolve it?
Regards,
Ron

Hi Ron,
As per your log, no E071K or E071K_STR entries found forR3TRTABUUSR11
no E071K or E071K_STR entries found for R3TRTABUUSR1
Looks like there is no entry found for E071K or E071K_STR in table USR11 and USR13.
Please check those table and make sure the above entries are there, if not that could be the issues.
Also, please check if these tables (USR10, USR11, USR12 USR13) are active in SE14.
Thanks
Adil

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Hello,
I'm new to SharePoint development. I just created a empty sharepoing app in VS2010, added a webpart and in .cs file of this webpart, add hello inside RenderContents. Its compiling fine. but giving following error while deploying
Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.
My VS 2010 is running under Administrator privileges & I'm admin to this machine.
Comments?

Hi, just had the same problem (on a 2013 enviroment) and was able to solve it partly by this post.
Also experience a problem with dublicate ports, see here: http://technicaltrix.blogspot.dk/2014/11/error-occurred-in-deployment-step-add.html
http://technicaltrix.blogspot.dk/

Error in Preprocessing Roadmap step JOB_RSUPDTEC_SHD aborted

Similar Messages

Maybe you are looking for