Error in crystal external component has thrown an exception

When the customer tries to print a report in crystal send this error external component has thrown an exception

Hi,
Is this occurring to all reports?
Thanks.
Clint

Similar Messages

SSRS 2008 R2 - Try to do some changes on an existing rdl - unexpected erro "External Component Has Thrown an Exception"

Hi,
I am working on SSRS 2008 R2 - Tried to do some changes on an existing rdl & save - An unexpected error "External Component Has Thrown an Exception" pop up
Any suggestions please to resolve it.
thank you !!!
best regards,
Venkat

Hi Venkat,
The issue may be caused by the Visual Studio tried to close an invalid handle. This problem may happen if the operating system is a debug version, not a retail version. Please refer to the following steps to check.
1. Right-click on "My Computer".
2. Click "Properties".
3. Make sure there is no "Debug" words at the end of the "Windows edition" section.
Reference:
http://connect.microsoft.com/SQLServer/feedback/details/467954/sql-server-2008-install-on-windows-server-2008-fails-with-external-component-has-thrown-an-exception
If the operating system is debug version, please re-install the operating system with retail version to solve the issue.
Hope this helps.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

VS 2010 This file could not be uploaded. The following error occured: External component has thrown an exception.

I just started getting this error message from my VS 2010 VB code, earlier this code ran without the error message. I suspect corruption since this error does not occur on another computer of mine. I tried repairing the installation of VS
2010 without results. Then I uninstalled VS 2010 and reinstalled it, but the error continues. The error message is not very definitive so I do not know how to proceed. I could provide the code, but it is rather lengthy and I don't get this error
with the VS 2010 installed on my laptop. So, I don't think my code is the issue. I would be very grateful for any suggestions you may care to offer for isolating and correcting this problem. Thank you. .......................Phil Hoop
Phil Hoop

Hi Phil,
What’s the template type of the project? Is it a BI project? Based on my research, the issue may be related to the following factors:
.NET Framework version of the project. If it targets .NET Framework 4.0 or higher, modify it to target .NET Framework 3.5 instead.
Debug or Release Configurations. If the project is set to Release Configurations, try to set it to Debug. For more information, please see:
http://msdn.microsoft.com/en-us/library/wx0123s5(v=vs.100).aspx
I noticed that you have asked another question in the asp .net forum, if the issue is not SQL Server BI project related, I suggest that you continue troubleshooting within the
thread in the asp .net forum.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

Encountered Error: Plugin has thrown an exception. See the cause

Hello,
I am trying to sync the simple_sync_android application. I imported the app to Eclipse, Built and run as to the android applcation. Now on the Android Emulator , I navigated to the Mobile Sync app (already deployed) and provided ID , PASSWORD and Host Url.

Now when I click the sync button....I keep getting the following error.
Re: Encountered Error: Plugin has thrown an exception. See the cause
Please help

TestStand API External Component Modified Since Last VI Save

