"Unable to find channel ID" error.

Hello experts,
We are building an IDOC->XI->JMS scenario.
Sending the IDOC gets it into the XI and it is visible inside the SXMB_MONI. Looking at a trace level 3 on the trace section of the message you can see that all pipeline activities are performed as normal.
The last action of the Outbound Binding is successful and the correct Communication channel name (from the Receiver Agreement) is displayed in the trace - meaning was selected.
Looking in the RWB on the details of the message show that:
- message was received from http://xiserver:50000/MessagingSystem/receive/AFW/XI
- The message goes in and out of the receive queue.
- the message status set to DLNG
- Unable to find channel ID.
- ... error stuff..
This Channel ID error is the one who causes us trouble.
Looking at the same place for a PROXY->XI->JMS scenario shows that the correct channel is selected. this channel is the channel in the receiver determination - the name only exists there so it doesn't relate to any other channel (like MQ channel).
Could really use help finding this problem source or activating J2EE traces the could point to what's wrong.
Thank's - Yoad.

Hi,
One thing which could be wrong is the cache. Try in the IB:Directory to see if all things have been succesfully committed to the CPA.
Then try to refresh the CPA cache. http://xiserver:50000/CPACache/refresh?mode=full (Login as XIDIRUSER)
If you are on SP 12, you could use NW administrator on http://xiserver:50000/nwa -> select Monitoring -> Logs and traces and in the blank dropdownbox select Default trace.
Hope this helps

Similar Messages

Error: Unable to find channel ID

Hello,
I have an scenario R/3 - XI - Mail in GEN, the same scenario was working perfectly in GED but after transporting it to GEN it does not work.
In the adapter monitoring I can see the following error: 'Unable to find channel ID'. Does anybody know the reason of this error?
Thanks in advanced,
Luis.

hi,
- check if all directory objects are tranported to new landscape!
- activate communication channel once more
- refresh CPA cache
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Unable to find channel ID at inbound SOAP Adapter

Hi experts,
I encountered a very puzzling problem:
I have a scenario:
IDOC -> XI -> SOAP
For 2 interfaces of such nature, 1 works fine, 1 doesn't.
The one that does not work is throwing the following error in RWB - Message Display Tool (MDT):
2007-03-22 10:57:05 Success The message was successfully received by the messaging system. Profile: XI URL: http://ootspdbs02:50100/MessagingSystem/receive/AFW/XI
2007-03-22 10:57:05 Success Using connection AFW. Trying to put the message into the receive queue.
2007-03-22 10:57:06 Success Message successfully put into the queue.
2007-03-22 10:57:06 Success The message was successfully retrieved from the receive queue.
2007-03-22 10:57:06 Success The message status set to DLNG.
<b>2007-03-22 10:57:06 Error Unable to find channel ID
2007-03-22 10:57:06 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: a277e57c-c837-e44f-9ae2-da0d701980c4. </b>
2007-03-22 10:57:06 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 22 10:58:06 SGT 2007.
2007-03-22 10:57:06 Success The message status set to WAIT.
In SXMB_MONI, it shows the message has been processed successfully - indicating that the mapping is fine. Status = Awaiting acknowledgement.
I've looked up the forums, and the general solution offered is to refresh the SLD cache.
I've tried that, but it doesn't work.
Please help.
Thanks.
Ron

> hmm.. then things not a problem with the cache.
> Is the error in MONI? Or is it in the Adapter Engine?
>
>
> I know it isrepeatitive, but checking if the Objects
> are all active and correct in the ID is the only
> solution I can suggest.
>
> Regards
> Bhavesh
In the MONI, the status is successful, awaiting acknowledgement.
After sometime, the ack status will be "Acknowledgement contains System Errors"
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>,BS_DEV1_NAUTICUS_OOTS</SAP:P1>
<SAP:P2>,BS_NHGDDBS01,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
But I don't think these are related, because the message wasn't sent out, naturally there's an error in the ack.

XI - Unable to find channel ID

