Error When canceling the released idoc ?

Hi All,
I am getting the following error when i try to cancel the releaseed idoc.
" There are already views referring to extension ZG_ORDERS05. The release can only be reset if no assignments between views and extensions exist. "
Can anyone tel me how to solve this error and add a new segment to the released idoc ?
Thanks.

hi,
i think you are using a view for this idoc.
1. Check: WE20 and open your receiverdetermination.
2. Open your Outbound parameter settings
3. check the view settings at the bottom of the first tab. Are you using a view ?
if yes... check transaction WE32 and remove the view.
maybe it´s useful!
Gordon

Similar Messages

Error when testing the standard idoc number of type PORDCH

while i was testing the idoc message type PORDCH in we02,i have got an error message type saying as
the following below are the steps which i have done in testing the idoc
WE02
Enter Idoc 705556 and execute
Opened status record.
Looked at the error under status 51. it says
An error has occurred assigning data (E1BPMEPOITEM )
Message no. B1527
Diagnosis
To call a BAPI the IDoc data must first be assigned to the relevant BAPI interface parameters.
An error has occurred when carrying out this operation, possibly due to an incorrect data type or data format in the segment E1BPMEPOITEM.
Procedure
Check that the data types in the IDoc data record matches the data types in the BAPI parameter.
You can reproduce the same error with BD87
Enter Idoc number and execute.
Drill down to the error (debug) and click process.
sap has shown the following error message in one of the status record when i tested using transactions bd87 and we02.
so wat must i do ,can i implement the SAP Note 731418 - ALE interfaces for PORDCR1 and PORDCH
are not up-to-date or is there any alternate way
will be waiting for quick and good response
bye.
Regards.
Varma Mandapati

Hi Seeta Ram,
try to reprocess the idoc using the Program
Program RBDMANI2 for status 51 ..
Read the below document for the Possible error
Processing in the Application Layer
The posting function module either calls a standard
SAP transaction, using the call transaction command
for posting the document, or invokes a direct input function module.
The results of the execution are passed back via the function
module's output parameters. If posting is successful, an application
document is created. The IDoc gets a status code of 53 (Application document posted).
If errors occur, the IDoc gets a status code of 51 (Application document not posted).
Regrads,
Prabhudas
Edited by: Prabhu Das on Apr 17, 2009 11:22 PM
Edited by: Prabhu Das on Apr 17, 2009 11:23 PM

How to cancel the release of the current segment definition-WE31-IDOC?

Hi Experts,
Am trying to add a new field to a existing custom segment type/defination. This segment type is already using in the system.
So, went to WE31 and pressed the PENCIL button for changing/adding my new field, but am geting the below message,
(1)pls let me know that does it mean CANCEL the release (Menu>Edit>Cancel Release)? if so, Can I go ahead and use this CANCEL the release? do I need to take any pre-requisites as this segment is already relased?
(2)But, you know there is another option saying 'ADD VERSION-Shift+F5', if I choose this option, its also taking me to a screen where in I can add new fields so which is correct option for me is it either (1) or (2)?
Current segment definition Z_segment_defination can no longer be changed
Message no. EA666
Diagnosis
The current segment definition Z_segment_defination of segment type Zsegment_type is already released.
System Response
The segment definition cannot be changed.
Procedure
You can either add a new segment definition or cancel the release of the current segment definition.
Thank you

so i tried to CANCEL the release by goiong menu pathEdit-->Cancel the release, but am getting the below error, How to fix it to add my new field?
Error while resetting release of segment
Thank you

Cannot cancel the release of a z segemt

Hi All,
I am getting the following error message while setting the status of IDOC segment as CANCEL RELEASE in WE31
Error while resetting release of segment Z1YV_CRRB_AUDIT
I need to add one more fields in the existing segment, but as there is error in CANCEL RELEASE of the segment i am unblae to do so.
Any help will be highly appreciated
Rgds
Kaushal

Hi,
generally first we create zsegments and then release them ten only we copy the basic type to zbasictype and then add the zsegment to it and then finally we release the basictype...This is what we do..as such in ur case it should allow u to modify the zsegment straight away when we cancel the release,but it was throwing error,so i thought to have a check at it if we relase basic type then release the segment ,may be it allows..thats why i suggested..
is it working or still u r facing some problem in it???let me know..
<REMOVED BY MODERATOR>
Regards,
Nagaraj
Message was edited by:
Alvaro Tejada Galindo