I'm using TestStand 3.5 with LabVIEW, and deploying my code across multiple stations. The code is managed by Perforce (source code control). I'm keeping the stations identical by installing NI software from the same CDs (which I'll refer to as an "Original Station"), but it seems that over time the TestStand API will somehow be externally modified ("Modified Station"), which causes LabVIEW to recompile the VI. The Explain Changes dialog box states "VI recompiled. External component modified since last VI Save." If I save the recompiled changes on a Modified Station and submit the changes, an Original Station opening the VI will then recompile VI, stating that an external component has been modified since the last VI save. If I resave the VI on an Original Station, then the next time I open it on a Modified Station the recompile will occur.
This is problematic, because there will be a performance hit if LabVIEW has to recompile when opening VIs. In addition, it makes debugging difficult, because LabVIEW will prompt to save changes on all the VIs if they were saved on a different station state. Not to mention the unnecessary copies made in the source code control to maintain the history of the recompiling.
My current solution is to reinstall TestStand on all the Modified Stations. I set any TestStand strict typedefs that I use to non-strict typdefs, mass compile the TestStand addon folder in vi.lib, and then the station becomes an Original Station again. Overtime, it will modify itself and turn into a Modified Station. Since these stations are at multiple sites, it is very inconvenient to manage.
My questions are the following:
1. What is causing this external modification? Is there anyway to prevent it, so that the installation and code will not get modified so that all will remain Original Stations?
2. If it is not preventable, how can I force all stations to become a Modified Station, so at least they are all the same?
I've attached LabVIEW 8.5 VIs that demonstrate the VI differences. I've observed this behavior in LabVIEW 7.1 and 8.2 previously. If anyone also experience this behavior or has a work around, please post to this thread. If NI has insight on what is causing this behavior and how to prevent it, it will help me out greatly.
Thanks!
Attachments:
test_recompile_original_lv85.vi ‏7 KB
test_recompile_modified_lv85.vi ‏7 KB

Wilbur,
Do you have more than one version of TestStand or LabVIEW on the stations? Switching the active version of TestStand changes the registered version of the TestStand API which I believe is the external change that forces a recompile. If version switching is the cause of the problem you could prevent these changes by not sharing any TestStand VIs between different versions of TestStand. If each version of TestStand has its own VIs then a VI is compiled against one and only one engine version.
-Rick Francis

External component changed

Hi all,
Could anyone help me on this ?
When opening this VI (see attachement) on one computer it says that the VI was changed (external component changed) and that I have to save it. When I save it and open the VI again on a second computer, LabView outputs the same message, an external component has changed... so I have to save it... Back on the frist computer same message again... etc...
I still don't know what's the 'external component' that changes from one computer to another... and how to find it.
Thanks in advance for any help or hint...
Attachments:
untitled.JPG ‏119 KB

Ok, this is one of these VI's that have an external component changing...
As I said Before, when I open this Vi in two different computers, LabView tels me each time that an external component has changed and that I have to save it. I don't know what is the external component changing... how to find it ?
Thanks.
Attachments:
ADO Connection Open.vi ‏14 KB

RWRBE60.exe has generated an exception: access violation

I have a user who uses Oracle report called from a form. Several times a day she reports that she get a Dr. Watson application error saying that RWRBE60.exe has generated an exception: access violation when she invokes the report runtime (while running the report not printing it). She is running Windows NT Version 4.0, SP 6; She has 256K memory. She is running Forms 6.0.5.0.2 and Oracle Report 6.0.5.28.0. Any thoughts?
Thanks
Anandhi

I've got a similar problem. I'm running windows xp and reports 6.0.8.22 including Patch 13. I don't get the same error, but the RWRBE60.exe stops with a problem. That only occurs by using reports where the parameters are variable and only by the second time I call such a report. If I close the RWRBE60.exe after the first report that probem doesn't occur. Maybe you could check, whether the problem doesn't occur if you close RWRBE60.exe between two reports.

Error handling: Customizing error details: Info about the the path to the VI which has thrown the error

Hi,
I need a quick advice about how to display in the error cluster the information about the path and VI which has thrown an error.
When I don't prepare my own error message, and the error is captured automatically, the information about the path, Vi name and calling VIs is presented automatically.
When I prepare/define my own basic error cluster I have only what I define in the string part of the cluster.
How to cause tha apperance the path and VI name in my defined error message?

MimiKLM wrote:
You mean this link
That's helpful too but, I had read "When I prepare/define my own basic error cluster I have only what I define in the string part of the cluster" as you wanted to use a file to expose those custom error codes and ultimately ship them with your solution dynamically rather than statically
The error ring will pick up any custom errors you define in the error file(s). Including formatting! this then populates the explain errors and error dialogs just like any error definition that ships with any LabVIEW component or toolkit.
Certainly, an error ring can also STATICALLY define or re-define an error within the application instance the ring is called from. Those Error Rings are quite flexible!
Jeff

Code could not be generated because an external component or driver is missing

Greetings All,
     I've using Labview for a little over a year and I have an interesting situation with regards to Labview that I came across today. When I left off yesterday (01/11/12) my TestStand sequence was compiling fine. Today for some reason the compiler told me that one of the VI was broken or missing a sub vi. When I made my way through all the sub vi's in the vi that seemed to be a problem I came across "Code could not be generated because an external component or driver is missing".
     The problem started on the computer (NI PXI-8101 with WinXP and Labview 2010) located in a PXI-1044 that is in my Test Stand.  I have a complete backup on my laptop and my desktop computer which both compiling successfully with no errors. I tried installing the directory on another PXI-8101 and got a different set of results.  The first PXI-8101 gave 100+ errors in TestStand pointing to one of my vi's and the other PXI-8101 reported only one (1) error. The vi is basically using DAQmx vi's to create a "write to one line" action. I'm kind of stumped as to why it works on the laptop/desktop and not the PXI computers. All four computer are WinXP professional and Labview 2010. I saw somethings through google search engine but nothing conclusive. I'm hoping that someone can give me an explaination as to what is causing the error as described. Even if I copy over the directory it doesn't fix the problem. Thank you in advance for an information you provide with this rather interesting problem that I've encountered. If you require addition information let me know.
Regards,
Scott
Solved!
Go to Solution.

Greetings Beau,
     Thank you for the reply.
     I loaded the offending VI into Labview (2010) with TestStand inactive. Of course this was after I completely shutdown the computer and re-booted to ensure that nothing was resident in memory. I've included a couple of the error list boxes in this post.
     It comes down to a subvi that is two (2) subvi's deep. All these vi's are doing is commanding a write or read to and from the PXI-6509. When I check the VI at the level that has no broken run arrows (named below), nothing in the block diagram looks out of place as it should since these were installed by Labview installation. The vi that uses these vi's looks total normal and its block diagram doesn't have anything out of the ordinary yet the run arrow is broken. The odd part of this is that the top of the window that states the filename of the vi has an astrex at the end of the filename, even though nothing has changed in that vi.
Here is a list of the deepest level that has no broken run arrow:
DAQmx Create Channel (DI-Digital Input).vi
DAQmx Start Task.vi
DAQMX Read (Digital Bool 1Line 1Point).vi
DAQmx Clear Task.vi
DAQmx Create Channel (DO-Digital Output).vi
DAQmx Write (Digital U8 1Chan 1Samp).vi
     I guess the real question is what is the error message ("External component or driver missing") really telling me if all of the vi's look right. I appreciate any information you can send my way that will give me a better understanding of where this error is coming from. The program I developed had been running without a hitch for a month an all of sudden crash.
Thank you for your time in this matter.
Scott
Attachments:
Write to one port broken VI error list.JPG ‏47 KB
Readfrom one line broken VI error list.JPG ‏46 KB
Broken_VI_Error_Screen.JPG ‏56 KB

Error message: ni: A frame has been dropped and the acqusition has been canceled

I use a NI PCIe 1433 framegrabber with a Basler spl4096-140km line camera.
Using triggered acqusition with an external source, I can get a framerate of 68500Hz in NI-MAX.
When I use the Matlab image acquisiton toolbox to acquire data, I however very often get the error message: 'ni: A frame has been dropped and the acqusition has been canceled". This happens even at much lower framerates (20kHz) and only seems to go away when acquiring data slowly.
Computer is a Dell Precision 7600 and I assume there should be no issues with RAM or the PC being slow. The error does not go away when reducing the data size (i.e. reducing the ROI to one single point that is readout).
Do you have any pointers why this error message appears and what can be done about it?
Thank you!
Reto

Hello,
I encountered the same problem and I think it is because the allowcation of storage in matlab cannot catch up with that of the camera so that it will drop frames when the buffer is full.
I also want to know how to solve that.
Yang

Interface Mapping run time error...java.lang.nullpointerException thrown

Hi,
I am trying to create a simple f2f scenairo and when I tested the configuration xi throws this message as :
Interface Mapping run time error...java.lang.nullpointerException thrown during application mapping.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:TimeSent>2007-01-09T03:43:49Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>CAMEL_BS_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>Camel_BService_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Target01_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>j5qiPBwVPU2yonkPwhdt/g==</SAP:ObjectId>
<SAP:SWCV>tR26oJ7nEdu5oM/vCXwv+g==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_Equipment_MM_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Equipment_MM_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-01-09T03:43:49Z" wasRead="false">
<SAP:Engine type="AE">af.pi7.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2007-01-09T03:43:50Z" wasRead="false">
<SAP:Engine type="IS">is.03.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20070108</SAP:Date>
<SAP:Time>224350</SAP:Time>
<SAP:Host>gbdci550</SAP:Host>
<SAP:SystemId>PI7</SAP:SystemId>
<SAP:SystemNr>03</SAP:SystemNr>
<SAP:OS>AIX</SAP:OS>
<SAP:DB>DB6</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PIAFUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService>
<SAP:QIdInternal>XBTOW0__0001</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">097C2FFA403445A30F7600CE</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>168</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2608</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>168</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>67</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Sender_Agreement_GUID>49574D50A74F3F5D902E20831759594C</SAP:Sender_Agreement_GUID>
<SAP:Serialize_Children>X</SAP:Serialize_Children>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.025474</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.064329</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.067038</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.085552</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.085573</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.472198</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.473649</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.483159</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.483341</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.48668</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.486921</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.49182</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.491835</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.720028</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.721545</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 9E0AD3009F9311DB8770000D60514DD2</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOW0__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="1" type="T">Interface Mapping http://kia.com/fiel2file Equipment_IM_Outbound</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_Equipment_MM_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Please I request to give me some hint how to troubleshoot this issue.
Thanks a lot,
Srujan

Hi, i have the same type of error when testing configuration, but it seems that the mapping even doesn't start :
i'm creating an EBP to XCBL scenario, so it's a RFC->XI->XCBL 3.5
Here is the Java exception
Mappage d'interface
Can someone be helpful for that ?
Regards
Laurent
Message was edited by:
Laurent Gitton

Error in Crystal Reports Runtime for VS 2008

Hi, everyone...
I have an app that have some reports.
On my DevMachine, works fine. But when I deploy in ServerMachine (Windows Server 2003 R2 64), the app fails when I try to access a page that have a Crystal Report component.
Retrieving the COM class factory for component with CLSID {5FF57840-5172-4482-9CA3-541C7878AE0F} failed due to the following error: 800736b1.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {5FF57840-5172-4482-9CA3-541C7878AE0F} failed due to the following error: 800736b1.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[COMException (0x800736b1): Retrieving the COM class factory for component with CLSID {5FF57840-5172-4482-9CA3-541C7878AE0F} failed due to the following error: 800736b1.]
   CrystalDecisions.CrystalReports.Engine.ReportDocument..cctor() +207
[TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.]
   CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor() +0
   test.Page_Load(Object sender, EventArgs e) +999
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
I tried so many things, such as verify permissions, change registry and other stuff, without success.
I have installed on my server machine, the correctly (I think) version of Crystal Runtime
Please help me!
Thanks..

Yes..
The app pool is running as 32bit... and the OS is 64bit..
Actually, there is something that can help..
Before this error appear (800736b1),
other error (800002ad UNKNOWN.RPT) was appearing...
After that I filled the property "TempDir" in the registry with a directory that had enough permissions,
the (800736b1) began to show.
Maybe you have the answer for this error (unknown.rpt)...
I already read the document (UNKNOWN Crystal Reports for .NET Troubleshooting the Background Processing Error Message),
but nothing in this document worked for me.
Edited by: lukinha on Jun 20, 2011 6:29 PM

Error on using MyFaces component

Hy all,
I don't know if someone as already tested to work with JSF and MyFaces on its WebAS.
In fact I've started by developping a simple JSF page
and next I would like to add some sweet component by using MyFaces and Tomawakh.
For the JSF page, no problem, it rulez, but, when I <b>just</b> add "myfaces-api-1.1.3.jar" and
"my-faces-impl-1.1.3.jar" and deploy it to my server.
No error during deploying but when I'm trying to open a
JSF page I get this long error :
#1.5#000D606F6C2B0026000000270000137800041B1DE87681AB#1155715175094#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#sap.com/NewsDisplayJSFApp#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#Guest#2####2839db702cfd11db94ff000d606f6c2b#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Server#Plain###Runtime error in compiling of the JSP file <D:/usr/sap/DEP/JC00/j2ee/cluster/server0/apps/sap.com/NewsDisplayJSFApp/servlet_jsp/newsDisplayJSF/root/NewsError.jsp> !
The error is: java.lang.NullPointerException: null
Exception id: [000D606F6C2B0026000000260000137800041B1DE8767EC8]#
#1.5#000D606F6C2B0026000000280000137800041B1DE8768B06#1155715175094#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/NewsDisplayJSFApp#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2####2839db702cfd11db94ff000d606f6c2b#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Processing HTTP request to servlet [Faces Servlet] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [D:/usr/sap/DEP/JC00/j2ee/cluster/server0/apps/sap.com/NewsDisplayJSFApp/servlet_jsp/newsDisplayJSF/root/NewsError.jsp].
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:117)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:238)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:429)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:169)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:100)
     at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:64)
     at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:224)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:373)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NullPointerException
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.validate(JSPParser.java:235)
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:348)
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:105)
     ... 30 more
