Mysterious routing problem / interface determination

Hi,
I have a very very strange routing problem with XI.
A message is sent from R/3 to XI and then send via adapter to an external party. The routing is configured well. But sometimes I have the following problem:
A message is received by XI (from R/3). The receiver is determinated. Although an interface determination and receiver agreement is configured, the trace shows "no interface determination fpr party xyz and service abc found". The very strange thing is that finally the receiver interface DELINS.DELFOR01 with namespace urn:sap-com:document:sap:idoc:messages is set!!
Finally, the error message is "no receiver agreement found for "... DELINS.DELFOR01, urn:sap-com:document:sap:idoc:messages", which is reasonable because this receiver interface has never ever been configured!
Any idea why the interface determination cannot be found and nevertheless a completely wrong receiver interface is set?
This error occurs just sometimes for certain partners, but not always with all messages for these partners!
Help appreciated!
Christopher

Hi,
all routing objects are 100% correct. Particularly the receiver service has definitely no DELINS.DELFOR01 interface, but nevertheless the Integration Runtime tries to send the message to this interface. Another strange thing is that in the trace there is the warning "no interface determination for party xxx and service xxx found".
By the way: The Receiver Determination was configured to terminate message processing when no receiver can be found.
CHRIS

Similar Messages

Receiver determination(or Interface determination) and conditional routing

I have a flat file to flat file scenario. Based on the input file content, I want to route data to the receiver.
My source flat file contains several IDOC details. Assume two fields FIELD1 and FIELD2 in different segments of the IDOC. My requirement is if FIELD1 of an IDOC = "US" and FIELD2 of the same IDOC = "CA", then that IDOC's details needs to be passed to the receiver.
I have implemented the above condition at interface determination.
But the problem is:
Assume there are 3 idocs in the input file.
FIELD1 of IDOC[1] = 'US' and FIELD2 of IDOC[1] = 'GL'
FIELD1 of IDOC[2] = 'UK' and FIELD2 of IDOC[2] = 'EN'
FIELD1 of IDOC[3] = 'BR' and FIELD2 of IDOC[3] = 'CA' .
Now none of the IDOCs in the input satisfy my requirement and hence the message mapping should not be called at all. But in my case its failing because FIELD1 of IDOC[1] and FIELD2 of IDOC[3] together are satisfying the condition and hence the message mapping is called.
But I need to check this condition IDOCwise. Both the conditions to be satisfies in the same IDOC.
I am thinking that contexts are not being taken care.. It just see the whole file together and not IDOCwise.
Can someone help me on the same. Please let me know if more information is required.
Thanks,
Shobha

>
Shobha HB wrote:
> I have a flat file to flat file scenario. Based on the input file content, I want to route data to the receiver.
>
> My source flat file contains several IDOC details. Assume two fields FIELD1 and FIELD2 in different segments of the IDOC. My requirement is if FIELD1 of an IDOC = "US" and FIELD2 of the same IDOC = "CA", then that IDOC's details needs to be passed to the receiver.
>
> I have implemented the above condition at interface determination.
>
> But the problem is:
> Assume there are 3 idocs in the input file.
> FIELD1 of IDOC[1] = 'US' and FIELD2 of IDOC[1] = 'GL'
> FIELD1 of IDOC[2] = 'UK' and FIELD2 of IDOC[2] = 'EN'
> FIELD1 of IDOC[3] = 'BR' and FIELD2 of IDOC[3] = 'CA' .
>
> Now none of the IDOCs in the input satisfy my requirement and hence the message mapping should not be called at all. But in my case its failing because FIELD1 of IDOC[1] and FIELD2 of IDOC[3] together are satisfying the condition and hence the message mapping is called.
>
> But I need to check this condition IDOCwise. Both the conditions to be satisfies in the same IDOC.
>
> I am thinking that contexts are not being taken care.. It just see the whole file together and not IDOCwise.
>
> Can someone help me on the same. Please let me know if more information is required.
>
> Thanks,
> Shobha
The ideal solution to your scenario is to redesign the interface as below;
1. Receive the file.
2. Do a 1: N mapping (this should split your message into multiple Messages)
3. On this message you can do the required check. Now only the required field for the particular IDoc will be part of the check and it will not mix with other Idocs.
Will this do? Else please provide more details

Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found