Cancel the release and change the z segment in new version.

Hi,
I have a Z segment created in 4.6c.
Now we have upgraded to ECC and i want to change one of the field ( i.e data element of the field ) and I am not able to change it.
It gives me the hard error. I am unable to cancel the relase and do the modication.
If I try to add a version it doesnt accept it with out any additonal fields.
I have tried deleting the segemnt in Basic type and tried deleting the whole segemnt, but it doesn accept this way too.
Any ideas how to go about it?
Thanks,
Krishna.

Hello,
I had a similar problem when I tried to delete fields from a segment. I also wasn't able to cancel the release of the segment and the release of the extended idoc type.
The reason seems to be that the idoc extension and the segment have been set to "released" in a lower release version of the sap-system.
I was able to edit the segment when I changed the corresponding table entry in EDISDEF and set the release to the current one. However that is no solution I would like to propose.
Anyway the problem could have something to do with the release of the the sap-system. In this case I would be glad if someone could offer a solution which is more close to the standard than editing the system tables directly.

Runtime Error when cancelling license request

I'm getting the following error when cancelling a license request. The main difference between my application and the sample applications is that the root Flex Application is mx:Application, rather than mx:WindowedApplication, but I can't figure out the best way to trap this Error - I guess it would be better for the Licensing SWC to catch this error and dispatch an Event instead?
TypeError: Error #2007: Parameter type must be non-null.
at flash.events::Event/ctor()
at flash.events::Event()
at com.adobe.licensing.controllers::LicenseProvider/set currentState()[/home/esbuilder/Shibuya-main/20100514.main.447/rialto/branches/main/compon ents/licensing/swc-release/ant-temp/com/adobe/licensing/controllers/LicenseProvider.as:226 ]
at com.adobe.licensing.controllers::LicenseProvider/httpServiceResultHandler()[/home/esbuild er/Shibuya-main/20100514.main.447/rialto/branches/main/components/licensing/swc-release/an t-temp/com/adobe/licensing/controllers/LicenseProvider.as:1212]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()

I think I'm missing something then.
I don't see how the Feature-based Licensing (http://learn.adobe.com/wiki/display/melrose/4.3+Feature-based+Licensing) can work as indicated in the documentation.
In the sample code the program will exit once the trial has expired, and there will be no other choices. If not purchased the feature doesn't turn on, but the trial dialog will indicated an option of buy or quit once trial is expired. The quit will exit the application completely, not disable the feature. The licensecheck also happens at creationcomplete, not giving an option for explanation of why to buy, or what is being unlocked (yes I realize it is just sample code, but it doesn't seem practical at this point.)
Am I reading the documenation / sample code wrong? Is there another example that will show a different type of behavior? If you set no trial does the licensing still come up?

Error when activating the master data

Hi
I am getting the following error when activating the master data. when using IDOC as transfer method in transfer rules
Error while creating table 'EDISEGMENT' entry '/BIC/CIRB0CLASS_NUM_TEXT'
If anyone came across this kind of problem plz share the solution.
Regards
Annie

Hi
I solved the problem. AFter changing from PSA to IDOC, i just saved first and activated. it got activated. But thanks for the response.
There are no short dumps in ST22
Regards
Annie

Getting the below error when running the Baseline.grf for the first time

