RFCLook up error in PI7.3

We upgraded the PI system from 7.0 to 7.3 recently and we are using RFCLookup in the interface mapping.
When I am doing the Message mapping test I am getting the below error .
Runtime exception when processing target-field mapping /ns0:mt_XXXXXXXX_XXXXX/Order/Header/DChl; root message: exception:[Java.lang.NullPointerException: while trying to invoke the method com.sap.aii.mapping.api.DynamicConfiguration.put(com.sap.aii.mapping.api.DynamicConfigurationKey, java.lang.String) of an object loaded from local variable '<12>'] in class com.sap.xi.tf._mm_XXXXXX_RFCLookUp_ method RFCLookupHDR[0000000775, BS_ERP_XXX_400, CC_Receiver_RFC_XXXXXXX, com.sap.aii.mappingtool.tf7.rt.Context@4b77308e] See error logs for details
I found 2 RFCLookups used in the interface mapping.
How to use the RFCLookup in PI7.3
Thanks
Naresh N
Edited by: Naresh Nelapatla on Feb 27, 2012 3:03 PM

Please make sure that you configure parameterised mapping in the new configuration. Go to parameter tab and see whether you set value for communication channel and so.
Refer this document which is same for PI 7.1 and 7.3
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35?QuickLink=index&overridelayout=true&38543036566484

Similar Messages

401 unathorized error in PI7.1

Hi experts,
We are getting the 401 unauthorized error in PI7.1 as shown below . PLease check and assist ASAP.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Rgds
Kishore

In Runtime workbench this is what i have observed in the Cache status overview,
The Central Adapter engine , Mapping Runtime cache( Central Adapter Engine) are showing up in red.
In the Mapping Runtime Cache the error is as follows:
Connection to system DIRECTORY using application DIRECTORY lost. Detailed information: Error accessing "http://sapqpi01:50000/dir/hmi_cache_refresh_service/int?container=any" with user "PIISUSER". Response code is 401, response message is "Unauthorized
We have accomplished delta cache refresh, complete cache refresh in SXI_CACHE.
Can you anyone suggest what needs to be done to refresh this cache in Cache status overview?
Rgds
Kishore

JCO_COMMUNICATION_FAILURE error in PI7.0

Hello
Till date we have been working with SAP XI 3.0 from last one year, and I have to work with PI 7.0. I creatd a sample scenarion "File to File"in PI 7.0. The sender adapter is picked the file. in SXMB_MONI Error ID showing JCO_COMMUNICATION_FAILURE. Plz suggest me how to resolve this problem.
Thanks
san

Hello San,
Your AI RUNTIME JCOSERVER and AI DIRECTORY JCOSERVER (names - not exact I think) should exist at SM59 of your ABAP stack as well as under JCORFC PRovider in Visual Admin.
Go to the Post isntall steps of XI 3 Install guide (most of the steps are relevant for PI7 also) (page 31 onwards) and you will have all the necessary details. There should be two more RFC destinations SAPSLDAPI adn LCRSAPRFC alongwith the above two.
However the other two are for communicating with SLD mainly.
Hope this helps.
Thanks,
Bhaskar

Reciever Determination condition error in PI7.1