We have a SOAP to PROXY scenario Which is in Production.
We keep getting the Error:
" Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found on host XXXXXX, ProgId =AI_RUNTIME_XXX.
We are using Standard Receiver Determination with single receiver without any condition. And no mapping being used in interface determination.
What are all the possible situation where we face such as this issue in Production.

Please check the SAP note
# 1706936 - messages fails with error java.lang.RuntimeException Bean SMPP_CALL_JAVA_RUNTIME3 not found
1944248 - PI unstable due to JCO_SYSTEM_FAILURE mapping issues

EOIO Problem in the Interface Determination

Hi All,
I have two different source systems (BUSSYS111 , BUSSYS222) and one target system BUSSYS999 (SAP System). I have two different mappings in each interface
Interface 1:
BUSSYS111 -> BUSSYS999 (file1 -> RFC, file1 -> JDBC, without BPM, split mapping)
Interface mappings:
Flow1 : BUSSYS111_File_To_BUSSYS999 (FILE -> RFC)
Flow2 : BUSSYS111_FILE_TO_BUSSYS111 (File -> JDBC)
Flow2 should execute only if the Flow1 is successful (RFC call is successful).
Interface Determination for Interface 1
Sender: BUSSYS111
Interface: Source Interface1
Receiver : BUSSYS999
Maintain Order at runtime Checked.
Receiver Interfaces
BUSSYS111_File_To_BUSSYS999 (Result of Flow1 & Flow2)
BUSSYS111_FILE_TO_BUSSYS111
The queue that is getting generated is *XISERIALIZE0011_BUSSYS999*_ (EOIO)
Interface 2:
BUSSYS222 -> BUSSYS999 (file1 -> RFC, file1 -> JDBC, without BPM, split mapping)
Interface mappings:
Flow1 : BUSSYS222_File_To_BUSSYS999 (FILE -> RFC)
Flow2 : BUSSYS222_FILE_TO_BUSSYS111 (File -> JDBC)
Flow2 should execute only if the Flow1 is successful (RFC call is successful).
Interface Determination for Interface 1
Sender: BUSSYS222
Interface: Source Interface1
Receiver : BUSSYS999
Maintain Order at runtime Checked.
Receiver Interfaces
BUSSYS222_File_To_BUSSYS999 (Result of Flow1 & Flow2)
BUSSYS222_FILE_TO_BUSSYS222
The problem here is in both the cases above, the interfaces seems to be independant. But sometimes for some messages the same queue *XISERIALIZE0011_BUSSYS999*_ is used and for some, a different queue is generated.and if the same queue is used in both the cases, the first interface fails, then the second one is going into holding state.
Can any one help to resolve this issue without going for the BPM (as it would be a design change) and it is already in production.
Thanks in Advance
Anil

Hi,
in the documentation
Interface Determination - Enabling Application-to-Application Processes - SAP Library
its mentioned as
You specify manually to which inbound interface at the receiver the message is to be forwarded. You can also specify the mapping that is to be executed. If you specify more than one inbound interface, you can specify conditions for forwarding the message to the inbound interfaces. These conditions are evaluated at runtime.
so better to raised it to SAP.
Reg,
avinash M

Problem in Interface determination for multiple MM

Hi experts,
i designed an IDOC to Jdbc scenario.
The particular thing is that I have TWO message mappings to apply for the same source and same target.
Hence, I have in my directory two scenarios with :
- same Reveicer Determination
- same Interface Determination
- differents Receiver agreements (i have two Communication Channels)
In my interface determination, I have configured a standard Interface determination with my two interface mappings to apply.
My problem is when I send an idoc, the result should be for my two interfaces differents payloads to inject to the database, but I get the same payload for both interfaces with the same namespace...it looks like it only use one Interface mapping instead of both...
It is driving me crazy...
Any help would be greatly appreciated
Kind regards,
Jamal

Hi,
i have the same receiver.
I do have two interface mappings in my interface determination. The problem is that it uses the same for both interface.
If I use enhanced ID, i can only specify one Interface mapping.
What I want :
- sender A - Message mapping 1 - receiver A
- and also sender A - Message mapping 2 - receiver A
when the idoc is sent.
what I have right now (though my configuration seems to be right) :
- sender A - Message mapping 1 - receiver A
- and also sender A - Message mapping 1- receiver A
Thanks a lots,
Jamal

HTTP to RFC Interface Determination problem