I am getting the below error when running the Baseline.grf for the first time.
Appreciate your support in resolving it.
Error below:
INFO [main] - *** CloverETL framework/transformation graph, (c) 2002-2012 Javlin a.s, released under GNU Lesser General Public License ***
INFO [main] - Running with CloverETL library version 3.2.1 build#63 compiled 04/01/2012 12:53:21
INFO [main] - Running on 4 CPU(s), OS Windows 7, architecture amd64, Java version 1.6.0_20, max available memory for JVM 901120 KB
INFO [main] - Loading default properties from: defaultProperties
INFO [main] - Graph definition file: graph/Baseline.grf
INFO [main] - Graph revision: 1.114 Modified by: mkressirer Modified: Thu Apr 12 13:27:18 EDT 2012
INFO [main] - Checking graph configuration...
INFO [main] - Graph configuration is valid.
INFO [main] - Graph initialization (Baseline)
INFO [main] - [Clover] Initializing phase: 0
INFO [main] - [Clover] phase: 0 initialized successfully.
INFO [main] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1306871483270_0
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [RUN_GRAPH1_0] - Running graph ./graph/InitDataStore.grf in the same instance.
INFO [RUN_GRAPH1_0] - Checking graph configuration...
INFO [RUN_GRAPH1_0] - Graph configuration is valid.
INFO [RUN_GRAPH1_0] - Graph initialization (InitDataStore)
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 0
WARN [RUN_GRAPH1_0] - WS messenger cleanup failed.
java.lang.NullPointerException
     at org.apache.axis2.client.Stub.cleanup(Stub.java:134)
     at com.opensys.cloveretl.component.WebServiceClient.free(Unknown Source)
     at org.jetel.graph.Phase.free(Phase.java:487)
     at org.jetel.graph.TransformationGraph.freeResources(TransformationGraph.java:681)
     at org.jetel.graph.TransformationGraph.free(TransformationGraph.java:955)
     at org.jetel.graph.runtime.PrimitiveAuthorityProxy.executeGraph(PrimitiveAuthorityProxy.java:149)
     at org.jetel.component.RunGraph.runGraphThisInstance(RunGraph.java:511)
     at org.jetel.component.RunGraph.runSingleGraph(RunGraph.java:409)
     at org.jetel.component.RunGraph.execute(RunGraph.java:302)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
WARN [RUN_GRAPH1_0] - Some graphs wasn't executed (because graph "./graph/InitDataStore.grf" finished with error).
WARN [RUN_GRAPH1_0] - Some graph(s) finished with error.
ERROR [WatchDog] - Graph execution finished with error
ERROR [WatchDog] - Node RUN_GRAPH1 finished with status: ERROR caused by: Graph './graph/InitDataStore.grf' failed!
ERROR [WatchDog] - Node RUN_GRAPH1 error details:
org.jetel.exception.JetelException: Graph './graph/InitDataStore.grf' failed!
     at org.jetel.component.RunGraph.execute(RunGraph.java:324)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - Execution of phase [0] finished with error - elapsed time(sec): 2
ERROR [WatchDog] - !!! Phase finished with error - stopping graph run !!!
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
INFO [WatchDog] - 0 ERROR 2 20132
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
WARN [exNode_0_1306871483270_RUN_GRAPH1] - Attempt to unregister non-registered thread in the ContextProvider.
./graph/InitDataStore.grf: Execution of graph failed! Error during graph initialization: Phase 0 can't be initilized.
INFO [WatchDog] - WatchDog thread finished - total execution time: 2 (sec)
INFO [main] - Freeing graph resources.
ERROR [main] - Execution of graph failed !