I mean, in each JSP page I'm trying to use those standard taglib :
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
It crashes.
I've try to add in my web-inf/lib some jar like : servlet_api.jar, servlet.jar, and so on but nothing seam to be working.
I've also try to define the extensionFilter of myfaces in my web.xml but it doesn't help me
Anyone has an idea ? I'll give reward
Thx.

Hy,
try do do this:
1) extract the JSF Tag-Lib's from the Jar-File in a folder under the WebContent folder (in my example named as "tld")
2) Add some TagLib- Entries in the WEB.XML like this:
<taglib>
   <taglib-uri>http://java.sun.com/jsf/core</taglib-uri>
   <taglib-location>tld/jsf_core.tld</taglib-location>
</taglib>
<taglib>
   <taglib-uri>http://java.sun.com/jsf/html</taglib-uri>
   <taglib-location>tld/html_basic.tld</taglib-location>
</taglib>
<taglib-uri> ist the URL that you use in the JSF Pages and <taglib-location> is the location of the expanded Tag-Libary.
The example above ist based on the Sun-Faces components but it works in the same way for Myfaces oder for the Oracle ADF faces.
Instead of the both Jar's myFaces-api and mafaces-imp I have use the myfaces-all.jar.
I hope this informatin will help you.

Error in Invoking peoplesoft component interfaces from BPEL process