Hi experts,
I am doing HTTP <-> RFC scenario mentioned in blog
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
almost everthing is done; but while configuring the interface determination, i am not able to see the inbound interface.
your valuable help would be appreciated
Regards
Sumit Bhutani

Hi Bhavesh,
Thanks for your quick response; this problem has been resolved, but while testing my scenario using RWB i am getting this error.
<?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="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read payload from the message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please suggest on this
Thanks
Sumit

Problem in Interface Determination

Hi All,
While trying to do webservices using webdynpro i was able to do the repository part without any errors but while trying to do configuration i'm facing a problem in interface determination.
I'm unable to find my interface mapping in the interface determination.
While trying to search for the interface mapping its showing me as "no objects found".
Could anyone help me out in this regard.
Thanks in Advance
Madhu

Hi,
As said by Moorthy, you should able to see interface mapping.You just Copy the interface mapping name from IR and insert at Interface Mapping in interface determination.To insert Interface mapping , right click choose Insert option from context.Save & activate Interface determination.If it is activated successfully every thing is ok.Otherwise once you should check as said by Moorthy and check Namespace of Interface too.Hope this will solve your problem.
Cheers
Tiger Woods
Note:Give the points for helpful answers

Condition in Interface Determination giving problem - URGENT!

Hello experts,
In my scenario I have one idoc posted from the SAP R/3 and I need to write max of 3 files in the same receiver file system based on some condition i.e. based on the value of some field in the incoming idoc.
What I have done is in my interface determination, I have given that condition for all the 3 inbound interface. that is in the condition field in interface determination, for each inbound interface I chose that perticular field in idoc and gave the condition for which that interface should run.
Now when I am pusing an idoc, if that idoc contains only one condition than my interface is working fine by creating only that file. I have checked this for all 3 files by sending 3 different conditions in 3 idocs. It creates 3 different files for 3 idocs.
But if I send all 3 conditions in one idoc (since idocs can have multiple segments - in few segments i am giving one condition and in few others the 2nd conditon and in the rest the 3rd condition), I expect all 3 files to be created in my file system with data fulfilluing only that perticular condition. but this is not happening. In interface determination only one of the 3 is getting executed. Rest 2 is ignored and i cannot trace it anywhere (RWB, SXI_MONITOR etc)
I have tried all possible combinations but this is not working if i send in 1 single idoc?
Please help me in solveing this as this is a production issue and they cannot send 3 diffent idoc for 3 conditions. Where am i going wrong?
Waiting for your responses.
Thanks,
Yash

Hi Jakub,
My scenario is one idoc say IDOC 1 and 3 files says FILE1, FILE2 and FILE3. Now the target message type for these three files are MT_FILE1, MT_FILE2 and MT_FILE3 (3 different message types).
The only catch point here is i have 2 different interface for creating FILE3 (same message type but different mapping, interface etc). Each interface is based on a condition.
Now when I send one doc which includes condition for only FILE1 and FILE2, it creates 2 file.
If I have condition of only FILE3 (one condition of FILE 3 as FILE3 has 2 conditions) and FILE2, it creates both files.
If I have both condition for FILE3 and FILE2, it creates FILE3 with only one condition and FILE2.
If i have condition for FILE1, FILE2 and both conditions for FILE3, it creates FILE1 and FILE2 both no FILE3 at all.
I guess the problem might be that I have same message type for both conditions for FILE3 but I m not sure. Let me try by creating seperate message type for both and see. But is there any other problem?
Yash

Condition based Interface determination

Hi ,
Environment : PI 7.1.
Scenario : File to Proxy.
In this scenario , We have a single file interface which reads a file and routes the data to two different inbound interfaces.
Steps followed to do this -
>>Defined two inbound interfaces interface1 & interface2.
>>Both interfaces are pointed to same ECC system.
>>Read the file using a single sender file communication channel.
>>Define receiver ECC in the receiver determination.
>> Define interface determination based on a value of a field in the file structure(source structure). Used XPATH to define this content based routing and selected operation mapping specific to the interface.
1 sender agreement
1 receiver determination ( not using enhaced receiver determination because we have only one receiver)
1 interface determination which has two receiving interfaces based on XPATH condition ( maintain order runtime is checked)
2 Receiver agreements.
2 Communication channels.
For example if you have 10 lines in a file , out of which if 5 lines has a value related to interface 1 & 5 lines has a value related to interface 2. It should push the data into two different proxies as configured.
We are facing a problem in this scenario -
There is no consistency in the logic. Some times it runs interface 1 & some time it executes interface 2.
based on condition 1 it routes the data to interface 1 successfully but the structure is not getting created for interface 2 so it is giving an error stating the interface 2 structure is not available.
In SXMB_MONI the branching steps show two subnodes but if you see the log it shows that in subnode 1 the sender is sender interface & the receiver is interface 1 based on the filter condition. If you see the log for subnode 2 then it shows the sender is sender & the receiver as interface 2 below that it shows another entry which shows the reciver interface is interface2.
Please evaluate and let us know if the approach we are following works or not. If there is any limitations please let us know how to achive this.
Regards,
Reddy

