ORA-24816 Error on EDI inbound processing

We are encountering an issue for EDI X12  inbound data files which have extraneous characters. B2B initially failed throwing  “ Document Protocol Identification error “ .
To resolve this, we enabled flag  “b2b.edi.enablePeprocess” to true , after which it started processing fine in DEV environment , however it throws below exception in QA environment .
Internal Exception: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column
Error Code: 24816
Call: INSERT INTO B2B_WIRE_MESSAGE (ID, JOB_ID, ACKNOWLEDGEMENT_MODE, LABEL, ATTRIBUTE2, MESSAGE_DIGEST, ATTRIBUTE4, MESSAGE_ID, ATTRIBUTE3, ATTRIBUTE5, CPST_INST_CREATED_TIME, CREATED, LAST_RESUBMITTED_TIME_STAMP, MODIFIED, LAST_VIEWED_TIME_STAMP, MSG_SIZE, DELIVERED_ENDPOINT, PASSWORD, DIRECTION, PORT, ENCRYPTION_CERTIFICATE, PROTOCOL_COLLABORATION_ID, ERROR_CODE, PROTOCOL_MESSAGE_ID, ERROR_DESCRIPTION_CLOB, PROTOCOL_TRANSPORT_BINDING, ERROR_TEXT_CLOB, REFER_TO_PROTOCOL_MESSAGE_ID, EXCHANGE_REMAINING_RETRY, RESUBMIT_COUNT, FROM_ADDRESS, SIGNING_ALGORITHM, SIGNING_CERTIFICATE, MESSAGE_STATUS, SIGNING_PROTOCOL, LAST_VIEWED_USER_NAME, STATE, DIGEST_ALGORITHM, TO_ADDRESS, ENCRYPTION_PROTOCOL, TRANSPORT_CERTIFICATES, ERROR_TEXT, TRANSPORT_CORRELATION_ID, EXCHANGE_RETRY_INTERVAL, TRANSPORT_HEADERS, ATTRIBUTE1, TRANSPORT_PROTOCOL, CHANNEL_NAME, TRANSPORT_PROTOCOL_VERSION, ERROR_DESCRIPTION, TRANS_SECURITY_PROTOCOL, HOST_NAME, TRANS_SECURITY_PROT_VERSION, ENCRYPTION_ALGORITHM, URL, LAST_RESUBMITTED_USER_NAME, USER_NAME, EXCHANGE_ATTEMPT_COUNT, VERSION, PAYLOAD_STORAGE, PACKED_MESSAGE, RESUBMIT_REF_TO) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
        bind => [A513532C140185965980000010261DFC, null, SYNC, null, null, rLdBG4pYQf76lQXJZdl43gE7QqE=^M
We checked many options for the differences between Dev & QA , but could not find a root cause . 
Version : 11.1.1.6

Hi,
I am getting the same error.
Can u please help me on this.
Thanks and Regards
Neha Kapoor

Similar Messages

  • ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing

    Hi,
    I am trying to update an already existing Sales Order through PO Change Inbound 860. When i am performing changes in the line quantity and scheduled ship date with operation code as "Update" then it is successfully updating the Order and also we are able to generate the POAck for the updated sales order lines. But when i am rejecting one of the PO change lines by checking rejected flag, then order is getting imported successfully(I mean sales order is getting updated successfully) but during the POAck Generation i.e. 865 its raising "*ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00103: Warning: document structure does not match DTD Error at line 1*" at XML Gateway. we are using XML Gateway to process the orders, can somebody help me to get rid of this issue. Thanks in advance.
    Thanks,
    Sunil Chauhan

    Hi Kishan
    Thanks for the reply.
    Because this is an outbound transaction so i can not provide you the XML file as we are facing issue to generate the same. Also we are using oracle seeded PO outbound Ack map.
    In addition i can provide you the DTD file.
    <!-- ==================================================== -->
    <!ENTITY % RESOURCES SYSTEM "oagis_resources.dtd">
    %RESOURCES;
    <!-- ==================================================== -->
    <!ELEMENT ACKNOWLEDGE_PO_008 (CNTROLAREA, DATAAREA+)>
    <!ATTLIST VERB
         value CDATA #FIXED "ACKNOWLEDGE"
    >
    <!ATTLIST NOUN
         value CDATA #FIXED "PO"
    >
    <!ATTLIST REVISION
         value CDATA #FIXED "008"
    >
    <!ELEMENT DATAAREA (ACKNOWLEDGE_PO)
    >
    <!ELEMENT ACKNOWLEDGE_PO (POORDERHDR, POORDERLIN*)
    >
    <!ELEMENT POORDERHDR ((%DATETIME.DOCUMENT;)?, (%OPERAMT.EXTENDED.T;)?, POID, POTYPE, ACKREQUEST?, CONTRACTB?, CONTRACTS?, DESCRIPTN?, NOTES*, OPRAMTAUTH?, PORELEASE?, TAXWHEXMPT?, USERAREA?, ACKHEADER, ATTCHREF*, CHARGE*, PARTNER*, POTERM*)
    >
    <!ELEMENT ACKHEADER (SENDER, (%DATETIME.PROMDELV;)?, (%DATETIME.PROMSHIP;)?, ACKCODE, DESCRIPTN?, NOTES*, SALESORDID?, USERAREA?)
    >
    <!ELEMENT POTERM (DESCRIPTN?, TERMID?, ((DAYOFMONTH, PROXMONTH) | DAYSNUM), ((%OPERAMT.EXTENDED.T;) | (%QUANTITY.PERCENT;)), USERAREA?)
    >
    <!ELEMENT POORDERLIN ((%QUANTITY.ORDERED;), (%DATETIME.NEEDDELV;)?, (%OPERAMT.UNIT.T;)?, POLINENUM, DRAWING?, HAZRDMATL?, ITEMRV?, ITEMRVX?, NOTES*, PACKING?, POLNSTATUS?, TAXWHEXMPT?, ((DESCRIPTN, ITEM?, ITEMX?, UPC?) | (ITEM, ITEMX?, UPC?) | (ITEMX, UPC?) | (UPC)), USERAREA?, ACKLINE*, ATTCHREF*, CHARGE*, DISTRIBUTN*, PARTNER*, POTERM*, POSUBLINE*, POLINESCHD*)
    >
    <!ELEMENT ACKLINE ((%DATETIME.PROMDELV;)?, (%DATETIME.PROMSHIP;)?, (%QUANTITY.ORDERED;)?, ACKCODE, NOTES*, SALESORDID?, USERAREA?)
    >
    <!ELEMENT POSUBLINE ((%QUANTITY.ITEM;), DRAWING?, ITEMRV?, ITEMRVX?, PSBLINENUM?, ((DESCRIPTN, ITEM?, ITEMX?, UPC?) | (ITEM, ITEMX?, UPC?) | (ITEMX, UPC?) | (UPC)), USERAREA?)>
    <!ELEMENT POLINESCHD ((%DATETIME.NEEDDELV;), (%QUANTITY.ORDERED;), DESCRIPTN?, PSCLINENUM?, USERAREA?)
    >
    Thanks,S
    --Sunil                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • BPM Error Permanent Error in BPE inbound processing

    Hi
    I require some urgent help on this BPM issue.
    We are trying to integrate SRM PO being directly sent to Vendors using HTTP. We are getting an error saying ‘Permanent Error in BPE inbound processing’. The scenario works like this.
    SRM system would sent PO using the SRM Standard interface PurchaseOrderRequest_Out. We need to transform the message into cXML format and send it to the vendors using HTTP adapter. Using the HTTP response we need to trigger an email to the business process team.
    The SRM interface is under the software component SAP SRM Server 5.5 and our mapping is being done in a common software component and for the vendor interface we have another software component. We have created a relationship in the SLD by making the common SWC as dependent software component to SAP SRM Server and Vendor Software Component. So in the integration repository we are able to get the interfaces for the SAP SRM Server and Vendor Software Component under the common software component. The receive step for this BPM is a copy of the standard SRM interface PurchaseOrderRequest_Out(as the standard interface is an asynchronous interface) and we would require an abstract interface for the BPM. We have checked the semantics for the BPM and its fine. The related ID development is in place. When the message is being triggered, it gives us this above mentioned error. When we go to the QRFC monitor we are able to check the details.
    Regards,
    Indranil

    Hi Indranil,
         You don't see you BPM....
    First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
    Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
    and check if any error is listed there.
    In order to check what is going on in your BPM you can trace it:
                      SXMB_MONI_BPE->Diagnosis Processes with Errors
                      SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
             Hope this helps you....
             Regards,
                Encinas.

  • Permenant error in bpm inbound processing error in inbound queue of pi7.1

    Hi Experts,
                 In  E filling scenario in SAPPI7.1, iam facing a problem. i.e In sxmb_moni message monitoring, the  message was schedule at outbound side.when i extend that, the message was stuck in smq2 with "permenant error in bpm inbound processing".can any one please tell me how to relove this issue.
    Thanks & Regards,
    Giri.

    Hello
    Check the note #1126656     BPE-TS: Permanent errors in the BPE inbound processing. This describes some possible causes and solutions for this error.
    Regards
    Mark

  • Permanent error in BPE inbound processing

    Hi all,
    We have recently migrated are XI scenarios to a new server.
    In one of the file to rfc scenario whenver a file is processed i get the error in smq2: Permanent error in BPE inbound processing.
    The chances of BPM and mapping error  are less as the BPM is working live in another server.
    What could be the other problems.
    REgards
    Edited by: Vinithra Iyangar on Feb 26, 2009 10:36 AM

    Dear Vinithra,
    Its highly improbable for this error to occur because of transports going wrong. There is one more case which i am sure is the cause why you are getting this error.
    "This behavior is when we place the files in the respective folders both the files are picked up by the file adapter. Process instance is generated for BPM. First receive step is encountered and the file is received by it. But due to the wait step the second receive step is not open and hence the second file cannot be delivered to it. Unlike the first case, in this case as the buffering is deactivated the file is not buffered and hence the inbound processing of BPM fails for the second receive step."
    Please check if something like this is happening.
    Refer : /people/milan.thaker/blog/2008/07/04/delivery-modes-in-bpm
    Rgds
    joel

  • Permanent error in BPE inbound processing for BPM Mesg Split

    Hi Friends,
    i have done the below scenario. i had done everything what theys mentioned in the blog but i am getting the error in smq2 as "Permanent error in BPE inbound processing" sysfail please helpme on this issue.
    Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure

    Hi Uday,
    Please check this blog for your error, This is really interesting. Permanent solution for your question.
    Delivery Modes in BPM.
    Thanks!

  • BPM workflow "In Process"-Queue "Permanent error in BPE inbound processing"

    Hi All,
    I am trying to collect messages from 2 different interfaces into BPM( Integration Process).
    when I checked in sxmb_moni  , i found the error on outbound status & BPM workflow has stuck with status  "In Process".
    it is not showing any error in Workflow, how to solve the issue.
    due to the above error, other messages are stuck in Queue stating "Permanent error in BPE inbound processing".
    Please help.
    -Jyoti

    Hi Jyoti,
    Goto T.Code swwl, in that clear all fields and choose from date as 1 month ago and try to execute. Then, delete all entries there. And re-execute your scenario.
    In this case, please see SAP Note 1126656.
    Please see the below blog, it might be helpful to you.
    /people/henrike.kaiser/blog/2009/02/03/how-to-analyze-stopped-queues-in-xi-ccbpm
    Regards,
    Rajesh

  • BPM: Permanent error in BPE inbound processing

    Hi guys...
    i am having a problem in my scenario which is involving BPM.
    The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing  error.
    yes..i searched on SDN and found resources like Note number 1126656
    i checked al the steps which were earlier mentioned posts like:
    SWWL:  there are no entries existing
    SMQ2: cleared the queues ,regenerated but still no luck.
    My undertsanding is no work is being generated at all .
    I checked BPM with F7 : its correct no errors
    BPM has return code of 0 in sxi_cache
    In ID BPM is latest and refreshed.
    Is there any way i can overcome this problem.
    Your inputs will be of real help.
    Thanks in advance.
    Regards,
    Kiran.

    My undertsanding is no work is being generated at all .
    If you are getting the error for Source ---> BPM  flow then there is a possibility that the ID objects (RD, Interface determination) are to be blamed.
    1) Recreate these particular ID objects/ make some dummy changes
    2) Activate and ensure that Cache is refreshed
    3) Delete the entry in the queue (or delete the queue)....do this only if the XI system is not of Quality, production
    4) some times the BPM cannot be triggered from sending a test message from RWB .... so make a testing from the source application .... this particular case has heppened to me and hence suggesting to you.
    Regards,
    Abhishek.

  • Permanent error in BPE inbound processing error

    Hi guys...
    i am having a problem in my scenario which is involving BPM.
    The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing error.
    yes..i searched on SDN and found resources like Note number 1126656
    i checked al the steps which were earlier mentioned posts like:
    SWWL: there are no entries existing
    SMQ2: cleared the queues ,regenerated but still no luck.
    My undertsanding is no work is being generated at all .
    I checked BPM with F7 : its correct no errors
    BPM has return code of 0 in sxi_cache
    In ID BPM is latest and refreshed.
    Is there any way i can overcome this problem.
    Your inputs will be of real help.
    Thanks in advance.
    Regards,
    Seshagiri.

    Hi Praveen,
    If the BPM goes in error due to "The incoming payload structure is incorrect (not matching message type structure of abstract interface)" , is there any work around?
    Currently in my scenario BPM goes into error due to incorrect structure , error show up in SMQ2 . And the subsequent message also get stuck. What I have to do is to delete the queue in error and reactivate the queue manually.
    Is there any way we can avoid this situation.
    Thanks,
    Pankaj

  • IDoc to Soap, with BPM - Permanent error in BPE inbound processing

    Hi Experts,
    IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
    How to rectify this any issue???
    Thanks-
    sk

    Hi,
    The inbound processing encountered a permanent error and the queue therefore stopped.
    The error message "Permanent error in BPE inbound processing" may be caused by the following:
    - At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
    Refer to the help in Note 1082099
    - The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
    Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
    Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
    Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
    - Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
    Hope this will help you.
    Regards
    Aashish Sinha
    PS : reward points if helpful.

  • ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing L

    Hi There,
    I am trying to load XML data [Given Below] into a table using "Load XML Data" option.
    <?xml version="1.0"?>
    <ROWSET>
    <ROW>
    <ID>13</ID>
    <TYPE_SEQ>8</TYPE_SEQ>
    <TYPE>B749</TYPE>
    <TYPE_DESC>B758</_TYPE_DESC>
    <EFFECTIVE_FROM>2099-01-01</EFFECTIVE_FROM>
    <EFFECTIVE_TO>2099-01-01</EFFECTIVE_TO>
    <CREATED_BY>958344</CREATED_BY>
    <CREATED_ON>2099-01-01</CREATED_ON>
    <UPDATED_BY>172283</UPDATED_BY>
    <UPDATED_ON>2099-01-01</UPDATED_ON>
    </ROW>
    </ROWSET>
    It throws the following error.
    ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00222: error received from SAX callback function
    Can any one advice the solution please.
    -Sudheer.

    Hi Sudheer,
    This is caused by the date format you are using. Probably it is not matching with your NLS settings. Check your NLS settings, what the date format is, and use that in the XML.
    Check it with this code:
    SELECT XMLELEMENT("date", sysdate) FROM dual;Make sure, you have your NLS_DATE settings in the same format.
    Check it with:
    SELECT * FROM v$nls_parameters WHERE parameter = 'NLS_DATE_FORMAT'And then make sure it is the same by setting for example:
      ALTER SESSION SET NLS_DATE_FORMAT = 'YYYY-MM-DD';Greetings,
    Rutger

  • ORA-19202: Error occurred in XML processing

    HI,
    I was preparing a support schema which is in synch with the production schema. For one of the UI i am getting the following error when the XML is too large.
    The same code is working in the production schema.
    I did a reconcilation and found the code sources are exactly the same.Pasting the debug lines below.Please help resolving the issue.
    gwpks_service_router.Getting the msg status for
    gwpks_service_router.Inside fn_get_msgstat
    gwpks_service_router.In wot of msg stat extraction: ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00225: end-element tag "REC" does not match start-element tag "FCUBS_BODY"
    Error at line 15697
    gwpks_service_router.l_msgstat:
    gwpks_service_router.Returning
    gwpks_service_router.l_msg_stat:
    gwpks_service_router.p_Process_Stat: S
    gwpks_service_router. fn_service_router return true
    gwpks_service_router.After fn_service_router, msgId:
    gwpks_service_router.Logging begins
    gwpks_service_router.Inside fn_populate_logs
    gwpks_service_router.Inside fn_get_msgstat
    gwpks_service_router.In wot of msg stat extraction: ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00225: end-element tag "REC" does not match start-element tag "FCUBS_BODY"
    Error at line 15697
    gwpks_service_router.l_msgstat:
    gwpks_service_router.Returning
    gwpks_service_router.Msg Status:
    gwpks_service_router.About to start the logging with MsgId:
    gwpks_service_router.fn_populate_logs returning true
    gwpks_service_router.MsgId:
    gwpks_service_router.SysMsgId:
    gwpks_service_router.MultitripId:
    gwpks_service_router.l_process_stat in pr_process_req_msg : S
    gwpks_service_router.GRAND SUCCESS CLOSING DEBUG
    gwpks_service_router.GRAND SUCCESS CLOSING DEBUG 1

    Hi,
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE     11.2.0.1.0     Production
    TNS for Linux: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production
    The code is very big.I prepared another schema on another database and the code is working.
    Then v$ version of the working schema is as below:
    Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    PL/SQL Release 11.2.0.2.0 - Production
    CORE     11.2.0.2.0     Production
    TNS for Linux: Version 11.2.0.2.0 - Production
    NLSRTL Version 11.2.0.2.0 - Production
    Still wonder why this works in the second schema but not the first one.

  • ORA-19202: Error occurred in XML processing  ORA-24333: zero iteration coun

    Hi,
    I have a procedure which craetes a sql v_sql dynamically
    IF v_cnt > 0 THEN
    For c1 in v_curr
    LOOP
    v_sql := ''''||'SELECT * from '|| c1.msg_rcrd_src_tbl_nm||' where rowid = '||''''||''''||c1.msg_rcrd_src_tbl_id||''''||''''||'''';
    select DBMS_XMLGEN.getXMLtype(v_sql) into v_xml from dual ;
    gives me a error
    ORA-19202: Error occurred in XML processing
    ORA-24333: zero iteration count
    ORA-06512: at "SYS.DBMS_XMLGEN", line 288
    ORA-06512: at line 1
    Any help greatly appreciated.
    Thanks,
    Raj

    Answered
    Re: Zero iteration error - when processing dynamic sql in dbms_xmlgen

  • Error while processing XML ; ORA-19202: Error occurred in XML processing

    We have an application, which sends an XML to DB for processing.
    While it works in general, it is failing, when special characters are present in the text node
    see example below
    <?xml version="1.0" encoding="UTF-8"?>
    <Query>
    <Group>
    <Value>  %</Value>
    </Group>
    </Query>
    Db throws following error while parsing this xml
    XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00217: invalid character 15573180 (U+EDA0BC)
    How to fix it?

    The following works for me on 11.2.0.2, db charset AL32UTF8 :
    test_sample.xml, encoding UTF-8 :
    <?xml version="1.0" encoding="UTF-8"?>
    <Query>
    <Group>
    <Value>?%</Value>
    </Group>
    </Query>NB : the characters behind the "?" got lost after posting, they're actually 0xF09F 8C82
    Loading...
    SQL> truncate table tmp_xml;
    Table truncated
    SQL>
    SQL> insert into tmp_xml values (
      2   xmltype(
      3     bfilename('TEST_DIR','test_special.xml')
      4   , nls_charset_id('AL32UTF8')
      5   )
      6  );
    1 row inserted
    SQL> set long 500
    SQL> select * from tmp_xml;
    SYS_NC_ROWINFO$
    <?xml version="1.0" encoding="UTF-8"?>
    <Query>
      <Group>
        <Value>🌂%</Value>
      </Group>
    </Query>
    Edited by: odie_63 on 25 sept. 2012 23:00

  • EDI :  inbound processing error.

    Hi All,
    I am facing the below error
    "Entry in inbound table not found" status 56.
    I am setting a new EDI inbound interface for goods reciept GR:
    We have got a flat file which we are trying to upload from SAP directory.
    after uploading i am getting the above error. The error points at Partner Profile details stating the details doesnot exist. But i cross checked and its all correct.
    - Partner Profile created.
    - Message type exixt in INBOUND Parameters.
    If i reprocess this failed idoc using we19 selecting INbound function module "L_IDOC_INPUT_WMMBXY" then it gets processed successfully.
    If i reprocess this failed idoc via editing and then running report RBDINPUT for processing edited idoc status 69, then the probelm persist.
    I dont know what i am missing.
    Thanks in advance.

    Hi,
    I am getting the same error.
    Can u please help me on this.
    Thanks and Regards
    Neha Kapoor

Maybe you are looking for