Hello,
I am trying to post a message via HTPP and I get the error message
Message Data - Error category: XI_J2EE_ADAPTER_ENGINE
Message Data - Error code: CHANNEL_DETERMINATION_FAILED
Audit Log - Error: Unable to find channel ID
Audit Log - Error: Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message:
Could you help me on this topic, please?
Thanks in advance for your answer,
Vincent,

Hi Vincent,
Here are a couple of suggestions which normally works.
I guess you should check your receiver agreement, i.e your receiver channel.
RWB --> Component monitoring --> Adapter monitoring --> your receiver channel (it should be green).
If it is not, then thats where the problem lies.
Also there is a nice link for Problem Analysis Guide, which tells you the approach to take to analyse a problem,
http://help.sap.com/saphelp_nw04/helpdata/en/6c/7ffb3f6c78ee28e10000000a1550b0/frameset.htm
Also check your Pipeline URL in SLD.
Business System ->Click On -> Pipe Line URL
It should be
http://Server:port/sap/xi/engine?type=entry
Second, Go to SICF Transaction in XI, and activate the service sap/xi/engine
For more
Transmitting message to entry pipeline failed !!
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
Also Double check your port(for the second URL). It should be the HTTP port listed when you go to txn SMICM then Goto->Services. The port you have there looks like the J2EE port.
If nothing works, Just try to restart AFW and AFxxx services (from Visual Admin)
Steps to restart AFW and AFxxx services are:
Start the Visual Admin tool. Connect to your XI J2EE Engine (640).
Go to Server->Services.
Try to restart such services as "SAP XI AF Messaging", "SAP XI AF Core", "SAP XI Adapter: XI", etc.
Regards,
Abhy
Message was edited by: Abhy Thomas

Unable to find channel ID - using Test Message in RWB

Hey all - we are using the Test Message tab of the RWB, and we get "Unable to find channel ID" as the response to our message being sent. We are clueless what this means... since this is supposed to send straight into the engine, I'd expect something like "no interface determination" or sometimes similar - but we can't figure out what this error means. This is the message we get, regardless of payload or interface chosen... We even chose an interface that has already been tested & is running successfully into XI via the JMS adapter, so we know the actual path thru XI is valid.
Help is appreciated - I'm sure this is something silly we don't have set up that we need...

We were hitting the Test tab after clicking the AF in RWB - you should choose the engine... it likes that much better.

Unable to find channel ID

Hello,
I am running into some problems testing out a scenario using the test tool in the rwb that is supposed to do a simple map and write to a table using the JDBC adapter.
The error I get in the message monitor are:
Message Data - Error catagory: XI_J2EE_ADAPTER_ENGINE
Message Data - Error code: CHANNEL_DETERMINATION_FAILED
Audit Log - Error: Unable to find channel ID
Audit Log - Error: Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message:
Using the test configuration tool in the Configuration Bulider test is successful, it finds Rec Det, Interface Det, Interface Mapping and Rec Agreement etc.
If anyone can give me any pointers would be very appreciated!
Thanks
Nam

Hello!
Wow, that was quick!
I originally tried clicking directly on the adapter engine (central) and sending from there. That sends the message to http://ac4sap02:58100/MessagingSystem/receive/AFW/XI.
That generates the errors I listed below.
I tried following your weblog and clicking on the Integration Server and testing from there. Message is sent to:
http://ac4sap02:58100/sap/xi/engine?type=entry
This generates an error: Error when sending message: 404 Not Found.
When testing the engine service in SICF I get the errors below:
Pipeline specified in URL attribute (type) not existing
URL_PIPELINE_NOT_FOUND
Pipeline ID , which is expected as value of attribute "type" in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=510
Thanks!
Nam

Transactions "unable to find channel"