Hi,
Your design is correct but here you missed one point. Here the message is send either to receiver1 or receiver2 depending on the condition but not both. As this does not result in multiple messages with the same payload because only one condition can ever be true at runtime. For more details see the below link
http://help.sap.com/saphelp_nw04/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
If you want to create multiple message then you need do 1:n mapping :
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID2056393550DB10021342992851308291End?blog=/pub/wlg/2927
Shweta.

Condition for interface determination

Dear all,
I would like to choose a target inbound interface depending on values in a field.
The problem is, that the source field has occurency 0...unbounded so that I check
the same field twice.
Example:
/TestMessage/Field1 = "A"
AND
/TestMessage/Field1 = "B"
To route the message to the desired inbound interface we need at least two occurencies
of source field "Field1". One with value "A" and one with value "B".
But he seems to check if Field1 is "A" and "B" so he will never use the desired inbound
interface. Do I have a chance to check values of two occurencies of one field or do I need
to use enhanced interface determination?
Thanks
Chris

Hi Christian,
You interface determination condition should work. e.g for one of my interface I am using following interface determination condition to send the msg to specific inbound interface.
(/p1:MT_Input/Recordset/row/Key = 10 AND /p1:MT_Input/Recordset/row/Key = 20)
The condition check if there is any "Key" with value 10 and othet with value 20 and then only it selects the desired output
inbound. The order of value 20 and 10 doesnt matter. Also only when both the values are there, then also inbound interface is
selected.
Can you provide your sample payload here?
Pooja Pandey

Multiple Interface Determination

Hello everybody,
I am working on the following szenarion:
- one sender and sender interface (incoming IDOC).
- one receiver with two different receiver interfaces (outgoing BAPIs). For one of these interfaces there exit two different interface and message mappings. So, 1 incoming interface => 3 outgoing with 2 different interfaces
So in the interface determination I want to rout the message by use of XPath expression to use one of the two interface (no problem at all), but also to choose one of two interface mappings for the same interface. If I try this by creating three lines in the interface determination and using different XPaths, the last entered interface always is deleted automatically.
Thanks for your help.

Hi,
To do what you want you may have to use both Receiver Determination and Interface Determination. XPath expressions can be used in both places.
In Receiver Determination, you will have 2 receiver services. Then, in one of the receiver services, you will have 2 Interface Determinations. So, you will end up with something like the following:
Receiver service1: interface1
Receiver service2: interface1, interface2
Regards,
Bill

Why does PI pickup wrong interface, in the interface determination step

I configured a scenario in id.
In ID, i can see the following when i open the interface determintation that i created.
Sender Details:
Communication Component:Sys_Sample_One_D
Interface: UserMasterQuery_Outb
Namespace: urn:sample.com:I_Legacy_JDBC_Application
Receiver Details:
Communication Component:Sys_Sample_Two_D
Interface:EmployeeEmailProcessing_Inb
Namespace:urn:sample.com:I_Legacy_FileApplication
Interface Mapping: UserMasterResultset_to_EmployeeEmail
But when i execute the scenario, and when i see in the the Interface determination pipeline step in moni, it is showing:
<SAP:Main..
     <SAP:Sender>
          <SAP:Service>Sys_Sample_One_D</SAP:Service>
          <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
     </SAP:Sender>
     <SAP:Receiver>
          <SAP:Party agency="" scheme=""/>
          <SAP:Service>Sys_Sample_Two_D</SAP:Service>
          <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
          <SAP:Mapping notRequired="Y"/>
     </SAP:Receiver>
     <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