Hi Experts,
I done File to File scenario in XI with multiple recievers based on FileName in Reciever Determination, i use context object(FileName, http://sap.com/xi/XI/System/File) in Expession editor, this condition was working in XI, but in PI7.1 it is not working, it is giving error like below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem evaluating a condition: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone please help me out of this.
<removed_by_moderator>
Edited by: Juan Reyes on Oct 1, 2010 2:53 PM

Hello ,
I have the same issue with PI system and all IDOCS in PI are in error state.
The issue in our case was the condition for the interface was visible from integration directory in receiver determination , but its not replicated in ABAP stack ( tcode sxi_cache ).
so we have gone in receiver determination in Integration builder-->Receiver Determination
Select a object --> click on Edit mode
Add a space in the description , click on SAVE. Then activate it.

Reg Sender IDoc error in PI7.3

Hi All,
I am facing the below error while triggering an IDoc from ECC to PI. I could see the error in SM58 and PI log as below:
[JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT, Managed_Application_Thread|XI_IDOC_DEFAULT Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@24a49d74 for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException (raised by system |PI_AAE_IDOC)
Can anyone please help me on the same.
The resource adapter configurations are deleted and created again. Also the RFC destination is working fine.
Cheers,
Neethu

Neethu,
Can you check if you are able to ping PI from the TCP Ip rfc destination in ECC.
Also the program id in the RFC destination created in SAP should match program id in InboundRA
Also the gateway parameters in the inboundRA in PI should be set properly. If you are setting the Gateway to be PI gateway then enable Local to true. If you are using SAP Gateway then set Local to false.

Idoc configurations in PI7.3

Hi Experts,
For an Idoc scenario prior to PI 7.3, RFC destination, port, logical system and partner profile needs to be created in case of outbound Idoc scenario and again at XI side we need to create RFC destination, port and loading of meta data....
Is the same is applicable for PI 7.3 as well? since Idoc resides in AAE in PI 7.3, I believe there could be some changes applicable for these settings of Idoc....
Pls provide your inputs.....

Hi,
Along with the links provided by Phani and Gayatri you can laso refer this thread for IDoc configuration in PI7.3
IDOC settings from sap r/3 to sap pi7.3
IDoc Packaging in PI7.3
http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/4096a6b3-3dc3-2d10-bf87-f63d5340a916
Configuring PI 7.30 Java IDoc Adapter
PI/XI: PI 7.3 New Java based IDOC adapter's configuration (sender, receiver) - teaser
IDoc Acknowledments in PI7.3
acknowledge handling for IDOC_AAE in sap PI 7.3
IDoc_AAE acknowledgement handling in PI 7.3
IDoc related error in PI7.3
Processing error in Idoc_AAE sender channel
Hope its informative.
Regards,
Amol

Problem to analyse mapping error

Hi all,
I have a problem to analyse a BPM mapping error on PI7.1. The szenario is as follows: I have 3 different containers (Abstract Interfaces) which data is used to determine the content of a result container.
E.g:
ABSTRACT_INTERFACE_1
ABSTRACT_INTERFACE_2 -> Mapping -> ABSTRACT_RESULT_INTERFACE
ABSTRACT_INTERFACE_3
If have quouted the source interfaces (cardinality 1 for each interface) in my operation mapping and configured the transformation step accordingly. The operation mapping alone works in the integration builder test environment. When I execute the BPM process, the mapping fails. Unfortunately the is no information in the trace leaf of the respective container information. Writing data to the mapping trace doesn't work neither.
Has got anybody an idea what might be the problem?
Kind regards,
Heiko

Hi Heiko,
Pls, do the following:
1. Build a java mapping which is going to write the payload content before the message mapping.
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationException;
import java.io.File;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
public class InputFileWriter implements StreamTransformation {
    public void setParameter(Map map) {
    public void execute(InputStream in, OutputStream out)
    throws StreamTransformationException {
        try{
            File f=new File("C:\PayloadContent.xml");
            FileOutputStream fosPayload = new FileOutputStream(f);
            byte[] content= new byte[in.available()];
            int c;
            int i=0;
            String sb = "";
            while ((c = in.read()) != -1){
                content<i>=(byte)c;
                sb += (char)content<i>;
                i++;
            fosPayload.write(sb.getBytes());
            fosPayload.close();
            out.write(sb.getBytes());
            out.close();
        }catch(Exception ex){
            ex.printStackTrace();
2. Add the javamapping to your interface mapping putting before of message mapping.
3. Run your scenario.
4. Check the file
C:\PayloadContent.xml
5. Test your message mapping in with PayloadContent.xml
And tell me what happened.
Regards
Ivan
Edited by: Jose Iván Reyes Arteaga on Jul 16, 2009 6:05 PM

Error while testing SAML service in PI7.1

Hello all,
I am creating a SAML secured service in PI 7.1
I have used WS adapter in sender communication channel and reciever as RFC adapter to extract data from the system.
I have done the necessary config in sender and receiver agreement and created the wsdl manually.
Now to test that service i have created another component as the client.
The sender is the SOAP channel and in the receiver, WS adapter is used.
With these basic configurations, i have created another wsdl file which invokes my previous service.
When i tested the new wsdl i get an error.
<SAP:Code area="INTERNAL">WS_LOGICAL_PORT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while determining logical port Cannot find logical port for agreement 34CBAC01EBEC3F15813332AC002BD3CF and interface http://atl.tarpon.com/SAPGetAddressSAML_C.MI_Inbound_SAPGetAddSAML_C</SAP:Stack>
Kindly guide me as to what is to be done for creation of logical port in *NWA as this tool is available for PI7.1 for me.
Regards,
Kevin

Hi Kevin,
What I meant to say is that there are multiple levels of settings required to enable SAML based communication. I wanted to ask you if you have already done those configurations.
See the image given at following URL.
http://help.sap.com/saphelp_nwpi71/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm
As you can see there is multiple parties involved in the overall SAML authentication process.
May be following blog will be helpful.
SAML Made Simple!
Regards,
Vandana.

Error in adapter module Upgrade PI7.11

Hello,
After upgrade from XI3.0 to PI7.11,I am trying to adapt code of an adapter module in order to use it in new version.
I have changed the code ,there were no compilation errors and it was deployed successfully.
But when trying to test the scenario ,I am getting following error:
<code>ADAPTER.JAVA_EXCEPTION</code>
               <text>javax.ejb.EJBException: (Failed in component: sap.com/ValidationModule7.11_EAR) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sapcons.xi.af.validation.ValidationModuleBean711.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sapcons.xi.af.validation.ValidationModuleBean711@4dee79d1 for bean sap.com/ValidationModule7.11_EARxml|ValidationModule7.11_EJB.jarxml|ValidationModuleBean711 in application sap.com/ValidationModule7.11_EAR.; nested exception is: java.lang.NullPointerException: while trying to invoke the method com.sap.engine.interfaces.messaging.api.MessageKey.getMessageId() of an object loaded from local variable 'msgKey'
java.lang.NullPointerException: while trying to invoke the method com.sap.engine.interfaces.messaging.api.MessageKey.getMessageId() of an object loaded from local variable 'msgKey'
I am nowhere using variable 'msgkey' in my code.
I was using getMessageId() method and because of this error,I have changed the code such that I am not using this method at all.
After this change ,I have deployed the module again,and the strange part is I am still getting the same error.
Just to be sure that I have deployed the changed code,I created an altogether new module ValidationModule7.11_EAR(it was ValidationModule_EAR before) and deployed it,I am sure ,I am not using getMessageId() method at all,but I am getting the same error (as mentioned above).
I have no idea why I am getting the same error.I can see in the error message that my new module is called which doesn't use this method.
Can anyone please suggest apart from saving the Bean after code changes and redeploying the code,what needs to be done.
(Rebuilding the project,etc.)
It would be great if I can get some inputs on this strange behaviour.
Thanks a lot.
Best Regards,
Shweta

Hello Stefan,
Thanks for your reply.
I have created my new module with a different JNDI name.
Also,I have verified that there is a link to the interface com.sap.aii.af.ifc.facade in application-j2ee-engine.xml .
This was the code which I was trying to adapt:
if((MessageContext)inputModuleData.getPrincipalData() instanceof MessageContext)
                MessageContext messsageContext = (MessageContext)inputModuleData.getPrincipalData();
                Message message = messsageContext.getMessage();
                Attachment rootDocument = message.getRootDocument();
                Object data = rootDocument.getData();
                if(data instanceof Binary)
                    Binary bin = (Binary)data;
                    request = bin.getBytes();
                    String messageID = "1232";
                    if(dir == Direction.INBOUND)
                        amk = new AuditMessageKey(messageID, AuditDirection.INBOUND);
                    else
                        amk = new AuditMessageKey(messageID, AuditDirection.OUTBOUND);
But I was getting errors like MessageContext not recognized and also,for the statement:
Attachment rootDocument = message.getRootDocument();
I was getting an error in statement :   if(data instanceof Binary) as following imports weren't recognized.
import com.sap.aii.messaging.lang.Binary;
import com.sap.aii.messaging.mo.*;
So I used import com.sap.aii.af.service.cpa.BinaryData; and following code
Object obj = null;
               Message message = null;
               obj = inputModuleData.getPrincipalData();
                          if(obj instanceof BinaryData)
                     message = (Message)obj;
                    BinaryData bin = (BinaryData)obj;
                    request = bin.getData();
                     String messageID = "1232";
                      amk = new MessageKey(messageID, message.getMessageDirection());
Code was compiled correctly and deployed ,but I get this error with getMessageId() when I try to test it.You can see I am not using getMessageId() and msgkey anywhere in the code
Thanks for your help
Regards,
Shweta

Using Response Oneway bean in PI7.1 throwing error

Hi Folks
Has any body used Response One way bean in PI 7.1 ? . I have a scenariofor File-RFC -File in which I am trying to Implement it I have gone through the blogs for File-RFC -File without BPM .
i have also gone through the documentation for adding the request response bean and one way response bean for PI 7.1 on help.sap.com . But unfortunately that blog is not working and also i tried all permutations and combinations for adding parameters as per help.sap.com for Pi7.1
I followed these links
http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/20cc5dc2180733e10000000a155369/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/20c210c20a0732e10000000a155369/content.htm
File-RFC-File Synchronous scenario error
I am getting a null pointer exception error in sender communication channel monitoring
Error: java.lang.NullPointerException
Please help in this regard
Thanks
Ninad

Has anybody used Response Oneway bean for File-RFC-File scenario in PI 7.1
My Response file is getting created but I ma unbale to delete my request input file even though my Sender communication channel is in delete mode and In communication channel monitoring its giving null pointer exception error
Can anyone check whats the issue in this ,
I am running this scenario on service pack 8 Pi 7.1
Regards
Ninad

PI7.1 error: no global key defined

Hi Experts,
I am getting an error when trying to open a message mapping in PI7.1: no global key defined. What does that mean? Can anyone shed some light on this? I've been unsuccessful in searching this error in SDN.
Regards,

Hi Sugata,
The solution provided by you is working in case we have XSD that are not having External References. However, when we tested the solution provided by you in one of the scenario where we have several XSDs referring each other, It does not work.
Also, we have found the link: http://wiki.sdn.sap.com/wiki/display/XI/ConvertingXSDtoSAP-PIcompatible+XSD
Thanks & Regards
Varun Goel

After Upgrade to PI7.1 getting Simple transformation error

HI Experts,
I have an Issue, the scenario which i', working its working properly in DEV, QA, PROD in PI 7.0, We upgraded the system to PI7.1
Unknown Simple transformation error in converting XML to internal table
Application error in mapping program , error text: Unknown Simple transformation error in converting XML to internal table An exception has occurred.
Can any one suggest related notes are suggestion.
appericate in advance for the solutions which you all provide me
Thank you
Venkat Anil

What kind of mapping is that ? Graphical, Java, XSLT, ABAP ?
The XML parser in 7.1 contains many subtle changes compared to 3.0
But this error sounds like a bug. Is there something special in the XML input ? is it wellformed-XML ?
CSY

PI7.1 EHP1 Java suppor packages LM-CORE Deployment ERROR

Hi,
I have installed PI7.1 EHP1 on Linux X86_64 /oracle 11.
Successfully Updated the ABAP Stack support packages to 7.11 SPS07 thru
SPAM, but During Java stack thru JSPM i have encountered follwoing
error for LS-CORE
7.11.7.3.
Error: 1. Item is skipped because of failed deployment of the item
sap.com_tclmwebadminflexstateview and because the applied error
strategy is oneErrorstop 1. Contains Aborted Deployment Component
sap.com_tclmwebadminflexstateview .
LOG::
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[/usr/sap/JXD/DVEBMGS00/j2ee/JSPM/log/log_2011_09_22_20_20_06/deploy_2011-09-22_20-56-07.log]/>
<!PATTERN[deploy_2011-09-22_20-56-07.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Sep 22, 2011 8:56:07 PM [Info ]:DC API is trying to connect to 'SJXD0001:50004'
Sep 22, 2011 8:56:07 PM [Info ]:DC API has Connected to 'SJXD0001:50004'
Sep 22, 2011 8:56:07 PM [Info ]:+++++ Starting D E P L O Y action +++++ [ deployerId=5 ] [ timerId=177]
Sep 22, 2011 8:56:07 PM [Info ]:Selected archives for deployment. [ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA
Sep 22, 2011 8:56:07 PM [Info ]:DC API got Session id='161',time:[id:#177, elapsed: 23 ms.].[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:component version handling rule is UpdateLowerOrChangedVersionsOnly.[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:deployment workflow strategy is safety deploy strategy.[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:Error strategies[ deployerId=5 ]:
Sep 22, 2011 8:56:07 PM [Info ]:error action 'DeploymentAction' is 'OnErrorStop'
Sep 22, 2011 8:56:07 PM [Info ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
Sep 22, 2011 8:56:09 PM [Info ]:clusterRestartTriggered for transactionId:161, clusterEventAction:cluster restart triggered
Sep 22, 2011 8:56:09 PM [Info ]:Caught exception [P4ConnectionException]. Because cluster restart has been triggered beforehand, assuming a cluster restart.
Sep 22, 2011 8:56:09 PM [Info ]:+++ Server is being restarted +++. The currently set engine start timeout is: 7200 seconds.
Sep 22, 2011 8:56:09 PM [Info ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
Sep 22, 2011 8:56:25 PM [Info ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
Sep 22, 2011 8:56:41 PM [Info ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
Sep 22, 2011 8:56:57 PM [Info ]:+++ Wait for server response +++. Elapsed: 48 seconds. Remainig to timeout 7151 seconds.
Sep 22, 2011 8:57:13 PM [Info ]:+++ Wait for server response +++. Elapsed: 64 seconds. Remainig to timeout 7135 seconds.
Sep 22, 2011 8:57:26 PM [Info ]:Wait for the operation 'Deploying' to finish
Sep 22, 2011 8:57:28 PM [Info ]:Assuming a subsequent restart of the server due to exception: [P4ConnectionException], message: Error. Check your available working servers. Error message: the requested server is not available
Sep 22, 2011 8:57:28 PM [Error ]:[ Exception ]::Unexpected exception during the notification of cluster listeners
Sep 22, 2011 8:57:28 PM [Info ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
Sep 22, 2011 8:57:45 PM [Info ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
Sep 22, 2011 8:58:01 PM [Info ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
Sep 22, 2011 8:58:18 PM [Info ]:+++ Wait for server response +++. Elapsed: 49 seconds. Remainig to timeout 7150 seconds.
Sep 22, 2011 8:58:36 PM [Info ]:Obtaining the deployment result from the server ...
Sep 22, 2011 8:58:37 PM [Info ]:Deployment result
Sorted Items -
     1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcsld~data.sda'
          Deploy status is 'Skipped'
          SDA : name 'tcslddata', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('FS', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
     2. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
          Deploy status is 'Skipped'
          SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
     3. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
          Deploy status is 'Skipped'
          SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
     4. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
          Deploy status is 'Skipped'
          SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
     5. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
          Deploy status is 'Skipped'
          SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
     6. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
          Deploy status is 'Skipped'
          SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
     7. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjebasicadminsapcontrolapp.sda'
          Deploy status is 'Skipped'
          SDA : name 'tcjebasicadminsapcontrolapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-ADM', dependencies :[( name 'tcjmx', vendor 'sap.com') , ( name 'adminadapter', vendor 'sap.com') , ( name 'tcjebasicadminsapcontrol~lib', vendor 'sap.com') ]
     8. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~com.sap.engine.customizing.ccms.sda'
          Deploy status is 'Skipped'
          SDA : name 'com.sap.engine.customizing.ccms', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826155427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'monitor', vendor 'sap.com') , ( name 'tcjmx', vendor 'sap.com') , ( name 'rfcengine', vendor 'sap.com') , ( name 'tcmonitoring~api', vendor 'sap.com') , ( name 'monitortree', vendor 'sap.com') ]
     9. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexflexcommons.sda'
          Deploy status is 'Skipped'
          SDA : name 'tclmwebadminflexflex_commons', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
     10. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
          Deploy status is 'Aborted'
          SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
     11. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
          Deploy status is 'Skipped'
          SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
     12. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
          Deploy status is 'Skipped'
          SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
     13. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.dbcontent.sda'
          Deploy status is 'Skipped'
          SDA : name 'com.sap.sl.ut.jddi.content', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('DBSC', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.sl.ut.jddi.schema', vendor 'sap.com') ]
     14. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
          Deploy status is 'Aborted'
          SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
Deployment Items -
     1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
          Deploy status is 'Aborted'
          Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop
          1. Contains Aborted deployment component:
sap.com_tclmwebadminflexstateview'.
          SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
          Composite Time statistics( ms ):
               1.Check composite version : 24
                    1.1.Check version:sap.com_LM-CORE : 1
                    1.2.Check contained SDAs versions : 23
               2.validate : 31
                    2.1.Check composite version : 31
                         2.1.1.Check contained SDAs versions : 31
               3.Persist in storage : 11
          Contained DCs:
               1.1 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_ear.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110823093938.0000
          2. Already deployed component has version:7.1107.20110823093938.0000'.
                    SDA : name 'tcsldcds~wsproxy_ear', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.2 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.namealloc.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110711084722.0000
          2. Already deployed component has version:7.1107.20110711084722.0000'.
                    SDA : name 'com.sap.lcr.namealloc', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.3 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctc~interface_lib.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110823083938.0000
          2. Already deployed component has version:7.1107.20110823083938.0000'.
                    SDA : name 'tclmctc~interface_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.4 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcslddpj2ee.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110823093938.0000
          2. Already deployed component has version:7.1107.20110823093938.0000'.
                    SDA : name 'tcslddp~j2ee', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.5 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.util.monitor.grmg.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110309073123.0000
          2. Already deployed component has version:7.1107.20110309073123.0000'.
                    SDA : name 'com.sap.util.monitor.grmg', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.6 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> apptracing.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110826165427.0000
          2. Already deployed component has version:7.1107.20110826165427.0000'.
                    SDA : name 'apptracing', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23

versions : 31
                         3.Persist in storage : 11
               1.22 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~cdsclient_lib.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110823093938.0000
          2. Already deployed component has version:7.1107.20110823093938.0000'.
                    SDA : name 'tcsldcds~cdsclient_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.23 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
                    Deploy status is 'Skipped'
                    Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                    SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.24 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_lib.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110823093938.0000
          2. Already deployed component has version:7.1107.20110823093938.0000'.
                    SDA : name 'tcsldcds~wsproxy_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.25 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> monitortree.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110826155427.0000
          2. Already deployed component has version:7.1107.20110826155427.0000'.
                    SDA : name 'monitortree', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.26 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110823093938.0000
          2. Already deployed component has version:7.1107.20110823093938.0000'.
                    SDA : name 'com.sap.lcr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.27 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
                    Deploy status is 'Skipped'
                    Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                    SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.28 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcmonitoring~sda.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110826155427.0000
          2. Already deployed component has version:7.1107.20110826155427.0000'.
                    SDA : name 'tcmonitoringsda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.29 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
                    Deploy status is 'Skipped'
                    Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                    SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.30 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
                    Deploy status is 'Aborted'
                    Description:'1. CFS Container reported an error. Check the causing exceptions for the reason for failure.
           -> [ERROR CODE DPL.CFS.0301] Error while notifying bootstrap about component "sap.com/tclmwebadminflexstateview". Collected error messages are: Collected bootstrap error messages ( appName:sap.com/tclmwebadminflexstateview) :
     /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/AC_OETags.js (No such file or directory)
     /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.html (No such file or directory)
     /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.swf (No such file or directory)
     /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/playerProductInstall.swf (No such file or directory)
                    SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.31 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
                    Deploy status is 'Skipped'
                    Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                    SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.32 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
                    Deploy status is 'Skipped'
                    Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                    SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.33 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.engine.heartbeat.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110826155427.0000
          2. Already deployed component has version:7.1107.20110826155427.0000'.
                    SDA : name 'com.sap.engine.heartbeat', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.34 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> dsr.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110826165427.0000
          2. Already deployed component has version:7.1107.20110826165427.0000'.
                    SDA : name 'dsr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.35 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtclmctccul~service_sda.sda'
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:7.1107.20110815124828.0000
          2. Already deployed component has version:7.1107.20110815124828.0000'.
                    SDA : name 'tclmctcculservice_sda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.36 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
                    Deploy status is 'Skipped'
                    Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                    SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
               1.37 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
                    Deploy status is 'Skipped'
                    Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                    SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
                    Time statistics( ms ):
                         1.Check composite version : 24
                              1.1.Check version:sap.com_LM-CORE : 1
                              1.2.Check contained SDAs versions : 23
                         2.validate : 31
                              2.1.Check composite version : 31
                                   2.1.1.Check contained SDAs versions : 31
                         3.Persist in storage : 11
Sep 22, 2011 8:58:37 PM [Info ]:+++ Deployment finished with status 'Error' +++.[ deployerId=5 ][#178: 149.398 sec]
Sep 22, 2011 8:58:37 PM [Info ]:+++++ End D E P L O Y action +++++[ deployerId=5 ]. Total time:[#177: 149.501 sec]

Source code has syntax error in SAP PI7.1 Mapping Test

HI All,
IN SAP P7.1 created simple two data types, message types and Message Mapping with only 2 fields. While testing the mapping in Message Mapping it is giving the error as
Source text of object Message Mapping: MM_Source_to_Target | http://abc.com has syntax errors:
Source code has syntax error:
I am able to activate the Datatypes and Message Types but not able to activate the Messge mapping.
Please if any body faced the same problem please give the solution.
One more thing is I am able to test the Message Mapping available in BASIS 7.1 Software Component objects. It is executing successfully...
but otherthan this SWC it not working success fully.....
Regards
Sridhar Goli

Hi David,
please check the default trace. It may contain the entry:
Error in compiling : java.io.IOException: Not enough space
If that's the case, maybe there's too little space for the swap file/device.
You should ensure that at least 2X (preferably 3X) of Heap (-Xmx) is configured as real swap
Hope that helps.
Regards,
Gábor Klauzer

Javawebstart error while opening IR and ID objects in PI7 and XI 3.0

Hi All,
When iam trying to open IR/ID objects in XI3.0 java webstart error occurs continously though iam deselecting java update statistics.
Pls help me out regarding this error.
C:\Documents and Settings\Administrator\Local settings\ Temporary Internet Files\Content.IE5\4X2C5RF7\repsitory[1].jnlp
Thanks&Regards,
Winston

Hi Winston,
Goto Administration in /rep.
Click on Java Web Start Administration - > Re-initialization and force-signing
Then try to open the IR and ID. This should work.
If it does not work then, do the following and paste the log.
Goto Control Panel - > Java -> Advanced->Java Console-> Show Console.
Then try to start the IR and ID.
You will get the error log.
Best Regards
Raghu.

RFCLook up error in PI7.3

Similar Messages

Maybe you are looking for