Hello,
I have made two test channels on my server - but doing a "rug channels" on
my clients gives a "No channels available" message (and performing a
transaction fails, giving an "unable to find channel" message).
I followed instructions in the ZLM Admin docs while setting up, the clients
both work fine with red-carpet.ximian.com, I was able to add the service
for my local ZLM server fine, and they both activated fine with a test
activation key I made, but for some reason they can't see any channels on
this server.
I'm at a bit of a loss troubleshooting the problem - can't figure out what
I might have missed! Any suggestions? (I'm using ZW6.5 on SLES8-SP3, with 2
clients: SLES9 and SuSE-Pro-9.1).
Many thanks for any help,
Karl

Kpodesta,
It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at http://support.novell.com in both the "free product support" and "paid product support" drop down boxes.
- You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums)
If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Unable to find file "ConfigureClusterNode" error

Hi All
I am trying to install UCM Cluster. According to Universal Content Management Cluster Configuration Guide for UNIX 10g Release 3 (10.1.3.3.1)
I can do this running Installer with some parameters, but I have Unable to find file "ConfigureClusterNode" error.
(http://download-west.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/documentation/integrator/install_cserver_unix_10en.pdf)
[wc@hostname linux]$ ./Installer -set-ClusterNodeIntradocDir=/home/wc/cluster/node1 -set-ClusterNodeName=node1 -set-ClusterNodeAddress=10.33.33.33 -set-ClusterBinDirRule=local ConfigureClusterNode ConfigureAdminClusterNode
Unable to find file "ConfigureClusterNode".
The file wait.dat wasn't removed.
I need help to identify and solve the problem.

Hi, and a warm welcome to the forums!
Forgive me, I'm about to go for a psychic cure here and pull a rabbit out of the hat, or is it a needle from a haystack!?
I'm thinking that if this remote volume was like SMB/MS-DOS/Fat32, that the "caseness" may be the problem... here's why... Uppercase may translate to be shown either Capitalized or lowercase on the other end, and although Fat32 is supposed to be/ and in fact IS Case Sensitive, many things along the way may almost rightfully expect Uppercase 8/3 format, and "Testing.df1" may show as "Testing.df1", but also "TESTING.DF1", and "testing.df1" might show as "Testing.df1", but behind the scenes it's back to reality.
Might be the most nothingness I've ever pulled out of thin air!?

"unable to find root device" error with linux-lts

Hi all,
I'm having a problem with booting linux-lts after a recent upgrade (3.14.39-1 -> 3.14.43-2). In particular, I get an "unable to find root device" error.
I have look at other threads for potential solutions; I have tried a) re-installing linux-lts, b) adding 'block' before 'autodetect' in mkinitcpio.conf before the re-installation, and c) changing /dev/sdb4 (my root partition) in syslinux.cfg to UUID and PARTUUID. I still get the same error.
In the emergency shell, running 'blkid' does not show the root partition in the output.
If I boot from the latest kernel (4.0.4-2), it all boots fine.
Does anybody have any ideas on anything I could try to get linux-lts to boot? I'd prefer to stay with the lts kernel if possible.

KangarooLemonade wrote:I ran through the beginner's guide to installing Arch on the wiki and installed Arch onto an external USB hard drive.
Yeah? And did you see this: https://wiki.archlinux.org/index.php/Be … nvironment ?
Here you need to set the right hooks if the root is on a USB drive, if you use RAID, LVM, or if /usr is on a separate partition.
No, of course you missed it...
Boot your install using the Fallback entry. If you do not have a Fallback entry, press Tab (for Syslinux) or "e" (for GRUB) and rename it initramfs-linux-fallback.img. After it boots, open up a terminal and run:
# nano /etc/mkinitcpio.conf
<add "usb" to the HOOKS line>
# mkinitcpio -p linux
# reboot
And don't forget to mark it as solved.
Last edited by DSpider (2012-10-01 20:11:04)

Unable to find channel ID in multi-mapping scenario

Hi all,
my scenario RFC-adapter-XI-File-adapter works fine, if I use a mapping without splitting the source message.
The supposed file is generated.
But If I split the source messsage in message mapping I see successfully splitted payloads in monitoring, but the files are not generated because of Error "channel ID can not be found".
AND "Zustellung der Message an die Anwendung über AFW ist fehlgeschlagen weil: Couldn't find delivery channel for message: 307e06d0-41c5-11db-96be-0017a41036a2. Message wird auf 'fehlgeschlagen' gesetzt"
I checked alread the whole forum and found some interesting informations, but nothing helped me..
Has anybody an idea?
Thanks a lot!