I developed a sample bpel process to invoke peoplesoft component interfaces.
I followed the steps mentioned in the document.
http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28997/bpel_pm.htm#CDEICHJB
When I run the BPEL process, I got the following error.
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/LOCATION_invoke.wsdl?wsdl [ LOCATIONPortType::LOCATION(input_LOCATION,output_LOCATION) ] - WSIF JCA Execute of operation 'LOCATION' failed due to: Error in parsing the input document.; nested exception is:
     javax.resource.ResourceException: Error in parsing the input document
I found the following message in the log located at <ORACLE_HOME>/adapters/C:\product\10.1.3.1\OracleAS_1\adapters\application\config\jca_sample\log.
Tue, 29 Jan 2008 18:30:47.0963 EST - Thread[WorkExecutorWorkerThread-2,5,main] [info ] [IWAF JCA PeopleSoft] IWAFManagedConnection for PeopleSoft:ica_psft has listener registered: com.evermind.server.connector.ConnectionContext@170d1b3
Tue, 29 Jan 2008 18:30:48.0307 EST - Thread[WorkExecutorWorkerThread-2,5,main] [info ] [IWAF JCA PeopleSoft] Local transaction not supported by underlying adapter.
Tue, 29 Jan 2008 18:30:48.0307 EST - Thread[WorkExecutorWorkerThread-2,5,main] [info ] [IWAF JCA PeopleSoft] IWAFManagedConnection for PeopleSoft:ica_psft dispatch event 2
Tue, 29 Jan 2008 18:30:48.0307 EST - Thread[WorkExecutorWorkerThread-2,5,main] [error] [IWAF JCA PeopleSoft] **** Error in parsing the input document.
oracle.xml.parser.v2.XMLParseException: Start of root element expected.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:205)
     at com.iwaysoftware.idom.XmlDocument.parse(XmlDocument.java:120)
     at com.iwaysoftware.idom.XmlDocument.setRootXML(XmlDocument.java:77)
     at com.ibi.afjca.cci.IWAFInteraction.execProcess(IWAFInteraction.java:195)
     at com.ibi.afjca.cci.IWAFInteraction.exec(IWAFInteraction.java:136)
     at com.ibi.afjca.cci.IWAFInteraction.execute(IWAFInteraction.java:93)
     at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:470)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:431)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:416)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:222)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:736)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:371)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3271)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1697)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:184)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:269)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5244)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1083)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:530)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:333)
     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:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:396)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:622)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
     at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
     at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
     at java.lang.Thread.run(Thread.java:595)
