ADAPT mode PDI exception

Hi Experts.
I just received access to a new SAP Cloud for customer system. I setup the Admin user for myself following the cloud setup guide.
I just wanted to add an extra field in account screen by going into ADAPT mode. However , when i go into ADAPT mode and click on 'edit screen' it throws up an error saying "PDI Exception occured" and messahe text as "Enable Administration mode for the Solution". I am perplexed as to what is missing in the access rights as i have tried to have most of the access rights assigned.
Any help is appreciated.
Thanks
Apoorva

Hi Horst,
I had a suspicion that setting the Administration mode on in the studio would be a solution (I've had to do this form uploading form templates for some bizarre reason).
However, I have just tried to do this in our C4C system and I am unable to turn on the administration mode in the studio. Even when I try to create a new solution it says that I do not have administration rights even though I have assigned these in the user managment.
Could this be due to some conflict with the user access rights? I am having the same problem with ByDesign where I cannot activate the Administration Mode in the studio. Do you have any idea why this is happening?
Thanks,
Alexander Ludwig

Similar Messages

PI 7.11: Adapter Framework caught exception: null

Hi,
I've a ABAP Proxy - to - SOAP scenario.
Message mapping works.
In the communication channel monitor I get the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
Adapter Framework caught exception: null
In the log viewer in NWA I see the following two messages:
Marked transaction for rollback for meesage 516e304f-b083-8e3e-e100-00000a01095f(INBOUND). Reason: <null>
Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 516e304f-b083-8e3e-e100-00000a01095f(INBOUND)
The payload for calling SOAP receiver looks like that:
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
         <ns1:e xmlns:ns1="http://test.com">
            <address_Mail_Incoming_Type>
               <email>test.com</email>
               <phone>7890</phone>
            </address_Mail_Incoming_Type>
            <badge_ID>123</badge_ID>
            <cost_Center>321</cost_Center>
            <date_Hired>1980-01-01T00:00:00.000Z</date_Hired>
            <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
            <department>123</department>
            <division>ABC</division>
            <employee_Category>A</employee_Category>
            <employee_Code>1000</employee_Code>
            <employee_Id>1000</employee_Id>
            <employee_Status>ACTIVE</employee_Status>
            <first_Name>A</first_Name>
            <last_Name>B</last_Name>
            <letter_code_3>FRI</letter_code_3>
            <location>123</location>
            <position>123</position>
         </ns1:e>
      </m:setEmployee>
When I copy this payload into SOAP UI (surrounded by <soapenv:Envelope>, <soapenv:Header> and <soapenv:Body>), the WS call works.
The URL for the receiving CC should be ok (same as in SOAP UI), the "Do not use SOAP Envelope" checkbox is not flagged.
What can be the reason for that error message?
Thanks in advance!

I've now changed the setting of the external definition to "Using RPC style", but I'm still running into the same error than before:
10.02.2012 14:51:03 Information SOAP: sending a delivery error ack ...
10.02.2012 14:51:03 Error Adapter Framework caught exception: null
10.02.2012 14:51:03 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
10.02.2012 14:51:03 Information SOAP: sent a delivery error ack
10.02.2012 14:51:03 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
The payload of the CC looks exactly the same than before:
<?xml version="1.0" encoding="UTF-8"?>
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
     <ns1:e xmlns:ns1="http://test.com">
          <address_Mail_Incoming_Type>
               <email>test.com</email>
               <phone>123</phone>
          </address_Mail_Incoming_Type>
          <badge_ID>123</badge_ID>
          <cost_Center>123</cost_Center>
          <date_Hired>1990-01-01T00:00:00.000Z</date_Hired>
          <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
          <department>123</department>
          <division>ABC</division>
          <employee_Category>PERM</employee_Category>
          <employee_Code>1000</employee_Code>
          <employee_Id>1000</employee_Id>
          <employee_Status>ACTIVE</employee_Status>
          <first_Name>A</first_Name>
          <last_Name>B</last_Name>
          <location>ABC</location>
          <position>123</position>
     </ns1:e>
</m:setEmployee>
If I copy that payload (without <?xml version="1.0" encoding="UTF-8"?>) into SOAPUI (surrounded by SOAP envelope), the WS call works without any problem.
Why doesn't it work from PI?
Another question:
Why is it putting <ns1:e> into the payload of the new interface and <ns0:e> for the existing interface (which is working, see Re: PI 7.11: Adapter Framework caught exception: null)?
Could that be the reason why data is not sent properly to the SOAP receiver?

Adapter Framework caught exception - 401

Hi,
I am trying to use NTLM authentication using Axis adapter in PI 7.1 SP7 but getting 401 error.
Axis adapter works for Basic auth.
SAP Note 856597 talks about giving PI user security role xi_adapter_soap_message. Haven't found the equivalent navigation of visual admin in NWA.
Details from message monitoring
Information Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: (401)Unauthorized
Error Adapter Framework caught exception: (401)Unauthorized
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: (401)Unauthorized.
Any help is appreciated.
Thanks
Kiran Gollapudi

Hi guys,
Even the message being old, there are some of you that may want a hint on how to solve this problem.
First of all, please refer to the generic description of the error that may help one of you:
401 Unauthorized
Description: The request requires user authentication
Possible Tips:
u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
u2022 If the error is in Adapter Engine
u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
u2022 May be wrong password for user XIISUSER
u2022 May be wrong password for user XIAFUSER
u2013 for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
Alternatively, ensure you maintain the correct password for all the service users according to one of the notes
below, taking into account your system version:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
Hope I could helped.
Regards,
Caio Cagnani

Adaptation Mode HTML5 - deleted fields not show up anymore -Please Help

Hi SAP,
Hi was doing screen arrangements though the adaptation mode, and by mistake I dragged the label Purpose to an area out of the Expense Report screen area. the label and the field do not show up any more in the Expense Report from a non-Travel Related expenses and there is no way to add this field again, it doesn't show up either under the fields available to add.
since it is a required field i can't create the documents any more.

Hi,
there is a function "discard screen" also on the same menu.
Best regards,
Sigi

SCSM 2012 UR3 - "The Full adapter threw an exception" error when viewing "Deleted Items" view

Has anyone expereinced the "The Full adapter threw an exception" eror in the SCSM 2012 console?
We get the error in both our dev and production environments when trying to view the "Deleted Items" view in the console (even after using powershell to remove all deleted iterms). As just noted, interestingly enough we can view, delete, and restore
deleted items using the corresponding Powershell commands. It should be noted that neither of our two SCSM 2012 environments has a registered data warehouse server. Below is a screen shot of the error as well as the associated error text and event
log errors.
Any help would be greatly apprecaited!
Regards,
JJ
Console Dialog Error Test
============================
Date: 10/17/2012 8:46:50 PM
Application: Service Manager Console
Application Version: 7.5.1561.0
Severity: Error
Message: An error occurred while loading the items.
Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportException: The Full adapter threw an exception. See the FullUpdate property to see the exception.
   at Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportAdapter.DoAction(DataQueryBase query, IList`1 dataSources, IDictionary`2 parameters, IList`1 inputs, String outputCollectionName)
   at Microsoft.EnterpriseManagement.UI.DataModel.QueryQueue.StartExecuteQuery(Object sender, ConsoleJobEventArgs e)
   at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
Associated Event Log Errors
============================
Log Name:      Application
Source:        MSSQLSERVER
Date:          10/17/2012 8:46:49 PM
Event ID:      8623
Task Category: Server
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      jhqsrv08.jhq.net
Description:
The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you
believe you have received this message in error, contact Customer Support Services for more information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSSQLSERVER" />
    <EventID Qualifiers="49152">8623</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-18T00:46:49.000000000Z" />
    <EventRecordID>339617</EventRecordID>
    <Channel>Application</Channel>
    <Computer>jhqsrv08.jhq.net</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Binary>AF21000010000000090000004A00480051005300520056003000380000000F00000053006500720076006900630065004D0061006E0061006700650072000000</Binary>
</EventData>
</Event>
Log Name:      Operations Manager
Source:        DataAccessLayer
Date:          10/17/2012 8:46:49 PM
Event ID:      33333
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      jhqsrv08.jhq.net
Description:
Data Access Layer rejected retry on SqlError:
Request: MTV_Select_62f0be9f-ecea-e73c-f00d-3dd78a7422fc_Top -- (NonGenericDistinctFilterForAbstract=4cf77750-6688-8672-9470-036e0f4b48d6,26b2dff7-2ce9-59cf-4eb8-a6fb2d095d45,89992420-1297-0b8b-f3ca-1e53aa36f9e0,ed5ec2bf-6745-086...), (ObjectStatus_4AE3E5FE_BC03_1336_0A45_80BF58DEE57B0=47101e64-237f-12c8-e3f5-ec5a665412fb)
Class: 16
Number: 8623
Message: The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify
the query. If you believe you have received this message in error, contact Customer Support Services for more information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="DataAccessLayer" />
    <EventID Qualifiers="32768">33333</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-18T00:46:49.000000000Z" />
    <EventRecordID>935685</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>jhqsrv08.jhq.net</Computer>
    <Security />
</System>
<EventData>
    <Data>MTV_Select_62f0be9f-ecea-e73c-f00d-3dd78a7422fc_Top -- (NonGenericDistinctFilterForAbstract=4cf77750-6688-8672-9470-036e0f4b48d6,26b2dff7-2ce9-59cf-4eb8-a6fb2d095d45,89992420-1297-0b8b-f3ca-1e53aa36f9e0,ed5ec2bf-6745-086...),
(ObjectStatus_4AE3E5FE_BC03_1336_0A45_80BF58DEE57B0=47101e64-237f-12c8-e3f5-ec5a665412fb)</Data>
    <Data>16</Data>
    <Data>8623</Data>
    <Data>The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions.
Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.</Data>
</EventData>
</Event>
Log Name:      Operations Manager
Source:        OpsMgr SDK Service
Date:          10/17/2012 8:29:26 PM
Event ID:      26319
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      jhqsrv08.jhq.net
Description:
An exception was thrown while processing GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions for session ID uuid:66ba50da-cdce-4d15-823c-92c41b46fe44;id=2425.
Exception message: The creator of this fault did not specify a Reason.
Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to The query processor ran out of internal resources and could
not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact
Customer Support Services for more information.).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="OpsMgr SDK Service" />
    <EventID Qualifiers="49152">26319</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-18T00:29:26.000000000Z" />
    <EventRecordID>935679</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>jhqsrv08.jhq.net</Computer>
    <Security />
</System>
<EventData>
    <Data>GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions</Data>
    <Data>uuid:66ba50da-cdce-4d15-823c-92c41b46fe44;id=2425</Data>
    <Data>The creator of this fault did not specify a Reason.</Data>
    <Data>System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to The query processor ran out of internal resources
and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error,
contact Customer Support Services for more information.).</Data>
</EventData>
</Event>

I have the same problem and get following error:
An exception was thrown while processing GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions
I have contacted MS Support, but hey could not help
either.
I really
need to fix it. Any help?

Alert mode in exception

Hi to all
I want to define a alert mode in exception , but i am not getting in AWB that reporting agent option , first time i am using 7.0 , can any body help me
Thanks in advance
shalini

Hi Shalini,
In BI 7.0 there is no reporting agent.
Exception broadcasting is now available in the Broadcaster. Create the exceptions in the query designer and select distribution type in the broadcaster. You can also use additional distributions types (subordinate) and create rules for when the exception report is monitored/executed. Exceptions can be based on single events or levels of any performance measure.
Hope it helps.
Shylaja.

Deleted Items Exception - The Full adapter threw an exception

Running SCSM 2012 R2 UR3, when trying to access the 'Deleted Items' view, the console has an exception:
Application: Service Manager Console
Application Version: 7.5.3079.0
Severity: Error
Message: An error occurred while loading the items.
Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportException: The Full adapter threw an exception. See the FullUpdate property to see the exception.
   at Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportAdapter.DoAction(DataQueryBase query, IList`1 dataSources, IDictionary`2 parameters, IList`1 inputs, String outputCollectionName)
   at Microsoft.EnterpriseManagement.UI.DataModel.QueryQueue.StartExecuteQuery(Object sender, ConsoleJobEventArgs e)
   at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
Any suggestions please? is this a known issue?

Yep, that's the problem I had. SQL is trying to union more tables than it can handle..hence the failed query plan. Removing some of the SCSM classes (and thus removing SQL tables) is an approach..but it's a bad approach.
There may be a SQL solution. There may be some kind of threshold that can be adjusted or query plan settings that can be tweaked..I'm afraid I simply don't know (As I've told people many times, I only know enough SQL to be dangerous :) ).
The other approach we used was to create specific Deleted Items views that targeted specific classes. It didn't solve the problem, but it at least gave us the ability to permanently remove or restore objects of some classes from the console.
I can say that I haven't seen the error in at least 3 months (this problem originally occurred back in March). But, again, we've tried to keep our deleted items around 5000 by regularly cleaning it out.
We're on R2 UR2, but I'm afraid I don't know if it was fixed in that update or a previous one..or if it's been fixed at all.
I've said "I don't know" a lot in this post..I'm sorry I'm not much help with this one.

Xi 3.0: Mail adapter fails with "exception in method process"

Hi.
I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
I tried both async and sync case with the same result. In the sync case, the response contains:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea???

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
Anyway, in my server i get a 404 for the link you suggested.
In the async case i don't get any error on the SXMB_MONI but only on the A.F.
I attach the audit log for the async case:
Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
Time Stamp Status Thread ID Sequence No. Description
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
Total: 33 Entries 1020304050 messages displayed per page; this is page 1 of 1 page(s)

Sender ADapter Monitor- ArrayIndexOutOfBOunds Exception

Hi
As me subject line reads, I am getting an "ArrayIndeXOutofBOunds 9" exception at the sender adapter monitor logs in the RWB.
I have an a<i>dapter monitor module</i> that picks up the file from the source and pushes the file to a target directory based on some condition. I am able to see the file being pushed to the target directory but not able to view the "pipeline steps" in the message monitor.
Do you think a restart of the server might fix the issue/ do you think there is a problem in my code. I have used just one array and i have checked that array if it is being accessed out of its bounds?
Thanks
krishna

Hi,
>>>>>ArrayIndeXOutofBOunds 9"
looks like an error in code
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>

JMS Receiver Adapter Catching MQ Exceptions

Hi Experts,
We are running into an issue with our JMS receiver adapter failing PI. We are trying to send transactions via the adapter to a MQ Series' queue but it is failing after no transactions have been sent after a period of 3 hours or more. The only way we can flush the queue is to change the setting on the adapter to Bypass, restart the adapter and then resend the message. Once we do this, everything runs fine throughout the day. It seems to be the amount of time between transactions be processed on the queue.   For instance, last night the last transaction processed successfully was at 7:36pm EST. Then around 11:40pm EST we tried sending another and this is when we caught an exception from MQ once again. We have tried everthing that we know of u2013 we thought it might have been a background job running on PI that causes the issue but last night proved that it wasnu2019t the issue since it occurred before midnight. I feel that the issue is between our JMS connection and your MQ. Below is the message log of the transaction:
What course of action should we take next in diagnosing the issue?
Audit Log for Message: 1c728f10-2044-0441-0a04-604e2cf00000
Time Stamp     Status     Description
2009-05-21 22:40:48     Success     Message successfully received by messaging system. Profile: XI URL: http://bus0157:52000/MessagingSystem/receive/AFW/XI Credential (User): PIPISUSER
2009-05-21 22:40:48     Success     Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-05-21 22:40:48     Success     Message successfully put into the queue.
2009-05-21 22:40:48     Success     The message was successfully retrieved from the receive queue.
2009-05-21 22:40:48     Success     The message status set to DLNG.
2009-05-21 22:40:48     Success     Delivering to channel: JMS_IDOC_SPK_RCV
2009-05-21 22:40:48     Success     MP: Entering module processor
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService
2009-05-21 22:46:48     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP
Time Stamp     Status     Description
2009-05-21 22:46:48     Error     Exception caught by adapter framework: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP?targetClient=1 JMSReplyTo:      null JMSRe
2009-05-21 22:46:48     Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP.

Ok, would you mind taking a look at my forum question titled "Multiple Message Types into one Websphere Message Queue", it may be an easy one for you since you are already doing this!
Best regards,
Aaron
[Multiple Message Types into one Websphere Message Queue|Multiple Message Types into one Websphere Message Queue]

SFTP adapter error : Catching exception calling messaging system

Error: com.aedaptive.sftp.adapter.SFTPException : Not all messages were delivered succesfully
Could not deliver message to XI: com.sap.aii.af.lib.mp.module.ModuleException: senderChannel 'ca09269447583427adc545f8c23d244b': Catching exception calling messaging system
This is error message which i get in sender communication channel while working with SFTP adapter.

Hi Pooja,
I think it would be better to add getcause() to get the cause of the issue.
Ref: http://help.sap.com/javadocs/pi/SP3/xpi/com/sap/aii/af/lib/mp/module/ModuleException.html
Thanks,

Custom adapter module throwing exception

Hi,
We have written an adapter module (EJB) to convert a file structure into XML for conversion in XI. Using file adapter(FTP), we are getting the files converted into XML without any problem. However, when there is no file in the directory the module is throwing an exception and writing an entry into the log (polling interval is 1 minute).
The requirement is when there is no file in the directory, the adapter should keep on polling, but without generating any exception or making an entry in the log.
Can anyone help out with this please?

strange...
if a file is not found in the specified directory where your file adapter is polling, it is not possible that the control comes to the adapter module you have specified in the module chain.
have you done something unusual in your CC config i.e. added only your module in the module chain and removed CallSAPAdapter

DB Adapter 902 binding exception while passing parameters for simple string

Hi,
I have an PlSQL API with two input paramters of string type... But this is only started after XML validation TRUE on the BPM server.
The error is
<bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>902</code>
</part><part name="detail"><detail>
Internal Exception: java.sql.SQLException: ORA-00902: invalid datatype
Error Code: 902</detail>
</part><part name="summary"><summary>file:/oracle/product/10.1.3/soa/bpel/domains/Website/tmp/.bpel_BPELProcess1_1.0_c64929dfd2dacf95db3c9da081c1797d.tmp/callingAPI.wsdl [ callingAPI_ptt::callingAPI(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'callingAPI' failed due to: Error while trying to prepare and execute an API.
An error occurred while preparing and executing the XXRBA.XXRBA_WEB_ADAPTER.FETCH_CUSTOMERS API. Cause: java.sql.SQLException: ORA-00902: invalid datatype
[Caused by: ORA-00902: invalid datatype
; nested exception is:
ORABPEL-11811
Error while trying to prepare and execute an API.
An error occurred while preparing and executing the XXRBA.XXRBA_WEB_ADAPTER.FETCH_CUSTOMERS API. Cause: java.sql.SQLException: ORA-00902: invalid datatype
[Caused by: ORA-00902: invalid datatype
Check to ensure that the API is defined in the database and that the parameters match the signature of the API. Contact oracle support if error is not fixable.
</summary>
</part></bindingFault>
The input XSD parameters in BPEL input
<element name="input" type="string"/>
The input XSD parameters in ADAPTER
<element name="P_WEB_ACCOUNT" type="string" db:index="1" db:type="VARCHAR2" minOccurs="0" nillable="true"/>
<element name="P_SOLICITED_ONLY" type="string" db:index="2" db:type="VARCHAR2" minOccurs="0" nillable="true"/>
The assignment I am doing in the .bple file is
<assign name="Assign_1">
<copy>
<from expression="bpws:getVariableData('inputVariable','payload','/client:BPELProcess1ProcessRequest/client:input')"/>
<to variable="Invoke_1_callingAPI_InputVariable" part="InputParameters"
query="/ns2:InputParameters/ns2:P_WEB_ACCOUNT"/>
</copy>
<copy>
<from expression="string('o')"/>
<to variable="Invoke_1_callingAPI_InputVariable" part="InputParameters"
query="/ns2:InputParameters/ns2:P_SOLICITED_ONLY"/>
</copy>
</assign>
--Khaleel

You have an attribute type in an object service that is supposed to be numeric, but when reading form the database it seems that is retrieving a non-numeric content...
Cheers,
Vlad

BC4J send messaging adapter gets JMS exception

Running a 9i standalone application based on BC4J. The following code is trying to send a single VO to an 8i queue. Note: prior to entering this routine, I have already called the .writeXML() method on the same VO and looked at the text and the XML all looks great.
AdapterMessage[] msgs = new AdapterMessage[1];
try {
// set up queue connection
msgs[0] = AdapterMessage.newViewObjectMessage( vo );
sendMessage( msgs );
public void sendMessage( AdapterMessage[] messages)
try
ApplicationModule am = QWsetup.ApplicationModule();
BC4JSendingAdapter adapter = new BC4JSendingAdapter();
adapter.setShowTrace(true);
adapter.sendMessage( am, messages);
catch(AdapterFailureException e)
System.err.println("sendMessage error: "+e.getMessage()+"\n"+
e.getOriginalException());
e.printStackTrace();
I step into the adapter.sendMessage line and get the following in my message window...
[2] Creating JDBC Connection...
[3] oracle.jdbc.driver.OracleDriver
[4] jdbc:oracle:thin:@pgia05.pginw.com:1521:qmpgit
[5] Creating Topic Connection...
[6] Creating Topic Session...
[7] Creating Topic...
[8] Publishing message...
[9] Done.
sendMessage error: JMS exception while processing message
java.lang.NullPointerException

Hi Roger,
I've been looking into your error message: JMS Exception while processing message.
I was able to reproduce this error message. In my case I was trying to send a BESAdapter message without setting its mandatory properties. My code was:
BESAdapterMessage a = (BESAdapterMessage)BESAdapterMessage.newViewObjectMessage(empvo);
BESAdapterMessage[] messages = new BESAdapterMessage[] {a};
try
am.sendMessage(messages);
There are two mandatory properies of the adapter that must be set that I forgot. I found the answer in the help. If you do a search for BESAdapterMessage you will find page Using the Adapter Message class for message payloads. Scroll down this page to the section: Using the BESAdapterMessage Subclass.
Although you are using the adapter classes without the modeler you may find some of the other help topics in the UML Modeling Help useful. Look under Modeling Activities for e-business Integration -> Creating Messaging Adapters.
I have raised a bug to put more validation in so that the error message will specify that properties have not been sent. Here is the abstract from help:
The BESAdapterMessage class (oracle.bm.ebiadapters.BESAdapterMessage) is a subclass of AdapterMessage. It provides additional functionality which is needed by the e-business integration generators to achieve full integration. In addition to setting the payload, the BESAdapterMessage class allows you to set metadata properties which are mapped to JMS header fields. Some of these properties are mandatory and some are optional. For example, the setEventName(String eventName) and setEventKey(String eventKey) methods can be used to set the mandatory Event Name and Event Key properties. Once set, these properties are mapped to JMS header properties to allow the JMS messages to be correctly propagated between Oracle AQ queues.
I've also raised a doc. bug to look again at the doc in this area.
Thank you very much for taking the time to report on this problem. We are reliant on input from people like you to continue to improve our product.
Rgds
Susan

PreparedStatement in batched mode gives Exception

Hi
I have a problem.
I am running PreparedStatement in batched mode, actually I am using Springs BatchSQLUpdate component.
Now i am creating a batch of about 10000 inserts / updates. However if any single of these inserts / updates fails, it gives exception with DataIntegrityViolation, BadSQLGrammer etc.
I am also maintaining a parallel cache of the values that I am using to bind the preparedstatements.
So for statement 1 in the batch, i know what values are being used.
My question is when the batch update fails, how can we identify which SQL statement, i mean which index in the batch caused the issue?
Please help me as I am stuck and need to build some robust exception handling for PreparedStatement batch loads.
Niki

Niki-Nono wrote:
The insertPreparedStatements.get() in my code returns a BatchSqlUpdate object which has already been assigned a statement and also have passed the array of object values to it.
I have done this using batchSqlUpdate.update(objects); where objects is an array of values.
THe code block that I executes the flush(). This throws an exception. In some cases it is a BadSQLGrammerException for cases where we try to insert alphabets in integer columns or in some cases DataIntegrityViolation where the batch has 2 sets of values with same primary key.
The results array is null when i check the value in the catch block.
And the flush() does not proceed with execution of the complete batch in fact it aborts when even 1 statement fails.
I hope it is clearer now.
However, if all the statements go through, I have seen that the results array has correct values as to how many rows were updated / inserted.
Please let me know.OK, I really wasn't sure about what it did on flush, as there's no explicitly stated exception and nothing in the method description. The array will be null since it hasn't been set with the return value from flush since an exception was thrown.
From what I can tell this Spring class uses, under the hood, the batch functionality from JDBC. So the particular exceptions you;re getting will have started life as SQLExceptions...which themselves will be of the BatchSQLException I mention in my first post. I'm wondering if the Spring exceptions contain the SQLException. I would hope so, and I have a vague recollection that the original is wrapped so you should be able to do something along the lines of:
catch (DataAccessException ex)
    SQLException ex = ex.getCause();
    if (ex instanceof java.sql.BatchUpdateException)
        // Get the info from here.
}Now, this is only a concept, and I haven't tested it or anything, but I would hope something along these lines should get you to the data you're after.

ADAPT mode PDI exception

Similar Messages

Maybe you are looking for