Hi Florian,
It looks like the system is unable to find a Receiver agreement / Communication Channel for one of the Messages created by the Map.
Check whether the Receiver Agreements exist for both Message Interfaces created by message split.
Hope this helps.
Rgds
R Chandrashekhar

'Unable to find operation: null' Error When I invoke Composite Wsdl Url

Hi ,
I have created one composite application which consists one BPEL process.That BPEL process takes input from other application.
But When I invoke that Wsdl Url to push the data from my application to that Wsdl Url,It is giving below error(System fault):
'Unable to find operation: null' .
I am getting below message in enterprise manager console (http://ipaddress:port/em):
'Composite instances are not generated for rejected messages. Click the error message for details'.
Note: When u click on 'unable to find operation: null' link it is showing the soap request that we submitted to composite URL.
Instance ID is also not created.
Can anybody help me regarding this issue?

As you are able to test the Composite in the EM console and the correct operation, everything looks fine from SOA side.
Now whatever application from which you are trying to push the data, make sure while configuring the WSDL of the Composite, please check whether you can select the operation of the SOA Composite over there. I think you are leaving the default option which is null or not selecting the required operation over there.
Hope this helps
N

Custom tag - unable to find setter method error

I see this compileException on IAS but not on BEA app server and iWS.
JSPProvider.processJSPFile(): jsp=searchContent.jsp, org.apache.jasper.compiler.CompileException
Unable to find setter method for attribute: input
The reason is because the custom tag has a setInput() that takes a String parameter while the getInput() returns an InputStream.
Should both get and set methods have the same type of parameters or is this a due to a bug in the app server ?

I see this compileException on IAS but not on BEA app
server and iWS.
JSPProvider.processJSPFile(): jsp=searchContent.jsp,
org.apache.jasper.compiler.CompileException
Unable to find setter method for attribute: input
The reason is because the custom tag has a setInput()
that takes a String parameter while the getInput()
returns an InputStream.
Should both get and set methods have the same type of
parameters or is this a due to a bug in the app server
I was only going off info from the original post. The error specifically states "Unable to find setter method for attribute: input" with a lower case i for the input attribute. You also specifcally stated "The reason is because the custom tag has a setInput()" with a capital I for the setInput method. This would most definitely cause the error you were receiving. That is unless you corrected this between your original post and your followup testing.
Cliff

When Audio Console launched, Unable to find audio device error message comes

When I launch audio console, I get an error message saying:
"Unable to find audio device. Please make sure that your audio device is enabled and installed with its driver. This application will be closed."
This can't be right because my soundblaster audigy 2 ZS platinum card is installed, its working, I can hear things etc.
I uninstalled and reinstalled the audio console software package from creative and that fixed the problem for a very short while and it is now reoccurring.
I've had this same setup for several years with no issues, now all of a sudden, this is happening.
Anyone out there had similar challenges?
Thanks for looking!Message Edited by dgmtoronto on 07-22-200703:33 PM

Most probably you don't have passed the correct root= option to the kernel so that the kernel cannot, as it says, find its root device. Read the wiki page about refind in order to know how to configure it (https://wiki.archlinux.org/index.php/REFInd). Refind as no fully automatic configuration like grub.

Unable to find Program Unit error (ORA-06508)

This problem is quite complex and difficult to explain completely. We have a situation where a program unit (called ztmessage) is duplicated ... it is in all forms modules (.fmb) and also in our message library which is attached to all forms and libraries. It is required in the form due to use of the forms generator and in the library so that all other external libraries can compile.
Under certain situations forms appears to get totally confused and can't find the ztmessage program unit (raises ORA-06508 ... Can't find Program Unit being called ... should be calling the "form" program unit). Are there any known issues with duplicated program units?? All of this setup works fine under the 4.5 environnment but falls over in 6.0.
null

