No interface found
Hello,
I am trying to send file to idoc. I get the following error.
Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MI_Material_Async_Out_9*</Trace>
<Trace level="1" type="T">select interface namespace http://dsouza.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
I have done the following.
1. CPA Cache refresh and all available cache refresh.
2. Test configuration - with payload and everything is green checked.
I have substantial time in searching sdn and unable to figure out the problem. Could you please help me.
Thank you.
William
Hi WILLIAM DSOUZA ,
In our production support we face same issue frequently, follow these steps which we follow to trace the error and solve that:-
1) In transaction SXMB_MONI in the very right of your message select your message then right click and copy all details of your message on a notepad
2) go to integration directory , click on the search button situated in the above left pan, then in the search window in the drop down meenu select interface determination, as you will select interface determination then in the bottom down window fillup the entries like sender service interface and receiver service and click on the button find
it will search your receiver determination click on the interface determination a new window will open, there you can find in the interface determination that is any condition? check that condition in your message payload and you will get the eroor
generally found errors in this case are as follows
a)when you will fill sender and receiver details in the receiver determination serach window then search comes with result that "No Interface found"
in that case you remove the receiver details and again search with only sender details then you will find what is the receiver service configured for this sender service. in case different receiver service is configured for this sender match it with your configured scenario
b) second error comes when you have given some condition on any tag for receiver determination and your payload is not satisfying that condition then it will give you no receiver error. then edit your payload and restart it again (for quality of service EO or EOIO)
Hope it may solve your problem
Thanks
Sandeep sharma
PS: if helpful reward points
Similar Messages
-
File-file,no interface found error
Hi, I am doing a simple file-file scenario testing. Following is the log from message monitor... Please let me know what other info you would need to help me the issue. Thank you
<Trace level="1" type="T">select interface MI_Motorola*</Trace>
<Trace level="1" type="T">select interface namespace http://www.motorola.com</Trace>
<Trace level="1" type="T"><b>no interface found</b></Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface MI_SSPRINT*</Trace>
<Trace level="1" type="T">select interface namespace http://www.sprint.com</Trace>
<Trace level="1" type="T"><b>no interface found</b></Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>Hi Satish,
I just tested the scenario from ID. I have checked the log. Please find it below and let me know next step...
<b>sender agreement not found</b>
<Trace level="1" type="B">SENDER AGREEMENT SIMULATION</Trace> <Trace level="1" type="T">Simulating Adapter Engine...</Trace> <Trace level="1" type="T">Simply trying to loolup for the most specific Sender Agreement object</Trace> <Trace level="1" type="T"><b>no objects found</b></Trace> <Trace level="1" type="T">Note that real results may differ</Trace>
I did double check sender agreement object which looks good. -
IDOC to File : "no interface found"
Hi all,
I have an IDOC to file scenario and I'm getting the error "no interface found" at sxmb_moni. The scenario is only for test purposes, very simple, using the IDOC /ISDFPS/T01./ISDFPS/T0101. I have configured
-> receiver and interface determination
-> receiver agreement with the receiver channel for file output.
Receiver interface (sender) is /ISDFPS/T01./ISDFPS/T0101 and receiver agreement I configured the inbound interface to /ISDFPS/T01./ISDFPS/T0101 (same interface, no mapping needed).
I don't know why I'm getting "no interface found" error... Some tips?
thanks!
robertiYes, Bhavesh, I think the same. But all of it seems to be ok, lets see...
<i><b>Rec. Determination</b></i>
<b>Sender</b>
Service: ED0
Interface: /ISDFPS/T01./ISDFPS/T0101
Namespace: urn:sap-com:document:sap:idoc:messages
<b>Receiver</b>
Party:*
Service:*
Type: Standard
Configured Receivers: Service: SAE_NAS (no conditions or partys)
<i><b>Interface Determination</b></i>
<b>Sender</b>
Service: ED0
Interface: /ISDFPS/T01./ISDFPS/T0101
Namespace: urn:sap-com:document:sap:idoc:messages
<b>Receiver</b>
Service: SAE_NAS
Type: Standard
Configured Inbound Interfaces
Inbound Interface
Name: /ISDFPS/T01./ISDFPS/T0101
Namespace:urn:sap-com:document:sap:idoc:messages
No mapping (are the same messages, but I have already tried with mapping)
<i><b>Rec. Agreement</b></i>
<b>Sender</b>
Service: ED0
<b>Receiver</b>
Service: SAE_NAS
Interface: /ISDFPS/T01./ISDFPS/T0101
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver com. channel: CHN_RCV
I think the problem is in a little bit detail... but I couldn't find it. Some tip?
thanks!
roberti -
Inbound interface found more than once for outbound interface
Hello everybody,
i have a simple problem.
I build a interface with XI3.0
File to idoc
for each file i need crate 2 idoc.
It's not a problem when Idoc type is different, but in my case i need crate 2 idoc of same type but with a different mapping.
so when i upload the file i have this error:
Inbound interface found more than once for outbound interface
how can i solve this problem? can i force this step?
i thought to create a different idoc type or create the 2 idoc in same mapping , but there is not my favourite solution because in case of error , both idoc will be not created.
any suggestion?
thanks in advance
alexHi,
Instead of exporting and changing the occurrence as suggested by Ravi,
use the same Idoc twice in mapping as well as Interface mapping.
Coming to ID part, do every thing as usual.
The only thing to note is instead of using normal Interface determination, use extended Interface Determination.
This will solve your problem. The error will not come again. I'm sure.
Try out and update the thread.
Regards,
Jeevan. -
hi ,
i am just using EJb in my Application
just created an SessionBean and with Local interface in it i am getting this wierd exception with weblogic NetBeans and eclipse also
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
at weblogic.ejb.container.compliance.SessionBeanClassChecker.checkInterfacesExist(SessionBeanClassChecker.java:177)
at weblogic.ejb.container.compliance.Ejb30SessionBeanClassChecker.checkInterfacesExist(Ejb30SessionBeanClassChecker.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:331)
at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:428)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:437)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:795)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:683)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1254)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:321)
at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
Truncated. see log file for complete stacktrace
>Hi Rajendar,
I think the problem with having empty interfaces, or interfaces without methods for EJBs, is that they don't really make "sense". After deploying your EJB, a client application will use JNDI or dependency injection to access your EJB. So in your case it will look something like this
@EJB
mytestSSBLocal myejb; //(In this case we are using the local interface)
In the second step, you will want to do something will your EJB, but since mytestSSBLocal doesn't define any methods, there is nothing you can do with your ejb.
The Exception is telling you that weblogic couldn't find a complaint interface for your EJB.
best regards, Nicolas -
XML message error "No inbound interface found "
Hi,
I have inbound file adapter and mine is standalone XI box,
and idoc outbound adapter, when i start the file adapter im getting the folloing error message in SXMB_MONI .
Error when determining inbound interface. No inbound interface found for sender XI1 and outbound interface FILE2IDOC.FILEINBOUND
pls help me.
thankxThe message is telling you the exact problem - you do not have a receiver identification configured in the Integration Directory for this combination of inbound interface, namespace, and business system. Make sure your file adapter is configured to send with the correct outbound interface/interface namespace.
HTH,
Paul Medaille -
Traceroute: Warning: Multiple interfaces found
I have added a route by
route add 10.224.36.0 -netmask 255.255.255.224 10.224.18.1
I can even ping to that IP. However when i do a traceroute it gives-->
$ traceroute 10.224.36.1
traceroute: Warning: Multiple interfaces found; using 10.224.8.152 @ ce0
traceroute to 10.224.36.1 (10.224.36.1), 30 hops max, 40 byte packets
1 10.224.18.1 (10.224.18.1) 0.608 ms 0.542 ms 0.410 ms
2 10.224.36.1 (10.224.36.1) 40.482 ms 45.331 ms 40.516 ms
What's wrong?
AnmolI don't think the version of traceroute here uses the routing tables at all, but just picks an interface to transmit on. That's why it whines about finding multiple interfaces. I'm not sure if other versions address this.
Try providing the interface directly.
Darren -
IDOC - BPM - IDOC Error --no sender or receiver interface definition found
I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
SergioRajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio -
Word import Module.vi is trying to call Vb project and VB components thru active X controls when it's trying to call Vb components it's giving the error no such interface found..I am using Labview 6,MSoffice97,Graph8
Hi Adam,
It seems that there have been a couple other instances of the same error occurring and the problem is a conflict that occurs with the Office 97 only. Somehow the MS Office type library has been modified and this is causing incompatibilities with MS Office 97. Have you installed any other application on top of MS Office that plugs into MS Office tools – Adobe Acrobat, Visio, Reflection?? If so, you will want to see about uninstalling or reinstalling those utilities and then reinstalling Office 97 to restore the original MS Office 97 type library.
Also, if you have a newer version of MS Office, I would highly recommend upgrading your computer. It seems that this problem is only with Office 97 and later versions of Office do not have this issue.
Thanks again for bringing this question up.
Kileen -
Complex interface determination fails for 0-N mappings
We have a mapping question for the following scenario in PI 7.1: One message needs to be mapped into two target structures, it comes from the same sender and goes to same receiver. We need to call two different BAPI in the same SAP end system simultaneously.
This is set up in one interface determination (same sender & receiver) where we use two different operation mappings with different receiver interface names. If the mapping have multiplicity 1, everything works fine and the message gets mapped to both receiver interfaces simultaneously. But, when the multiplicity of the mappings is 0-N (split mapping), then we get error message during interface determination phase:
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface http://sending/namespace.sndInterfaceName
How can we set up our scenario with two 0-N mappings without getting error message? One option would be combining two mappings in one, but this can not work in our case because of the high complexity.
Any comments appreciated. Thanks, Sanjay.
Edited by: Sanjay Gupta on Oct 21, 2010 10:50 PMThanks for taking the time to look into this. See my comments below.
1. Are you using multi mapping? Source Message type 1 and Traget message types 2 (added from messages tab in the mapping)
We have two mappings, both create only a single output type, however, they are split mappings, meaning the mapping result message multiplicity is 0-N. So the answer is NO, this are no multi mappings
2. At any time, can both the target messages be created or are they mutually exclusive?
both targets will always be created, they are NOT mutually exclusive
3. With in each message type that gets generated on the target side, is the occurance 1..1 or 1..unbounded?
Don't fully get the question, but I assume you ask if the mapping is defined as a 1:1 or 1..N mapping. The latter is true.
4. Is there any condition in the interface determination?
Answer is No.
5. How many operation mappings did you design.
We have two operation mappings, each containing a different mapping to the different receiver interface type.
Being said that, the ideal way should be, You need to create only one message mapping by adding multiple message types on the target side. I fully understand and agree with this statement, but due to the complexity of the mapping we need to separate it out into two mappings.
It is confusing, that the described scenario works if the multiplicity of the mapping objects used is 1, but as soon as the multiplicity is 0-N (when using a split mapping instead), we start getting the error message. -
Interface Determination causing issue in Receiver Determination
Hi
I am having an issue with interface and receiver determination as follows:
- Inbound message may be sent to two receivers.
- Message gets sent to first receiver, fails during interface determination. There are multiple inbound interfaces found based on a set of XPATH conditions. This creates an error 'Inbound interface found more than once for outbound interface '. That is itself is <b>not </b>the issue.
- Issue is that the message is stopped from going to the other receiver even if there are no issues in the interface determination for that receiver.
Is there a way to resolve this? Appreciate any help. Thx, DuncanAgain, thanks for the replies.
<b>MONI for RD</b>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE COSTCENTRE or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice")% EX or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:inventoryActivityOrInventoryStatus")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:despatchAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid Receiver with Condition: - GLR430</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE COSTCENTRE and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT_ONESTEP and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT_ONESTEP</Trace>
<Trace level="2" type="T">...invalid Receiver: P_3PL_XML_ME_ODTH - despatchAdviceToE1EDT20</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 3</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: P_3PL_XML_ME_ODTH - S_HTTP</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:2</Trace>
</Trace>
</Trace>
</Trace>
Here, you see that both receivers are found.
<b>MONI for ID</b>
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2007-02-26T20:06:49Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_STATUS</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_ACTIVITY</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification</Trace>
<Trace level="2" type="T">......extracting values found: 2</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue")% CE SHUTTLE</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Here, you see that the ID runs for the first receiver. It hits an error because two conditions on the ID for the first receiver are satisfied. However, it then stops rather than allow the processing for the other receiver to continue.
Any ideas? Thx, Duncan -
Error when determining the inbound interface
Hi Experts,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Scenario Steps
1) No Condition in Interface Determination
2) 0..unbounded in Message Mapping and Operational Mapping.
3) E1KNA1 is mapped to E1KNA1
4) E1ADRMAS is mapped to E1ADRMAS
5) One Message Mapping and 1 Operational Mapping.
Thanks in Advance.
Sriram.Hello,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
Since your scenario makes sure that the 2 files are created, there is no need to use multi-mapping. Rather, you can use an interface determination split. To do this:
1. declare xml_file1 as service interface 1, xml_file2 as service interface 2
2. do not change target occurrence in message mapping and operation mapping, maintain it as 1..1
( 2 operation mappings)
3. in ID, add the two service interfaces in your interface determination
At runtime, it will split into two inbound interfaces.
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Were you able to declare the 2 xml_files as two separate service interface(different names) in your operation mapping?
Hope this helps,
Mark -
Error like -- No outbound binding found for
i created a order in one system and want to send to another system
i got errors like given below....can u check and helpme me... how to solve the issue
plz check both errors...
SAP: Stack> Error when determining the inbound interface: For Outbound
Interface http://cgi.com/xi/Global.PurchaseOrderRequest
An inbound interface repeatedly found (at the same transmitter and
Receiver). On the outbound interface http://cgi.com/xi/Global.
Purchase Order Request, a multiple inbound interface found (in
The same transmitter and receiver). </ SAP: Stack>
<SAP: Additional text> No outbound binding found for PC100, cgi_PurOrdrProcessing, PC200, SAPESD_SalOrdrProcessing, http://cgi.com/xi/Global, Purchase Order Request </ SAP: Additional Text>
<SAP: Stack> There is a problem with the recipient agreement for the station PC100-cgi_PurOrdrProcessing to receiver PC200-cgi_SalOrdrProcessing, http://cgi.com/xi/Global.PurchaseOrderRequest occurred: No. outbound binding found for PC100, cgi_PurOrdrProcessing, PC200, cgi_SalOrdrProcessing, http://cgi.com/xi/Global, Purchase Order Request </ SAP: Stack>
<SAP: Retry> M </ SAP: Retry>
i am already checked the config.part and cache als ...still the error exist
kindly help on this issue//
best regards,saranHi
refer this for related discussion
Error when trying multiple inbound interface determination for IDOC
Check your receiver identification configured in the Integration Directory for this combination of inbound interface, namespace, and business system. Also Make sure your file adapter is configured to send with the correct outbound interface/interface namespace.
Regrds
Anusha Ramsiva -
Dear Team,
Oracle 12c GRID Runclufy check failing with below error. Even After Changing Local Built in Administrator User Name also same failure reporting. Kindly help to resolve this Issue and Provide steps to Avoid this conflict.
Windows user account consistency check across nodes - Checks consistency of Windows user account across nodes Error:
PRVG-11818 : Windows user "MDCCOMMONLDAP\Administrator" is a domain user but a conflicting local user account was found on nodes "sep03vvm-401,sep03vvm-402" -
Cause: A conflicting local user account as indicated was found on the identified nodes. - Action: Ensure that the Windows user account used for Oracle installation and configuration is defined as a domain user on all nodes or as a local user on all nodes, but not a mixture of the two.
Check Failed on Nodes: [sep03vvm-402, sep03vvm-401]
c:\Oracle12c_software\Oracle12c_grid\grid>runcluvfy.bat stage -pre crsinst -verbose -n SEP03VVM-401,SEP03VVM-402
Performing pre-checks for cluster services setup
Checking node reachability...
Check: Node reachability from node "sep03vvm-401"
Destination Node Reachable?
sep03vvm-401 yes
sep03vvm-402 yes
Result: Node reachability check passed from node "sep03vvm-401"
Checking user equivalence...
Check: User equivalence for user "Administrator"
Node Name Status
sep03vvm-402 passed
sep03vvm-401 passed
Result: User equivalence check passed for user "Administrator"
Checking node connectivity...
Interface information for node "sep03vvm-402"
Name IP Address Subnet Gateway Def. Gateway HW Addre
ss MTU
PublicLAN 153.71.45.202 153.71.45.0 On-link 153.71.45.254 00:50
:56:91:05:30 1500
PrivateLAN 10.10.10.15 10.10.10.0 On-link 153.71.45.254 00:5
0:56:91:75:1B 1500
6TO4 Adapter 2002:9947:2dca::9947:2dca 2002::
00:00:00:00:00:00 1280
Interface information for node "sep03vvm-401"
Name IP Address Subnet Gateway Def. Gateway HW Addre
ss MTU
PublicLAN 153.71.45.201 153.71.45.0 On-link 153.71.45.254 00:50
:56:91:56:B6 1500
PrivateLAN 10.10.10.14 10.10.10.0 On-link 153.71.45.254 00:5
0:56:91:60:99 1500
6TO4 Adapter 2002:9947:2dc9::9947:2dc9 2002::
00:00:00:00:00:00 1280
Check: Node connectivity of subnet "153.71.45.0"
Source Destination Connected?
sep03vvm-402[153.71.45.202] sep03vvm-401[153.71.45.201] yes
Result: Node connectivity passed for subnet "153.71.45.0" with node(s) sep03vvm-
402,sep03vvm-401
Check: TCP connectivity of subnet "153.71.45.0"
Source Destination Connected?
sep03vvm-402 : 153.71.45.202 sep03vvm-402 : 153.71.45.202 passed
sep03vvm-401 : 153.71.45.201 sep03vvm-402 : 153.71.45.202 passed
sep03vvm-402 : 153.71.45.202 sep03vvm-401 : 153.71.45.201 passed
sep03vvm-401 : 153.71.45.201 sep03vvm-401 : 153.71.45.201 passed
Result: TCP connectivity check passed for subnet "153.71.45.0"
Check: Node connectivity of subnet "10.10.10.0"
Source Destination Connected?
sep03vvm-402[10.10.10.15] sep03vvm-401[10.10.10.14] yes
Result: Node connectivity passed for subnet "10.10.10.0" with node(s) sep03vvm-4
02,sep03vvm-401
Check: TCP connectivity of subnet "10.10.10.0"
Source Destination Connected?
sep03vvm-402 : 10.10.10.15 sep03vvm-402 : 10.10.10.15 passed
sep03vvm-401 : 10.10.10.14 sep03vvm-402 : 10.10.10.15 passed
sep03vvm-402 : 10.10.10.15 sep03vvm-401 : 10.10.10.14 passed
sep03vvm-401 : 10.10.10.14 sep03vvm-401 : 10.10.10.14 passed
Result: TCP connectivity check passed for subnet "10.10.10.0"
Check: Node connectivity of subnet "2002::"
Source Destination Connected?
sep03vvm-402[2002:9947:2dca::9947:2dca] sep03vvm-401[2002:9947:2dc9::9947:2dc
9] yes
Result: Node connectivity passed for subnet "2002::" with node(s) sep03vvm-402,s
ep03vvm-401
Check: TCP connectivity of subnet "2002::"
Source Destination Connected?
sep03vvm-402 : 2002:9947:2dca::9947:2dca sep03vvm-402 : 2002:9947:2dca::9947:
2dca passed
sep03vvm-401 : 2002:9947:2dc9::9947:2dc9 sep03vvm-402 : 2002:9947:2dca::9947:
2dca passed
sep03vvm-402 : 2002:9947:2dca::9947:2dca sep03vvm-401 : 2002:9947:2dc9::9947:
2dc9 passed
sep03vvm-401 : 2002:9947:2dc9::9947:2dc9 sep03vvm-401 : 2002:9947:2dc9::9947:
2dc9 passed
Result: TCP connectivity check passed for subnet "2002::"
Interfaces found on subnet "153.71.45.0" that are likely candidates for VIP are:
sep03vvm-402 PublicLAN:153.71.45.202
sep03vvm-401 PublicLAN:153.71.45.201
Interfaces found on subnet "2002::" that are likely candidates for VIP are:
sep03vvm-402 6TO4 Adapter:2002:9947:2dca::9947:2dca
sep03vvm-401 6TO4 Adapter:2002:9947:2dc9::9947:2dc9
Interfaces found on subnet "10.10.10.0" that are likely candidates for a private
interconnect are:
sep03vvm-402 PrivateLAN:10.10.10.15
sep03vvm-401 PrivateLAN:10.10.10.14
Checking subnet mask consistency...
Subnet mask consistency check passed for subnet "153.71.45.0".
Subnet mask consistency check passed for subnet "10.10.10.0".
Subnet mask consistency check passed for subnet "2002::".
Subnet mask consistency check passed.
Result: Node connectivity check passed
Checking multicast communication...
Checking subnet "153.71.45.0" for multicast communication with multicast group "
224.0.0.251"...
Check of subnet "153.71.45.0" for multicast communication with multicast group "
224.0.0.251" passed.
Check of multicast communication passed.
Checking the status of Windows firewall
Node Name Enabled? Comment
sep03vvm-402 no passed
sep03vvm-401 no passed
Result: Windows firewall verification check passed
Check: Total memory
Node Name Available Required Status
sep03vvm-402 4.9996GB (5242420.0KB) 4GB (4194304.0KB) passed
sep03vvm-401 4.9996GB (5242420.0KB) 4GB (4194304.0KB) passed
Result: Total memory check passed
Check: Available memory
Node Name Available Required Status
sep03vvm-402 3.6612GB (3839028.0KB) 50MB (51200.0KB) passed
sep03vvm-401 3.3152GB (3476244.0KB) 50MB (51200.0KB) passed
Result: Available memory check passed
Check: Swap space
Node Name Available Required Status
sep03vvm-402 5.8121GB (6094388.0KB) 4.9996GB (5242420.0KB) passed
sep03vvm-401 5.8121GB (6094388.0KB) 4.9996GB (5242420.0KB) passed
Result: Swap space check passed
Check: Free disk space for "sep03vvm-402:C:\Windows\temp"
Path Node Name Mount point Available Required Stat
us
C:\Windows\temp sep03vvm-402 C 82.6484GB 1GB pass
ed
Result: Free disk space check passed for "sep03vvm-402:C:\Windows\temp"
Check: Free disk space for "sep03vvm-401:C:\Windows\temp"
Path Node Name Mount point Available Required Stat
us
C:\Windows\temp sep03vvm-401 C 82.6112GB 1GB pass
ed
Result: Free disk space check passed for "sep03vvm-401:C:\Windows\temp"
Check: System architecture
Node Name Available Required Status
sep03vvm-402 64-bit 64-bit passed
sep03vvm-401 64-bit 64-bit passed
Result: System architecture check passed
Checking length of value of environment variable "PATH"
Check: Length of value of environment variable "PATH"
Node Name Set? Maximum Length Actual Length Comment
sep03vvm-402 yes 5119 100 passed
sep03vvm-401 yes 5119 129 passed
Result: Check for length of value of environment variable "PATH" passed.
Checking availability of ports "6200,6100" required for component "Oracle Notifi
cation Service (ONS)"
Node Name Port Number Protocol Available Status
sep03vvm-402 6200 TCP yes successful
sep03vvm-401 6200 TCP yes successful
sep03vvm-402 6100 TCP yes successful
sep03vvm-401 6100 TCP yes successful
Result: Port availability check passed for ports "6200,6100"
Starting Clock synchronization checks using Network Time Protocol(NTP)...
Checking daemon liveness...
Check: Liveness for "W32Time"
Node Name Running?
sep03vvm-402 yes
sep03vvm-401 yes
Result: Liveness check passed for "W32Time"
Check for NTP daemon or service alive passed on all nodes
Result: Clock synchronization check using Network Time Protocol(NTP) passed
Checking if current user is a domain user...
Check: If user "Administrator" is a domain user
Result: User "MDCCOMMONLDAP\Administrator" is a part of the domain "MDCCOMMONLDA
P"
Check: Time zone consistency
Result: Time zone consistency check passed
Checking for status of Automount feature
Node Name Enabled? Comment
sep03vvm-402 yes passed
sep03vvm-401 yes passed
Result: Check for status of Automount feature passed
Checking consistency of current Windows user account across all nodes
PRVG-11818 : Windows user "MDCCOMMONLDAP\Administrator" is a domain user but a c
conflicting local user account was found on nodes "sep03vvm-402"
Result: Check for Windows user account "MDCCOMMONLDAP\Administrator" consistency
failed
Pre-check for cluster services setup was unsuccessful.
Checks did not pass for the following node(s):
sep03vvm-402SEVERE: [FATAL] [INS-30131] Initial setup required for the execution of installer validations failed.
CAUSE: Failed to access the temporary location.
ACTION: Ensure that the current user has required permissions to access the temporary location.
Are you using a supported OS version (listed in the Install Doc) and following all of the steps in the Install Doc ?
HTH
Srini -
Receiver interfaces problem...
Hi all...
I have 2 questions...
1. Can we use multimaping in which both proxy and other adapter(say File or Mail) are in receiver side without any BPM?
If yes lemme know how please...
I could not do the above so i am going for 2 different mappings.....
2. Can i use the same receiver interface in more than 1 flow for the same sender and receiver components but the sender interfaces are in different namespaces?
I am trying to do above but i am getting the following error...
- <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="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface found several times (for same sender and receiver) for the outbound interface urn:np.atl.warrants.stage2meterplus.WarrantsS2Meterplus_OB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:interface_OB Inbound interface found several times (for same sender and receiver) for the outbound interface urn:interface_OB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any1 please throw some light on this issue..
Thanks in advance..> 1. Can we use multimaping in which both proxy and other adapter(say File or Mail) are in receiver side without any BPM?
Yes, you can do it without BPM if it is 1:N mapping but if it is N:1 then you have to use BPM.
I could't realize while answering. It is not possible, see the reason given below by Sanjeeve.
> 2. Can i use the same receiver interface in more than 1 flow for the same sender and receiver components but the sender interfaces are in different namespaces?
No, you cannot do like this. You can see it is clear from the error message it self that "Inbound interface found several times (for same sender and receiver)".
Regards,
Sarvesh
Edited by: Sarvesh Singh on Dec 14, 2009 8:54 PM
Maybe you are looking for
-
HP LaserJet 500 support on HOST-RESOURCES-MIB
Hi, We've various HP printer install in our campus. I've tried to enable snmp in one of the HP printer ( e.g. HP LaserJet 500 color M551). Our goal for the HP printer is to have them response the SNMP "hrDeviceDescr" under the HOST-RESOURCES-MIB
-
Click wheel and buttons don't work on 5th gen.
I have had my iPod for about half a year and for some reason my iPod buttons don't work. If I move the hold button it turns on but none of the other buttons work. It charges and everything. Does anyone know what to do? 5th generation Windows XP
-
Can i recover photos moved from iphoto via finder?
first things first: i made a stupid mistake. i wanted to share a lot of photos w/ friend via my google drive. i store my photos in iphoto. what i did was that i located the files in finder, selected them and moved the whole lot to my googledrive. wha
-
As you can see from the title, I have pulled the hard drive from a computer that wont boot. I can see the itunes data using a drive reader. How do I migrate it to a new laptop?
-
Any reason I Shouldn't...
Use a wall power charger that came with a 4th gen. iPod to charge my Touch? This charger has a firewire port, but I have the correct cable for it. TIA, Scott