Tue, 29 Jan 2008 18:30:48.0323 EST - Thread[WorkExecutorWorkerThread-2,5,main] [error] [IWAF JCA PeopleSoft] SOS !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tue, 29 Jan 2008 18:30:48.0323 EST - Thread[WorkExecutorWorkerThread-2,5,main] [error] [IWAF JCA PeopleSoft] oracle.xml.parser.v2.XMLElement@4f9c1a
Tue, 29 Jan 2008 18:30:48.0323 EST - Thread[WorkExecutorWorkerThread-2,5,main] [error] [IWAF JCA PeopleSoft] EOS !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tue, 29 Jan 2008 18:30:48.0323 EST - Thread[WorkExecutorWorkerThread-2,5,main] [info ] [IWAF JCA PeopleSoft] IWAFManagedConnection for PeopleSoft:ica_psft dispatch event 4
I am sending the following input to run the bpel process.
<PS8 SERVICENAME="LOCATION" METHODNAME="LOCATION" LICENSE="test">
<component perform="browse">LOCATION</component>
<key name="SETID">SHARE</key>
<key name="LOCATION">ALBERTA</key></PS8>
Can anyone help in sending the right input xml to component interface?

I do the same thing.
Take wsdl from axis and save it somewhere.
Then you can create a standard project in Oracle BPEL PM. Create partnerlink, give a name and click on first icon to take your wsdl. It will add some needed code, you answer always yes. Then you can create receive, assign, invoke, assign and callback or similar and deploy it.
Try it through BPEL Console...
Ema

HP CUE-Scanning Flow Component has stopped working on printer settings

Hello,
When i click Printer Settings or when i am done with scan and need to send it to printer i got: HP CUE-Scanning Flow Component has stopped working error. Specifications of system are below.
OS: Windows 7
Scanner: HP ScanJet G2400 (System saying: G2410 )
Printer: HP LaserJet 1010 USB ( Drivers for Win XP by reccomendation from this forum, not my post )
Solution Center Ver: 130.0.44.62
I belliwe error is printer driver, and dont say to switch to Vista drivers, TOO buggy.
This question was solved.
View Solution.

Hello ArsenArsen,
Welcome to the HP Forums!
I understand your concerns. Unfortunately, for this Scanjet and this Laserjet printer, I need to direct you to our Enterprise Business Community Forums. This will be the right section to troubleshoot this issue.
Good luck.
I worked on behalf of HP.

Error in crystal external component has thrown an exception

Similar Messages

Maybe you are looking for