I suspect that this is a manifestation of Bug 612052 and it's relations.
What you were doing in 4.5 e.g. calling back from a PLL into a piece of code in
the form was strictly a No-No. However, it worked and lots of people used it.
Anyway the Name resolution works differently in 6.0 and the callbacks would all go
to the initial PU that was first bound rather than the "expected" one in the
current form.
In your case you are probably binding to the ztmessage PU in a form which is subsequently
being closed and hence the reference is broken - 6508 would result.
Anyway, that bug now has a "Fix" e.g. there is a way of restoring the 4.5 behaviour
Simply set the environment variable FORMS60_PLSQLV1_NAME_RESOLUTION to TRUE (or YES)
in the registry. You'll need patch 5 or 6i for this.
The side effects will be:
1) Performance will degrade as we have to resolve the name every time
2) You won't be able to use the SHARE_LIBRARY_DATA flag on OPEN_FORM/CALL_FORM

Export Release Build error - Exception in thread "main" java.lang.Error: Unable to find named traits

I've been developing an AIR application for Android and iOS. During development, I've run the application (in debug mode) in the desktop simulator as well as on an iPhone 4 and a Nook Tablet.
However, I recently tried to "Export Release Build" for iOS and hit the following error: (I've stripped out the package and class information in the error message below)
!ENTRY com.adobe.flexbuilder.project 4 43 2012-04-06 13:09:15.516
!MESSAGE Error occurred while packaging the application:
Exception in thread "main" java.lang.Error: Unable to find named traits: valid.package.path.here::ValidClassName
          at adobe.abc.Domain.resolveTypeName(Domain.java:231)
          at adobe.abc.Domain.resolveTypeName(Domain.java:148)
          at adobe.abc.GlobalOptimizer.sccp_eval(GlobalOptimizer.java:6665)
          at adobe.abc.GlobalOptimizer.sccp_analyze(GlobalOptimizer.java:5909)
          at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4628)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3514)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2215)
          at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:526)
          at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:336)
          at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:472)
          at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:82)
Compilation failed while executing : ADT
!STACK 0
java.lang.Exception
          at com.adobe.flexbuilder.project.internal.FlexProjectCore.createErrorStatus(FlexProjectCore. java:1019)
          at com.adobe.flexbuilder.util.logging.GlobalLogImpl.log(GlobalLogImpl.java:66)
          at com.adobe.flexbuilder.util.logging.GlobalLog.log(GlobalLog.java:52)
          at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.doPackage (ExportReleaseVersionWizard.java:283)
          at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.performFi nish(ExportReleaseVersionWizard.java:152)
          at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
          at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
          at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
          at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
          at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
          at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
          at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
          at org.eclipse.jface.window.Window.open(Window.java:801)
          at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction$1.run(Export ReleaseVersionAction.java:97)
          at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction.run(ExportRe leaseVersionAction.java:103)
          at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
          at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
          at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:584)
          at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
          at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :411)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
          at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
          at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
          at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
          at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
          at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
          at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
          at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
          at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
          at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
          at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.ja va:108)
          at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
          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 org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
          at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
          at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
The class the error message is referring to is defined with a SWC that my project links to. However, I've even tried to define a class with that same name (and location) within my project and it still fails to find it.
Why am I able to Project->Clean and run this project within the desktop AIR player (or on the device in debug mode) but unable to export it as a release build?
I have found a couple of threads mentioning a similar error but none of them have been marked as resolved.

At this point I feel I am talking to myself, but I will share my work-around in case it helps another who may stumble across this post.
In my particular case, both my main AIR application and my ANE wrapper library were referencing the same external Flex library (same revision). Both projects had the library linkage set to merge. Changing the linkage to "External" on one of the 2 libraries (it doesn't seem to matter which) and leaving the other as "Merged into code" enabled the export to complete without the bizarre "Unable to find named traits" error.

"Unable to find channel ID" error.

Similar Messages

Maybe you are looking for