It can't find an Endeca specific class when running via the clover command line utility. Thus, the classpath being set in that shell script is not incorporating the .jar files where the endeca-specific classes are packaged. I would start by adding an line to see what your classpath is set to. There are actually already some lines of shell script in clover that you can uncomment to see what .jars are getting loaded:
#echo $CLOVER_LIB/*
for i in $CLOVER_LIB/*.jar $CLOVER_LIB/*.zip; do
     LOCAL_CLASSPATH="$LOCAL_CLASSPATH:$i"
done;
#for i in `ls $CLOVER_LIB/*.jar`; do
#echo $i
#done;
You could also echo LOCAL_CLASSPATH to see what is getting set there. At the end of the day, you will need the endeca-specific jars to load which can be found here: /Endeca/Discovery/2.3.0/Integrator/plugins/com.endeca.latitude_1.0.0/*
HTH,
Dan
http://branchbird.com

Error when determining the inbound interface

Hi Experts,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Scenario Steps
1) No Condition in Interface Determination
2) 0..unbounded in Message Mapping and Operational Mapping.
3) E1KNA1 is mapped to E1KNA1
4) E1ADRMAS is mapped to E1ADRMAS
5) One Message Mapping and 1 Operational Mapping.
Thanks in Advance.
Sriram.

Hello,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
Since your scenario makes sure that the 2 files are created, there is no need to use multi-mapping. Rather, you can use an interface determination split. To do this:
1. declare xml_file1 as service interface 1, xml_file2 as service interface 2
2. do not change target occurrence in message mapping and operation mapping, maintain it as 1..1
( 2 operation mappings)
3. in ID, add the two service interfaces in your interface determination
At runtime, it will split into two inbound interfaces.
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Were you able to declare the 2 xml_files as two separate service interface(different names) in your operation mapping?
Hope this helps,
Mark

PDF Report Error When Distribute the Output?

REP-0069: Internal Error.
REP-57054: In-process job terminated:Executed successfully but there were some errors when distribute the output.
REP-50159: Executed successfully but there were some errors when distribute the output.
Approximately 5000 Pages
Distribute PDF File Approximately 1700 Files
How i can resolve this issue?

Based that you are in base release I will encourage you to upgrade to the latest patchset for 10gR2 (10.1.2.3) and then apply the recommended bundled patch on top of 10.1.2.3 as several issues have been fixed with
those patches.
Reference
Oracle Reports - Recommended Patch Bundle on Top of 10.1.2.3 (Doc ID 1162562.1)
Regards RZ

Where to put break point when debugging the inbound IDOC processing

Hi, Dear Experts,
If IDOC has error and want to debug, which program or function module to put break point when debugging the inbound IDOC processing
Thank you so much!
Helen

It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

ABAP Run time error when display the Customs Export declarations

Hi,
I'm receiving ABAP Run time error when display the Customs Exp. Declarations Under SAP Customs Processing -> Customs Processing - Import / Export -> Monitoring.
Error messaging point to Function Module - /SAPSLL/CUHD_LOAD_SELECTION.
While debugging we found that Primary Key of the below structures are not the same
lt_corpar                              type      /sapsll/corpar_t
lt_corpar_ht      type      /sapsll/corpar_k02_ht
Does anyone has the SAP Notes or solution to this issue other than changing the structures manually. I'm not sure about the impact if i change manually
Error message short details
Termination occurred in the ABAP program "/SAPSLL/SAPLCUHD_SELECTION" - in
     "/SAPSLL/CUHD_LOAD_SELECTION".
    The main program was "/SAPSLL/CULO_DISPLAY_CUS_EXP ".
    In the source code you have the termination point in line 144
    of the (Include) program "/SAPSLL/LCUHD_SELECTIONU01".
We are on GTS Release 8.0 and Support Package SAPK-80014INSAPSLL (Support pack level 14).
Regards,
Pradeep Maddi

Hi,
I have implemented SAP Note 1531799, but it hasn't resolved the current issue.
For Our GTS instance, there are 2 Feeder Systems (ECC) attached, but document transfer in one of the system has not been activated. Both having the same partner functions ( We copied the sandbox into 2 different instances for different business Testings and now these 2 instances attached to GTS for testing). These feeder systems have different Logical system names and Logical system groups.
Recently i have implemented SAP Corrections manually for one the issue, Please see below thread for the detail information
Proforma Invoice not transferred to GTS
After implementing the corrections, i have created Pro-forma invoice in ECC system. When i tried to display, i'm facing the ABAP Dump issues.
Error details
Runtime Errors         ITAB_DUPLICATE_KEY
ABAP Program           /SAPSLL/SAPLCUHD_SELECTION
Application Component SLL-LEG
You tried to insert an entry into table "\FUNCTION=/SAPSLL/CUHD_LOAD_SELECTION\DATA=LT_CORPAR_HT". However, updating the unique table key "PRIMARY_KEY" resulted in a duplicate entry. The key concerned may be either the primary key or a secondary key.
Regards,
Pradeep

While processing ALEAUD - "Error when locking the audit statistics"

Hello,
I am sending out IDOC for HR data and then prcessing ALEAUD inbound idoc immediatley (setting is done in WE21 partner profiles).
While processing these incomming idocs, I am getting this error "Error when locking the audit statistics for P01LOGSYS1 IMTIMEDEP HRMD_A" for few idocs. e.g. out of 1000 for 100 idocs this error will happen and IDOC goes to status 51.
If I try to process thes idocs ALEAUD using background processing and if I schedule 2 jobs at a time then I will get same error and IDOC goes to status 51.
Can someone help me out?

Hi
I tried processing the idocs in background processing as you have suggested using program RBDAPP01 (inbound).
There are 2 options in this program serial processing and parallel processing. When I select serial processing everyhting goes smooth but it takes long time. But when I select parallel processing I get same locking error mentioned above and only few idocs will get processed successfully with status 53 and all other will error out with status 51.
If I schedule 2 different jobs in background program RBDAPP01 (inbound) using serial processing then same thing will happen. only few idocs will get processed successfully with status 53 and all other will error out with status 51.
And I will get locking error ....
Note 1333417 says, " these IDocs will be processed via background runs of report RBDAPP01 \ RSEOUT00 (using background work processes) in batch mode leaving dialog work processes free for users and mission-critical processes. Hence you will not encounter the resources problems you are currently experiencing. The only other option would be to try increasing the number of available dialog work processes. The number of dialog processes must be greater than or equal to the total of the number of update and background processes per application server and must be configured across all operation mode
switches (see SAP note 74141). *However when there are a large number of IDocs being processed this is not a practical solution."*
Does that mean there is no possoble solution for this issue. If I increase dialog work processes will it be helpfull ?

ORA-03113 error when running the Java stored proc demos

Hi there,
Has anyone else run into this issue. When attempting to transfer an object type from Java to Oracle - through a Java stored proc - the session crashes with:
ORA-03113: end-of-file on communication channelLooking in the trace file generated the error message looks something like:
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [0x8fe04468] [SIGTRAP] [unknown code] [0x8FE59034] [] []
Current SQL statement for this session:
select pointruntime.jdistance(point(1, 2), point(2, 3)) from dual
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
ksedmp+764           call     ksedst               0 ? 2C4F4A ? 2C ? 98968000 ?
                                                   DB02C ? 27A50000 ?
ssexhd+956           call     ksedmp               3 ? 0 ? 8FE5E790 ? 5905870 ?
                                                   8FE0434C ? 40895E4 ?
0x9012c860           call     ssexhd               5 ? BFFEEF70 ? BFFEEFB0 ? 0 ?
                                                   0 ? 0 ?As you can see from the trace snippet above, I was attempting to run one of the Oracle Java stored procedure demos. Has anyone successfully run those demos? Specifically the ones where complex types (table objects or the Point object) are passed back to Oracle from the JVM.
I would appreciate some help with this. The code works fine in a Windows or Solaris environment but barfs on Apple. Truly annoying....
Anyone?
Thanks in advance,
Alex

Yes,
Apologies for not stating that information, Steve. Was a bit naughty of me! I guess the reason I didn't was because I just wanted to hear if anyone else running Oracle on Mac received such errors when executing the Java stored proc demos (specifically, the execution of PointRuntime.jDistance). Nevertheless, here's the relevant info from the trace file:
Dump file /Users/oracle/admin/sandbox/udump/sandbox_ora_1861.trc
Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining Scoring Engine options
ORACLE_HOME = /Users/oracle/product/10.1.0/db
System name:     Darwin
Node name:     maczilla.local
Release:     8.3.0
Version:     Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
Machine:     Power Macintosh
Instance name: sandbox
Redo thread mounted by this instance: 1
Oracle process number: 10
Unix process pid: 1861, image: [email protected] for the Java version, according to the readme file in the javavm directory, I am running 1.4.1:
1.5 Java Compatibility
This release has been thoroughly tested with Sun's Java Compatibility
Kit for the JDK 1.4.1. Oracle is committed to OracleJVM keeping pace
with Java and other Internet standards.

"ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED"

Hi all,
In SMICM all the services are showing active, when I tried to run the webservices the following is the error that I am getting, have looked at different solutions on sdn.
Also please find below the dev_icm file.
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<SYSTEMFAULT href="#o112" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_AI_SYSTEM_FAULT id="o112">
- <CX_ROOT>
<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>185</PROGID>
<CONTID>978</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SOAP:1.023</CODE>
<ERRORTEXT>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
</asx:heap>
</asx:abap>
dev_icm:
trc file: "dev_icm", trc level: 1, release: "640"
sysno 00
sid CC5
systemid 560 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 139
intno 20020600
make: multithreaded, Unicode
pid 5848
[Thr 5852] Thu Jan 15 23:09:17 2009
[Thr 5852] ICM running on: dlwsdv11
[Thr 5852] MtxInit: -2 0 0
[Thr 5852] IcmInit: listening to admin port: 65000
[Thr 5852] DpSysAdmExtCreate: ABAP is active
[Thr 5852] DpShMCreate: sizeof(wp_adm)##10528#(1316)
[Thr 5852] DpShMCreate: sizeof(tm_adm)##2969176#(14772)
[Thr 5852] DpShMCreate: sizeof(wp_ca_adm)##24000#(80)
[Thr 5852] DpShMCreate: sizeof(appc_ca_adm)#8000#(80)
[Thr 5852] DpShMCreate: sizeof(comm_adm)##290000#(580)
[Thr 5852] DpShMCreate: sizeof(vmc_adm)##0#(424)
[Thr 5852] DpShMCreate: sizeof(wall_adm)##(38456/34360/64/184)
[Thr 5852] DpShMCreate: SHM_DP_ADM_KEY##(addr: 032C0040, size: 3381680)
[Thr 5852] DpShMCreate: allocated sys_adm at 032C0040
[Thr 5852] DpShMCreate: allocated wp_adm at 032C1B88
[Thr 5852] DpShMCreate: allocated tm_adm_list at 032C44A8
[Thr 5852] DpShMCreate: allocated tm_adm at 032C44D0
[Thr 5852] DpShMCreate: allocated wp_ca_adm at 03599328
[Thr 5852] DpShMCreate: allocated appc_ca_adm at 0359F0E8
[Thr 5852] DpShMCreate: allocated comm_adm_list at 035A1028
[Thr 5852] DpShMCreate: allocated comm_adm at 035A1040
[Thr 5852] DpShMCreate: allocated vmc_adm_list at 035E7D10
[Thr 5852] DpShMCreate: system runs without vmc_adm
[Thr 5852] DpShMCreate: allocated ca_info at 035E7D38
[Thr 5852] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
[Thr 5852] IcmCreateWorkerThreads: created worker thread 0
[Thr 5852] IcmCreateWorkerThreads: created worker thread 1
[Thr 5852] IcmCreateWorkerThreads: created worker thread 2
[Thr 5852] IcmCreateWorkerThreads: created worker thread 3
[Thr 5852] IcmCreateWorkerThreads: created worker thread 4
[Thr 5852] IcmCreateWorkerThreads: created worker thread 5
[Thr 5852] IcmCreateWorkerThreads: created worker thread 6
[Thr 5852] IcmCreateWorkerThreads: created worker thread 7
[Thr 5852] IcmCreateWorkerThreads: created worker thread 8
[Thr 5852] IcmCreateWorkerThreads: created worker thread 9
[Thr 5852] IcmCreateWorkerThreads: created worker thread 10
[Thr 5852] IcmCreateWorkerThreads: created worker thread 11
[Thr 5852] IcmCreateWorkerThreads: created worker thread 12
[Thr 5852] IcmCreateWorkerThreads: created worker thread 13
[Thr 5852] IcmCreateWorkerThreads: created worker thread 14
[Thr 5852] IcmCreateWorkerThreads: created worker thread 15
[Thr 5852] IcmCreateWorkerThreads: created worker thread 16
[Thr 5852] IcmCreateWorkerThreads: created worker thread 17
[Thr 5852] IcmCreateWorkerThreads: created worker thread 18
[Thr 5852] IcmCreateWorkerThreads: created worker thread 19
[Thr 5852] IcmCreateWorkerThreads: created worker thread 20
[Thr 5852] IcmCreateWorkerThreads: created worker thread 21
[Thr 5852] IcmCreateWorkerThreads: created worker thread 22
[Thr 5852] IcmCreateWorkerThreads: created worker thread 23
[Thr 5852] IcmCreateWorkerThreads: created worker thread 24
[Thr 5852] IcmCreateWorkerThreads: created worker thread 25
[Thr 5852] IcmCreateWorkerThreads: created worker thread 26
[Thr 5852] IcmCreateWorkerThreads: created worker thread 27
[Thr 5852] IcmCreateWorkerThreads: created worker thread 28
[Thr 5852] IcmCreateWorkerThreads: created worker thread 29
[Thr 5852] IcmCreateWorkerThreads: created worker thread 30
[Thr 5852] IcmCreateWorkerThreads: created worker thread 31
[Thr 5852] IcmCreateWorkerThreads: created worker thread 32
[Thr 5852] IcmCreateWorkerThreads: created worker thread 33
[Thr 5852] IcmCreateWorkerThreads: created worker thread 34
[Thr 5852] IcmCreateWorkerThreads: created worker thread 35
[Thr 5852] IcmCreateWorkerThreads: created worker thread 36
[Thr 5852] IcmCreateWorkerThreads: created worker thread 37
[Thr 5852] IcmCreateWorkerThreads: created worker thread 38
[Thr 5852] IcmCreateWorkerThreads: created worker thread 39
[Thr 5852] IcmCreateWorkerThreads: created worker thread 40
[Thr 5852] IcmCreateWorkerThreads: created worker thread 41
[Thr 5852] IcmCreateWorkerThreads: created worker thread 42
[Thr 5852] IcmCreateWorkerThreads: created worker thread 43
[Thr 5852] IcmCreateWorkerThreads: created worker thread 44
[Thr 5852] IcmCreateWorkerThreads: created worker thread 45
[Thr 5852] IcmCreateWorkerThreads: created worker thread 46
[Thr 5852] IcmCreateWorkerThreads: created worker thread 47
[Thr 5852] IcmCreateWorkerThreads: created worker thread 48
[Thr 5852] IcmCreateWorkerThreads: created worker thread 49
[Thr 4204] IcmWatchDogThread: watchdog started
[Thr 4248] ISC: created 400 MB disk cache.
[Thr 4248] ISC: created 50 MB memory cache.
[Thr 4248] HttpSubHandlerAdd: Added handler HttpCacheHandler(slot=0, flags=12293) for /:0
[Thr 4248] HttpSubHandlerAdd: Added handler HttpSAPR3Handler(slot=1, flags=4101) for /:0
[Thr 4248] HttpSubHandlerAdd: Added handler HttpJ2EEHandler(slot=2, flags=1077253) for /:0
[Thr 4248] Started service 1080 for protocol HTTP on host "dlwsdv11"(on all adapters) (processing timeout=60, keep_alive_timeout
[Thr 4248] =================================================
[Thr 4248] = SSL Initialization on PC with Windows NT
[Thr 4248] = (640_REL,Jul 16 2006,mt,ascii,SAP_UC/size_t/void* = 16/32/32)
[Thr 4248] SapISSLComposeFilename(): profile param "ssl/ssl_lib" = "D:\usr\sap\CC5\SYS\exe\run\sapcrypto.dll"
 resulting Filename = "D:\usr\sap\CC5\SYS\exe\run\sapcrypto.dll"
[Thr 4248] = found SAPCRYPTOLIB 5.5.5C pl24 (Jun 11 2008) MT-safe
[Thr 4248] = current UserID: I2\SAPServiceCC5
[Thr 4248] = found SECUDIR environment variable
[Thr 4248] = using SECUDIR=D:\usr\sap\CC5\DVEBMGS00\sec
[Thr 4248] = Success SapCryptoLib SSL ready!
[Thr 4248] =================================================
[Thr 4248] Started service 8443 for protocol HTTPS on host "dlwsdv11"(on all adapters) (processing timeout=60, keep_alive_timeou
[Thr 4248] Started service 1025 for protocol SMTP on host "dlwsdv11"(on all adapters) (processing timeout=60, keep_alive_timeout
[Thr 2464] MPI<4>1#3 Peak buffer usage: 1 (@ 64 KB)
[Thr 2112] MPI<5>2#3 Peak buffer usage: 2 (@ 64 KB)
[Thr 4248] Thu Jan 15 23:09:26 2009
[Thr 4248] *** WARNING => IcmNetCheck: NiAddrToHost(10.0.0.1) took 9 seconds [icxxtool.c 1065]
[Thr 4248] *** WARNING => IcmNetCheck: 1 possible network problems detected - please check the network/DNS settings [icxxtool.c
[Thr 200] Thu Jan 15 23:09:36 2009
[Thr 200] MPI<7>4#3 Peak buffer usage: 3 (@ 64 KB)
[Thr 4092] MPI<9>6#3 Peak buffer usage: 4 (@ 64 KB)
[Thr 1660] Thu Jan 15 23:09:40 2009
[Thr 1660] MPI8#3 Peak buffer usage: 6 (@ 64 KB)
[Thr 3168] Fri Jan 16 00:02:52 2009
[Thr 3168] *** WARNING => Connection request from (8/24/1) to host: 10.20.232.89, service: 4444 failed (NIECONN_PENDING)
RM-T8, U24, 600 AVISHNU, GX280I576YB1S, 00:02:47, M1, W1, SEU_, 3/2 [icxxconn.c 2121]
[Thr 3684] Fri Jan 16 00:04:40 2009
[Thr 3684] Deactivated service 1080 for protocol HTTP on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 3804] Fri Jan 16 00:04:56 2009
[Thr 3804] Deactivated service 8443 for protocol HTTPS on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 2664] Fri Jan 16 00:09:26 2009
[Thr 2664] *** ERROR => IcmConnConnect: No service for protocol HTTP started [icxxconn.c 2007]
[Thr 3516] Fri Jan 16 00:23:53 2009
[Thr 3516] *** ERROR => IcmConnConnect: No service for protocol HTTP started [icxxconn.c 2007]
[Thr 4116] Fri Jan 16 00:26:53 2009
[Thr 4116] *** ERROR => IcmConnConnect: No service for protocol HTTP started [icxxconn.c 2007]
[Thr 4112] Fri Jan 16 00:27:07 2009
[Thr 4112] *** ERROR => IcmConnConnect: No service for protocol HTTP started [icxxconn.c 2007]
[Thr 1684] Fri Jan 16 00:34:23 2009
[Thr 1684] *** ERROR => IcmConnConnect: No service for protocol HTTP started [icxxconn.c 2007]
[Thr 3516] Fri Jan 16 00:46:52 2009
[Thr 3516] Reactivated service 1080 for protocol HTTP on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 3516] Reactivated service 8443 for protocol HTTPS on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 3468] Fri Jan 16 01:29:23 2009
[Thr 3468] *** WARNING => Connection request from (9/25/0) to host: 10.20.232.89, service: 4444 failed (NIECONN_PENDING)
RM-T9, U25, 600 SRAJEEV, GX_XP2BASE:0, 01:29:18, M0, W0, SEU_, 2/2 [icxxconn.c 2121]
[Thr 1660] Fri Jan 16 02:00:47 2009
[Thr 1660] Deactivated service 1080 for protocol HTTP on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 196] Fri Jan 16 02:00:57 2009
[Thr 196] Reactivated service 1080 for protocol HTTP on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 2292] Fri Jan 16 02:13:41 2009
[Thr 2292] Deactivated service 1080 for protocol HTTP on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 4108] Fri Jan 16 02:14:05 2009
[Thr 4108] IcmChangeService: change service 1080 for HTTP to 8080
[Thr 4108] Reactivated service 8080 for protocol HTTP on host: "dlwsdv11"(on all adapters) (timeout=30)
[Thr 4208] Fri Jan 16 02:15:24 2009
[Thr 4208] *** WARNING => Connection request from (8/24/3) to host: 10.20.232.89, service: 4444 failed (NIECONN_PENDING)
Regards,
vishnu
Edited by: vishnuarigela on Jan 16, 2009 10:05 AM
Edited by: vishnuarigela on Jan 16, 2009 10:20 AM

Hi Olivier,
I know its been more than an year since the last time I have posted on this thread.
The problem still persists, I have made the necessary changes as you have suggested,
made the necessary changes to the logical port number.
The error has changed to no extended error message (SOAP_ESERVER).
In sm21:
SOAP Runtime: SOAP Runtime exception: 112 occurred in method XP_READ_TAG of class CL_SOAP_XP at position 1
SOAP Runtime: Exception message: no extended error message (SOAP_ESERVER)
dev_rfc:
ERROR 01:01:48: SOAP Application CL_SOAP_APPLICATION_CLIENT
IF_SOAP_APPLICATION_CS~EXECUTE_PROCESSING() A SOAP Runtime Core
Exception occurred in method XP_READ_TAG of class CL_SOAP_XP at
position id 1 with internal error id 112 and error text no
extended error message (SOAP_ESERVER) (fault location is 1 ).
Any suggestions would be greatly appreciated. I have looked up on sdn, however was
unable to find a solution.
I have opened another thread under Netweaver Administrator with the subject SOAP Exception,
I apologize if it was a mistake.
Regards,
Vishnu.
Edited by: vishnuarigela on Feb 11, 2010 9:36 AM
Edited by: vishnuarigela on Feb 11, 2010 9:37 AM
Edited by: vishnuarigela on Feb 11, 2010 9:38 AM
Edited by: vishnuarigela on Feb 11, 2010 11:46 AM

Error When canceling the released idoc ?

Similar Messages

Maybe you are looking for