In the <SAP:Receiver> section, the <SAP:Service>Sys_Sample_Two_D</SAP:Service> is as per my configuratioin,
but <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface> is not the interface that i configured as the receiver interface, infact this is the sender interface.
the correct receiver interface to be pickedup is EmployeeEmailProcessing_Inb
and finally it is showing the error in moni, in the Technical Routing pipeline step
<SAP:AdditionalText>No standard agreement found for , Sys_Sample_One_D, , Sys_Sample_Two_D,
urn:sample.com:I_Legacy_JDBC_Application, UserMasterQuery_Outb</SAP:AdditionalText>
the error i can see later, but i would like the right interface to be determined by PI,
i refreshed various caches etc, recreated the config objects in ID, but it is not picking up the right receiver interface.
any inputs appreciated, to find out what went wrong.
thanks,
Madhu.

Two threads which has some discussion regarding this happening in PI 7.1.Hope it gives you some help.
Incorrect Receiver Determination
Reciver Problem
And, as you have checked your Interface determination similarly can you also check your receiver determination.
Does the receiver determination have the correct receiver at the bottom ?

Interface determination Issue in PI7.1

Hi ,
I am working on PI 7.1
Problem 1:
I am not able create any interface determination objects. There is a lock object created everytime I use the wizard. Unlocking the object and run the cache refresh has not helped..
I am able to create the interface determination manually after removing the lock. But now I am not able to associate a operation/interface mapping to the Interface determination . After I selected a message/service interface in the Interface determination, I clicked on the mapping option. The possible mapping was showed up on the list. But once I select one option from the list it does not show up in the interface determination. The field remains blank.
Problem 2:
I am unable to open the existing interface determination also. These interface determinations are present in the DEV environment.I have taken the system copy of the dev environment on the UAT environment.I am getting the below error when i try to open the interface determination
====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
====================================================================
== Content from the LogHandler =====================================
====================================================================
#300 11:56:48 [AWT-EventQueue-2] WARNING com.sap.aii.utilxi.swing.toolkit.ButtonPanel: Special button of type 4 was not added in order (class com.sap.aii.utilxi.swing.toolkit.ButtonPanel)
#299 11:56:48 [AWT-EventQueue-2] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)

Hi Shilpa,
Ask your basis guys to check the SP level of JAVA components in system component information of your PI7.1 system............ask them to check for patches for your SP level of PI7.1 or upgrade to a higer SP level...........
Also try this from your PI IB webpage, go to Administration - JAVA web start administration - then click on execute link in the status window and do a reinitialization of your JAVA web start...........then close your ID and reopen your ID........then create your interface determination again in ID...........
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:05 AM
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:25 AM

Error while opening the Interface determination

Hi,
I am working on PI system(unix platform) which is a system copy(from a windows platform).
When i tried opening few interface determinations which are already present in ID, it gives me following Error.
====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:643)
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:612)
     at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:160)
     at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)
     at $Proxy26.read(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)
     at $Proxy27.read(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sap.aii.ib.clsif.login.BeanProxy.invoke(BeanProxy.java:114)
     at $Proxy27.read(Unknown Source)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:101)
     ... 39 more
Caused by: java.io.InvalidClassException: com.sap.aii.ib.bom.gen.container.ContainerElementState$XsdSimpleState; local class incompatible: stream classdesc serialVersionUID = 42, local class serialVersionUID = -6470496719860432109
     at java.io.ObjectStreamClass.initNonProxy(Unknown Source)
     at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
     at java.io.ObjectInputStream.readClassDesc(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.readObject(Unknown Source)
     at java.util.Hashtable.readObject(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.readArray(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.readObject(Unknown Source)
     at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.readResult(P4InvocationHandler.java:303)
     at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:138)
     ... 52 more

Hi,
This is the problem with the XI system. You have to add some patches.
For that check this link same problem solved here.
PI 7.1 : Java exception creating new "Integration process"
Thanks.

Do I need a router to interface with my wireless laptop and printer, or can booth tooth.

Im having a problem interfacing the HP B210 all in one wireless printer to my ASUS wireless Laptop. Do I need a router or can I some hoe make the wireless connection using my blue tooth on my laptop. Please help.

Well, the printer does not have bluetooth so that will not work.
However, you can connect to it directly via wi-fi on your laptop. From the front of the printer go to: Setup > Network > Restore Network Defaults.
Now, on your PC, look for a wireless network beginning with "HP". Join it. There is no password.
Now, go to Control Panel > Printers and Add a Printer.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Mysterious routing problem / interface determination

Similar Messages

Maybe you are looking for