Terminating Event Generate an Error

Hi All.
My custom workflow has asynchronous task where the terminating events trigger from ABAP program and passed some data.
This task will completed upon custom event "ACCEPTED" raised in the system based on certain keyfield and continue next steps.
Terminating events tab contains element WIOBJECT_ID and my custom event "ACCEPTED".
Binding is use standard element Binding details as per standards, &_EVT_CREATOR& --> &INITIATOR and &_EVT_OBJECT& --> &_WI_OBJECT_ID&
I though this is the only step that I need to do and of course wait step.
However when I test this terminating event via SWUE with proper object key, event trace transaction reported event "ACCEPTED" for task TS95000052 not defined as start/end event.
I check in instance linkage transaction, linkage is activated for my object type, "ACCEPTED" and receiver type "WORK ITEM".
Event type linkages between event and my asynchronous task also active.
Will someone give me a clue, what should I do to resolve this issue?
Many Thanks

You cannot exit from a for loop until it is done. Use a while loop instead. Also, using the event structure in this case causes all kinds of exit problems. Try it and you will see what I mean. Instead, use the abort button itself. Put a case statement at the end to give the error output if the abort button was pressed. See attached vi.
- tbob
Inventor of the WORM Global
Attachments:
abortTesting.vi ‏45 KB

Similar Messages

  • Workflow runtime error because of terminating event

    Hi all,
    In one of the workflow template, in one step, the Standard Task is having Terminating Event.
    At the runtime, at the particular step, when it was in process, the terminating event is triggered. The step got completed,
    But the workflow is not proceeding.
    When I viewed the workflow log, In the perticular step after receiving the terminating event, the follwoing error is shown
    " Workitem XXXXXX is locked by the user YYY(Enqueue error)".
    The workitem number mentioned in the error is parent workitem number, not one of the particular step.
    I know that there is a setting in SWU3 to schedule a job for errored out workitems. That job is already scheduled and it has tried two times and it stopped.
    Now do I have to restart the workflow again or the issue can be resolved in the workitem in progress.
    Thanks,
    Sarayoodharan.K

    the terminating event is triggered. The step got completed,
    But the workflow is not proceeding.
    When I viewed the workflow log, In the perticular step after receiving the terminating event, the follwoing error is shown
    " Workitem XXXXXX is locked by the user YYY(Enqueue error)".
    Can you please let us know how you are trying to trigger the terminating event,I mean are you trying to trigger the terminating Programatically, then you might be using a FM to rasie the terminating event, by looking at the error it is clear that the event is triggered and the workitem got completed but the lock on the workitem is not released , you can release it by using the COMMIT WORK statement
    You have to write the commit work statement after raising the even or make sure that someor the other way the commit work is executed, this is beacuse once the commit work statement is executed all Locks are released..

  • Terminating Event to Event Queue due to Work Item Lock

    I have a dialog workflow task based on an asynchronous method defined with a terminating event.  When the user executes the work item, the method generates the terminating event (via a V2 change document) but the work item is enqueued (locked) by the same user (locked when they execute the work item from SBWP) and therefore the terminating event goes into error and is placed in the event queue.  The background job which processes the event queue does not redeliver the event so it stays in the event queue and the work item fails to complete.  Other than dequeing the work item lock myself with a function call how do I get around this catch 22?

    Hello Martin,
    Actually, the locking happens whether I have the task as asynchronous or synchronous.  The problem is the timing. If the user does not release the lock (by backing out of the dialog which is executed) prior to the terminating event attempting to enqueue and complete the work item then the event goes into error and is inserted into the event queue (and lingers there indefinitely, almost). Another issue with the asynchronous approach is that even if the user backs out of the dialog before the event actually attempts to complete the work item they will still see the work item in the inbox unless they click the refresh button when they get back to the inbox. 
    I have changed the task to synchronous but here is my scenario and another question.
    The process being workflowed is the approval of service entrysheets (similar to an invoice if you are not familiar with External Services).  In our process, there are a large number of documents being created and requiring approval by particular approvers.  It is a normal scenario for an approver to have, lets say 25 documents in his inbox awaiting approval. It was not practical for him to have to navigate back and forth between his inbox and the approval task screen.  Therefore, I give the users the option of (when executing a work item) having all the documents in his in-box (for this particular task) be presented in an approval list screen.  They can then do a mass approval of the 25 documents with 1 click and 1 navigation.  This list screen is also available to be executed outside workflow via a tcode.  So, when the user executes the mass approval (either from the inbox or outside workflow) the work items are terminated via the terminating event assigned to the approval task.
    A couple of issues remaining:
    1) Given my example of 25 work items (user executes 1 work item from in-box
    and I displayed all 25) being approved, when the user returns to the in-box, the 24
    items remain in his inbox until he clicks the refresh button since these were not actually "executed" from the workflow engines point of view.  However, these were terminated successfully because they were not "locked".
    <b>Question:</b> Is there a way (user exit?) to trigger the inbox refresh automatically.
    2) Now, the issue with the actual work item which the user executes from the inbox.  As I mentioned, the work item is locked as soon as the user executes it and is not released until they back out of the dialog or logoff.  So, here is what happens:  If the terminating event is sent before the lock is released the event is sent to the event queue.  If they then back out back to the in-box, its OK since I put some code in the SWO1 object type program (rememeber, its now synchronous) which will determine if they did the approval/rejection and the work item will complete and the event in the event queue will be deleted the next time the Event Queue Background job runs (it deletes any events for work items already in COMPLETED status). However, lets say they simply log off rather than backing up to the in-box or they don't do anything and are eventually logged off by timeout. In this case the code in the object type program to determine if the approval/rejection was done does not get executed (control does not return to the object type program) and the work item remains in "STARTED" status and remains in the users inbox and the event is in the event queue. So, now we have a work item that should be completed still sitting in the users in-box and the terminating event in the event queue. So the next time the user goes to their inbox the work item is still there.  The interesting thing is that though this may be confusing to the user, if they then attempt to execute the work item, they will get a message: "Work item currently being completed by event" (Message SWF_RUN 644) and the event sitting in the event queue gets redelivered and completes the work item.  To alleviate this problem I was thinking of adding a call to SAP_WAPI_WORKITEM_COMPLETE in the approval list screen after they do the approval but I'm guessing it wont work since it probably will try to enqueue the work item and it will still be locked. 
    Hopefully you haven't nodded off reading this rambling note...
    Thank you,
    Bob

  • [EJB:010112] - error with WLI8.1 Event Generator for foreign JMS/MQ provider

    I'm getting following error in weblogic server log when starting a JMS Event generator
    to a foreign JMS(MQ5.3) Queue.
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect
    every 10 seconds. This log message will repeat every 600 seconds until the condi
    tion clears.>
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. The Error was:
    [EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted, but the pro
    vider defined in the EJB is not transacted. Provider should be transacted if onM
    essage method in MDB is transacted.>
    My WLI8.1.2 is patched with CR131686_812.zip to support event generator for foreign
    JMS destinations. The foreign JMS/MQ provider is configured properly. QueueSend/Receive
    were tested fine with JMS java code using local JNDI names of foreign JMS objects.
    So we know that foreign Queue is active and accessiable from webLogic.
    Anyone run into this? Solution?
    Thanks,
    Scott

    Hi Scott,
    I need a transaction from the MDB since I am not using an EJb to pursue the action.
    Hence I need to retain the <trans-attribute>Required</trans-attribute> at the
    MDB.
    Have any answers?
    Pradip
    "Scott Yen" <[email protected]> wrote:
    >
    It's resolved.
    The MDB automatically created by JMS Event Generator defaults to be deployed
    with
    “transacted”. That requires the foreign JMS provider to be “XA”.
    The deployment descriptor is created as <domain-directory>/WLIJmsEG_<event_gen_name>.jar
    e.g. C:\bea812\user_projects\domains\jmsInterop\WLIJmsEG_mqQueueEventGen.jar
    Since MQ in the localhost and remote SLUDV18 are not XA-enabled, we had
    to manually
    change the <container-transaction> section in ejb-jar.xml:
    From :
    <trans-attribute>Required</trans-attribute>
    To:
    <trans-attribute>NotSupported</trans-attribute>
    "Scott Yen" <[email protected]> wrote:
    I'm getting following error in weblogic server log when starting a JMS
    Event generator
    to a foreign JMS(MQ5.3) Queue.
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. Connection failed after 2 attempts. The MDB will attempt to
    reconnect
    every 10 seconds. This log message will repeat every 600 seconds until
    the condi
    tion clears.>
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. The Error was:
    [EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted,
    but the pro
    vider defined in the EJB is not transacted. Provider should be transacted
    if onM
    essage method in MDB is transacted.>
    My WLI8.1.2 is patched with CR131686_812.zip to support event generator
    for foreign
    JMS destinations. The foreign JMS/MQ provider is configured properly.
    QueueSend/Receive
    were tested fine with JMS java code using local JNDI names of foreign
    JMS objects.
    So we know that foreign Queue is active and accessiable from webLogic.
    Anyone run into this? Solution?
    Thanks,
    Scott

  • Email Event Generator - Error

    Hi,
    I am facing a problem in reading the email and its attachments. Basically I get excel attachments from a third party and some message in the body of the mail. I need to read the email body in the jpd ( process ) and archive the attachments of the mail in a location . To achieve this I use the email event generator to archive the attachments and to call a process to read the body of the mail.
    Steps I followed -
    1. Created a mail account with my name on the mail server.
    2. Created a new email event genertor with all the required parameters in WLI console. configurations being
    Server Protocol POP3
    Channel Name /EmailEventProcess/SampleStringChannel
    Hostname ABC.ENERGY.LOCAL
    Port Number 25
    Username TestSS
    Password ********
    Attachments Archive
    Polling Interval 1 min
    Read Limit 10
    Post Read Action Archive
    Archive Directory C:\Cache
    Error Directory C:\Cache
    Description
    Publish As weblogic
    3. created a channel in the project in weblogic workshop -
    <channel name ="SampleStringChannel" messageType="string" qualifiedMetadataType="eg:EmailEventGenerator"/>
    4. In a process project - took the option
    subscribe to a message broker channel and start via an event (through email)..
    code :
    * @jpd:mb-static-subscription message-metadata="{x1}" channel-name="/EmailEventProcess/SampleStringChannel" message-body="{x0}"
    public void subscription(java.lang.String x0, com.bea.wli.eventGenerator.EmailEventGeneratorDocument x1)
    //#START: CODE GENERATED - PROTECTED SECTION - you can safely add code above this comment in this method. #//
    // input transform
    // parameter assignment
    this.testString = x0;
    this.testEmailEG = x1;
    //#END : CODE GENERATED - PROTECTED SECTION - you can safely add code below this comment in this method. #//
    I tried printing out the testString , but i get some strange error.. below is the error -
    <Jan 22, 2010 12:19:50 PM CET> <Error> <WLI-Core> <BEA-489203> <Error while publishing message: com.bea.wli.mbconnector.email.EmailConnMDB$EmailConnectorException: connect to store failed>
    I checked the mail box , when i send test mails , I can see the mails in the inbox..
    Can anyone help me to overcome this error /
    thanks

    access issues..

  • Email event generator - error publishing emails received from browser

    Hi,
    Configured an email event generator that listens on a mailbox. The message type is set to string and no filters. All emails sent from outlook is published successfully to message broker channel and the subscribed by a process. Whereas for emails sent from any browser email like yahoo, gmail gives "Null pointer exception - cannot publish message". Anybody have encountered this error?
    Also is it possible to configure the email event generator to archive the emails to another folder in the mailbox rather than to a physical directory?
    -Manjula.

    access issues..

  • E-mail event generator errors

    We've done many different channels and not had many problems however, we've been
    experiencing problems when creating Email event generators that publish on a message
    broker channel and there's not a decent example in the documentation.
    The errors are listed in the attached file along with the contents of our channel
    definition file. The encoding error happens no matter how the e-mail is encoded.
    Has anybody seen this error? How was it resolved? An example would be helpful
    too!
    [email_channel_errors.txt]

    Hi Sean,
    The channel definition specifies through the ' messageType="xml" ' attribute that
    the message body is well-formed xml. Based on this I created an Email Event Generator
    that publishes to that channel (I used your channel definition). I sent four types
    of messages. Type 1 was a message with no body at all. Type 2 was a message with
    a random text body. Type 3 was a message with a malformed xml body. Type 4 was
    a message with a proper xml body. The results indicate that the error message
    you are seeing is due to a message being published that has no body at all (Type
    1 in my test).
    Type 1 - message with no message body content: BINGO!
    <Mar 24, 2004 10:49:24 PM PST> <Error> <WLI-Core> <BEA-489203> <Error while publishing
    message: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create
    process variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException:
    Can't read XML (no root element)>
    Type2: Random text body:
    "<Mar 24, 2004 10:50:54 PM PST> <Error> <WLI-Core> <BEA-489203> <Error while publishing
    message: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create
    process variable: com.bea.xml.XmlException: error: Unexpected element: CDATA>
    Type 3: Malformed xml body:
    <Mar 24, 2004 10:58:26 PM PST> <Error> <WLI-Core> <BEA-489203> <Error while publ
    ishing message: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can'
    t create process variable: weblogic.xml.stream.XMLStreamException: '>' expected
    [?! -- [CDATA[ ] - with nested exception: [weblogic.xml.stream.XMLStreamException:
    '>' expected [?! -- [CDATA[ ] - with nested exception: [Error at line:1 col:10
    '>' expected [/?! -- [CDATA[ ]]]>
    Type 4: well-formed XML message body
    ...No error message!...
    If there actually was a message body please post it and I'll give it a go.
    Hope this helps!
    Steve Waterhouse
    BEA WorldWide Technical Training
    "Sean McGillen" <[email protected]> wrote:
    >
    >
    >
    We've done many different channels and not had many problems however,
    we've been
    experiencing problems when creating Email event generators that publish
    on a message
    broker channel and there's not a decent example in the documentation.
    The errors are listed in the attached file along with the contents of
    our channel
    definition file. The encoding error happens no matter how the e-mail
    is encoded.
    Has anybody seen this error? How was it resolved? An example would
    be helpful
    too!

  • Use abap class event as terminating event

    Hi,
       The class is say ZCL_WF_CLASS and the event  END_WF.
    What needs to be done to have this event used correctly as a terminating event of a workflow? Does this event require a parameter to hold the workitem id (or workflow id), as currently this event has no parameters?
    Previous developer has developed the class and event and installed as a terminating event but the workflow is going into error not terminating correctly. I believe the incorrect development of the event and/or its use in the workflow is the issue. Note that nowhere is this event currently raised in any code of the workflow.
    Cheers,
    Ross

    Hello,
    Unless I'm mistaken, a terminating event for a workflow is just like any wait-for event in a workflow.
    It can be based on any object or class and it can be used in various ways - to terminate a branch or terminate the workflow, for example.
    The workflow listens out for the event and checks if there is a matching key. You could base it on the key of a workflow object but it makes more sense to base it on an object or class that's used in the workflow - e.g. the POSTED event of an object would be used to terminate a workflow seeking approval for the posting of an object.
    It definitely won't work if the event has no parameters. I guess if you do base it on the workflow object then you would use the top-level workitem id. Try it with a test workflow and SWUE to generate the event.
    regards
    Rick Bakker
    hanabi technology

  • Event ID: 10830 errors in our RMS server.

    Hi
    We are getting Every hour 6 to 7 Event ID: 10830 errors in our RMS server. Help us to resolve this issue.
    Event Type:    Error
    Event Source:    Health Service Modules
    Event Category:    None
    Event ID:    10830
    Date:        10/27/2011
    Time:        4:08:05 AM
    User:        N/A
    Computer:    IND-APP142
    Description:
    An alert couldn't be inserted to the database. This could have happened because  of one of the following reasons:
         - Alert is stale. The alert is generated by an MP recently deleted.
         - Database connectivity problems or database running out of space.
         - Alert received is not valid.
     The following details should help to further diagnose:
     Details: RuleId:8654b44b-a532-3e3a-19be-1d4a66e9f790. HealthServiceId:e840b3ad-86d3-d373-1970-4c8b39f171c2. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager",
    table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
    The statement has been terminated.RuleId:8654b44b-a532-3e3a-19be-1d4a66e9f790. HealthServiceId:e840b3ad-86d3-d373-1970-4c8b39f171c2. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database
    "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
    The statement has been terminated.RuleId:8654b44b-a532-3e3a-19be-1d4a66e9f790. HealthServiceId:e840b3ad-86d3-d373-1970-4c8b39f171c2. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database
    "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
    The statement has been terminated.RuleId:8654b44b-a532-3e3a-19be-1d4a66e9f790. HealthServiceId:e840b3ad-86d3-d373-1970-4c8b39f171c2. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database
    "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.
    The statement has been terminated..
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Regards Donald D'souza http://donald-scom.blogspot.com/

    Hi
    I am able to find out from which agent this error is causingby the below command
    get-monitoringobject -id HealthServiceId
    I have followed the below steps to resolve the ssue
    1. Stopped the Health service
    2. Deleted the Health Service State Folder
    3. Started the Health service
    Still the issue was not fixed.  This error is coming from a Domain controller. The agent pointing to the gateway server so i have followed the same above steps on the gateway server but still the issue not resolved.  Then I have restarted the SDK,
    Config and Health Service on the RMS server but still I am getting the error.
    Help us on this.
    Regards Donald D'souza http://donald-scom.blogspot.com/

  • The Lync Server Front-End service terminated with service-specific error %%-1008124893.

    Hello, everyone
    I've installed Lync Server 2010. There was no error during installation. But when i start Lync Server Front End Server, i'm getting following error:
    The Lync Server Front-End service terminated with service-specific error %%-1008124893.
    In event viewer:
    The evaluation period for Microsoft Lync Server 2010  has expired. Please upgrade from the evaluation version to the fully licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
    Cause: The evaluation period for Microsoft Lync Server 2010  has expired.
    I've upgraded Lync Server according to http://technet.microsoft.com/en-us/library/gg521005.aspx?ppud=4
    Also I've installed all Lync Server updates.
    But I still could not start Lync Front End Sever. How can I solve this problem?
    Thanks

    Hi,
    Can you try to run
    start-cswindowsservice -report c:\report.html
    and post the report so we can have more information about your problem ?
    Regards,
    Adrian TUPPER - ABC Systemes - http://thelyncexperience.blog.com/ If answer is helpful, please hit the green arrow on the left, or mark as answer Thank you

  • Copy of task TS50000075 and  EXTSRV - termination event not working

    Hi,
    We have done copy of TS50000075 and extended business object EXTSRV to ZEXTSRV
    this was done to call function module ISR_CALL_FOR_CHANGE to open up adobe form in edit mode
    it works well but the task is not terminated
    if termination event is put just like TS50000075 like WIOBJECT, ZEXTSRV COMPLETED then workitem never ends and always stays in inbox
    ZEXTSRV COMPLETED event is not triggered when the workitem is completed in the UWL
    even if we trigger this event programatically , it does not find receiver and the task stays in-process
    if termination event is put as _WORKITEM PROCESSED then it bahves like synchronous task ie even if the workitem is clicked and form is not completed, the workitem ends. so the user can click it only once
    also i've tried following
    1 - used the function module to complete the workitem in QISR BADI. but the workitem ID is not available inthe BADI. If I try to export it from business object method and import in BADI, it doesnt work
    2 - find active workflows and derive workitem id and complete workitem using FM SAP_WAPI_WORKITEM_COMPLETE
         this FM doesnt work , step becomes logically deleted which is not desirable
    3 - find active workflows and derive workitem id and complete workitem using other FM SAP_WAPI_SET_WORKITEM_COMPLETD
         work item is complete but there is workflow error - cannot determine succesor node
    4 - find active workflows and derive workitem id and change a particular container element
        check this container element in complete workitem condition in activity step of dialog step of workflow of this task-
         workitem stays inprocess
        check this container element in parellel wait step to complete the workitem-
         parellel step executes but fork is not complete, workflow doesnt proceed
    kindly help in this matter. the workitem does not get completed at all even if we force complete, workflow goes in error of - cannot determine succesor node.
    is there anything specific to the EXTSRV-PROCESS method which makes the TS50000075 task to trigger EXTSRV-COMPLETED and end the workitem ?
    help is much needed in this case
    thank you,
    b

    Hi,
    You need to see the event in SWEL, otherwise it will never work with workflow. Make sure that the event monitor is on (in transaction SWELS).
    I cant see the event in SWEL. The vent monitor is on because if I create event in SWUE, it shows up.
    How you actually create the event now?
    There is BADI QISR which is always called to handle user action of PDF form. I have written the function modue to create event in the user action
    >If i trigger it using funciton module -- then it doesnt find any receivere so it doesnt terminate the task. it is seen in SWEL with no receiver found. do i still need to do commit work ?
    You need the COMMIT WORK always if you trigger the event in any program&function or whatever.
    ok ill try doing commit work after the create event function module
    Test your event with transaction SWUE. Make a test case first in a way that the task is waiting in the inbox/UWL. Then create the event in SWUE. Now, if the task gets completed, you will know that that event itself is working and your terminating event configuration is done properly. If this works, your only problem is in the event creation itself. And for that you need to tell exactly how you create the event. If you do it with your own custom code, use SAP_WAPI_CREATE_EVENT and don't forget to have COMMIT WORK after the function call.
    I am doing exactly like you said. but it doesnt work ie even if I create the event in SWUE, the workitem doesnt get completed.
    This event is seen in SWEL with no receivere found
    I am able to infact set the workitem to complete using WAPI funciton module to complete teh task in the BADI.
    but the workflow goes in to error saying , next node cannot be determined
    Regards,
    Karri

  • RDBMS Event Generator Issue - JDBC Result Set Already Closed

    All -
    I am having a problem with an RDBMS event generator that has been exposed by our Load Testing. It seems that after the database is under load I get the following exception trace:
    <Aug 7, 2007 4:33:06 PM EDT> <Info> <EJB> <BEA-010213> <Message-Driven EJB: PollerMDB_SessionRqt_1186515408009's transaction was rolledback. The transact ion details are: Xid=BEA1-7F8C65474500D80A5B94(218826722),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],numRepli esOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_Affinity_cgJMSStore_auto_1]=(ServerResourceInfo[JMS_Affi    nity_cgJMSStore_auto_1]=(state=rolledback,assigned=wli_int_1),xar=JMS_Affinity_cgJMSStore_auto_1,re-Registered = false),XAServerResourceInfo[ACS.Telcordi    a.XA.Pool]=(ServerResourceInfo[ACS.Telcordia.XA.Pool]=(state=rolledback,assigned=wli_int_1),xar=ACS.Telcordia.XA.Pool,re-Registered = false),XAServerReso urceInfo[JMS_Affinity_cgJMSStore_auto_2]=(ServerResourceInfo[JMS_Affinity_cgJMSStore_auto_2]=(state=rolledback,assigned=wli_int_2),xar=null,re-Registered = false),SCInfo[wli_int_domain+wli_int_2]=(state=rolledback),SCInfo[wli_int_domain+wli_int_1]=(state=rolledback),properties=({START_AND_END_THREAD_EQUAL    =false}),local properties=({weblogic.jdbc.jta.ACS.Telcordia.XA.Pool=weblogic.jdbc.wrapper.TxInfo@d0b2687}),OwnerTransactionManager=ServerTM[ServerCoordin    atorDescriptor=(CoordinatorURL=wli_int_1+128.241.233.85:8101+wli_int_domain+t3+, XAResources={weblogic.jdbc.wrapper.JTSXAResourceImpl, Affinity_cgPool, J    MS_Affinity_cgJMSStore_auto_1, ACSDispatcherCP_XA, ACS.Dispatcher.RDBMS.Pool, ACS.Telcordia.XA.Pool},NonXAResources={})],CoordinatorURL=wli_int_1+128.241 .233.85:8101+wli_int_domain+t3+).>
    <Aug 7, 2007 4:33:06 PM EDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
    javax.ejb.EJBException: Error occurred while processing message received by this MDB. This MDB instance will be discarded after cleanup; nested exceptio n is: java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages.
    javax.ejb.EJBException: Error occurred while processing message received by this MDB. This MDB instance will be discarded after cleanup; nested exception is: java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages
    java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages
    at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.fetchUsingResultSet(RDBMSIntrusiveQryMDB.java:561)
    at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.onMessage(RDBMSIntrusiveQryMDB.java:310)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2523)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: java.sql.SQLException: Result set already closed
    at weblogic.jdbc.wrapper.ResultSet.checkResultSet(ResultSet.java:105)
    at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:67)
    at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next()Z(Unknown Source)
    at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.handleResultSet(RDBMSIntrusiveQryMDB.java:611)
    at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.fetchUsingResultSet(RDBMSIntrusiveQryMDB.java:514)
    ... 8 more
    javax.ejb.EJBException: Error occurred while processing message received by this MDB. This MDB instance will be discarded after cleanup; nested exception is: java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages
    at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.onMessage(RDBMSIntrusiveQryMDB.java:346)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2523)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    >
    I have tried several things and had my team do research but we have not been able to find an answer to the problem.
    If anyone can offer any insight as to why we might be getting this error it would be greatly appreciated. Thanks!

    i also have same error during load testing, mainly this error
    "Unexpected exception while enlisting XAConnection java.sql.SQLException"
    i tried rerunning after increasing connection pool sizes, transaction timeout, but no luck, marginal improvement in performance though
    also tried changing the default tracking levl to none, but no luck.
    i am with 8.1SP5, how about you ?
    do share if you are able to bypass these errors
    cheers

  • Generate an error message that Adobe Reader 8 or later is required

    Afternoon all,
    I have created a form (in Acrobat 10 Pro) with a lot of scripts and we have determined that they do not all work as desired in Adobe Reader 7 and earlier.
    Is there a way to generate an error message if a user opens this form with Adobe 7 or earlier?
    We would like a message to pop up advising the user that Adobe 8 or later is required for this form.
    It does not have to lock them out or anything, we just want to advise them.
    Thanks much,
    Steve

    Thanks,
    This is how my bosses want this done. For one part, some of the functionality we are using just doesn't exist in Reader prior to version 8. For others, the users don't really have an option to go elsewhere.
    As for thescript, i am not sure how to apply it. Where do i access the initial page's open event?
    I do know how to enter document level scripts (this form has several) but what does "outside of a function definition" mean and how do i do that?
    Thanks everyone,
    steve

  • Terminating event -- No active receiver found

    Hi -- on an Integration project I just need a workitem that stays active until explicitly closed via an event..
    It's easy enough to create a triggering event which starts a process.
    I've followed all the rules (as far as I can see) to create a terminating event but it doesn't work.
    I've created a test Bus Obj ZZJIMBO which simply has a key of the SAP user ID.
    I've defined 3 events
    STARTSYN  ====> Synchronous
    STARTASY  =====> Asynchronous
    FINISHED ======>  terminating
    Using SAP_WAPI_CREATE_EVENT the STARTSYN and STARTASY  are triggered and the relevant processes start - both for the synchronous and asynchronous tasks.
    However on raising the FINISHED event the system just errors with NO Active receiver found.
    All the binding etc is fine and SWU0 doesn't find any problems.
    Looking at the instance table (transaction SWE3)
    I see that the eventid is the same as the current workitem but the object key is empty
    object key  <empty> 
    eventid    000000250100
    The only possibility I can see is that my Business object doesn't really have "instances" like say a sales order as it only exists at run time.
    Would I have to say trigger the event finished using something like the Work item itself which does have a valid individual instance -- I can extend the WORKITEM bus obj and add an event FINISHED to it instead.
    I can get the workitem id via the container so that shouldn't in theory be a problem to "instantiate"  the Workitem (or ZWORKITEM) business object.
    I really hoped to have all the events in the SAME business object however.
    Any ideas
    Cheers
    jimbo

    Hi James.
    1. Yes, I think the workitem in runtime would expect the triggering event should be from the instance of the object either from
            a. standard workitem relevant obejct instances like _WORKITEM, ATTACHOBJECTS, RULERESULT
           b. or the associated BO in the task i.e WIOBJECT_ID
    2. However as you say >>I really hoped to have all the events in the SAME business object however>>. I can suggest the following
           a. create a parallel fork to the step which is creating your workitem
           b. In this parallel branch create step 'Wait for Event; and refer it to your ZZJIMBO.FINISHED.
          c. define necessary branches required to complete the fork as 1. meaning, if any one of the branch ends flow will continue to next step in main workflow.
    So, when the event ZZJIMBO.FINISHED is raised with the correct instance which was used in workflow. 'Wait for event' will receive it and this branch will end and eventually other branch will get logically deleted. You can put some flag in the 'Wait for event' branch using which u can understand whether the workitem is completed in normal way or through exeption.
    Hope this helps !!
    Regards
    Krishna Mohan

  • NWDS is generating IndexedStore Errors when I do reload +rebuild

    Hi All,
    I am working on a Java Webdynpro application in NWDS V7.0.13 with Eclipse 2.1.2. When I am trying to RELOAD + REBUILD NWDS is generating some errors which are not source code related.
    I would like to know why I am getting those errors whenever I rebuild my project. And if I go to the Project Explorer and do DC rebuild and refresh sometimes the errors are gone after 7 to 8 rebuilds.
    I would appreciate if I get any help here as I am working on a critical project.
    The error log shows below errors:
    Error Wed Apr 02 19:25:53 CDT 2008 Apr 2, 2008 7:25:53 PM    com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse  [Thread[ModalContext,5,main]] Error: Refresh of resource C:/Documents and Settings/mkosuri/.dtc/0/DCs/deloitte.com/home/enrolment/_comp/gen_wdp/packages/com/deloitte/component/enrollment/OpenEnrollmentComponent.java fails (org.eclipse.core.internal.resources.ResourceException: Indexed store transactions did not commit properly: C:\Documents and Settings\mkosuri\Documents\SAP\workspace\.metadata\.plugins\org.eclipse.core.resources\.projects\NWP_ESSTRK4_Dhomeenrolment~deloitte.com\.properties.)
    org.eclipse.core.internal.resources.ResourceException(C:/Documents and Settings/mkosuri/Documents/SAP/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/NWP_ESSTRK4_Dhomeenrolment~deloitte.com/.properties)[272]: IndexedStoreException:Error committing the indexed store.
    org.eclipse.core.internal.indexing.ObjectStoreException: Cannot store page in page store.
         at org.eclipse.core.internal.indexing.IndexedStore.commit(IndexedStore.java:139)
         at org.eclipse.core.internal.properties.IndexedStoreWrapper.commit(IndexedStoreWrapper.java:86)
         at org.eclipse.core.internal.properties.PropertyStore.commit(PropertyStore.java:449)
         at org.eclipse.core.internal.properties.PropertyManager.setProperty(PropertyManager.java:173)
         at org.eclipse.core.internal.resources.Resource.setPersistentProperty(Resource.java:1190)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceNew(GenerationEclipse.java:1344)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.access$1000(GenerationEclipse.java:76)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse$11.run(GenerationEclipse.java:1386)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceInBatch(GenerationEclipse.java:1391)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:268)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:307)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visitComponent(GenerationVisitor.java:297)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visit(GenerationVisitor.java:127)
         at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:106)
         at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:50)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:76)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:119)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:60)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:82)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationBuilder.build(GenerationBuilder.java:99)
         at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:427)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:125)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:181)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:191)
         at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:151)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:165)
         at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:265)
         at org.eclipse.core.internal.resources.Project.build(Project.java:85)
         at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:156)
         at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:122)
         at org.eclipse.ui.actions.WorkspaceAction$1.execute(WorkspaceAction.java:279)
         at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
    org.eclipse.core.internal.indexing.ObjectStoreException: Cannot store page in page store.
         at org.eclipse.core.internal.indexing.ObjectStore.commit(ObjectStore.java:183)
         at org.eclipse.core.internal.indexing.IndexedStore.commit(IndexedStore.java:137)
         at org.eclipse.core.internal.properties.IndexedStoreWrapper.commit(IndexedStoreWrapper.java:86)
         at org.eclipse.core.internal.properties.PropertyStore.commit(PropertyStore.java:449)
         at org.eclipse.core.internal.properties.PropertyManager.setProperty(PropertyManager.java:173)
         at org.eclipse.core.internal.resources.Resource.setPersistentProperty(Resource.java:1190)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceNew(GenerationEclipse.java:1344)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.access$1000(GenerationEclipse.java:76)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse$11.run(GenerationEclipse.java:1386)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceInBatch(GenerationEclipse.java:1391)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:268)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:307)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visitComponent(GenerationVisitor.java:297)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visit(GenerationVisitor.java:127)
         at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:106)
         at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:50)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:76)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:119)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:60)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:82)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationBuilder.build(GenerationBuilder.java:99)
         at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:427)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:125)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:181)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:191)
         at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:151)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:165)
         at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:265)
         at org.eclipse.core.internal.resources.Project.build(Project.java:85)
         at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:156)
         at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:122)
         at org.eclipse.ui.actions.WorkspaceAction$1.execute(WorkspaceAction.java:279)
         at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
    org.eclipse.core.internal.indexing.PageStoreException: Error occurred opening transaction log file.
         at org.eclipse.core.internal.indexing.LogWriter.open(LogWriter.java:39)
         at org.eclipse.core.internal.indexing.LogWriter.putModifiedPages(LogWriter.java:26)
         at org.eclipse.core.internal.indexing.PageStore.commit(PageStore.java:209)
         at org.eclipse.core.internal.indexing.ObjectStore.commit(ObjectStore.java:181)
         at org.eclipse.core.internal.indexing.IndexedStore.commit(IndexedStore.java:137)
         at org.eclipse.core.internal.properties.IndexedStoreWrapper.commit(IndexedStoreWrapper.java:86)
         at org.eclipse.core.internal.properties.PropertyStore.commit(PropertyStore.java:449)
         at org.eclipse.core.internal.properties.PropertyManager.setProperty(PropertyManager.java:173)
         at org.eclipse.core.internal.resources.Resource.setPersistentProperty(Resource.java:1190)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceNew(GenerationEclipse.java:1344)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.access$1000(GenerationEclipse.java:76)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse$11.run(GenerationEclipse.java:1386)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceInBatch(GenerationEclipse.java:1391)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:268)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:307)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visitComponent(GenerationVisitor.java:297)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visit(GenerationVisitor.java:127)
         at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:106)
         at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:50)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:76)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:119)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:60)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:82)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationBuilder.build(GenerationBuilder.java:99)
         at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:427)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:125)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:181)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:191)
         at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:151)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:165)
         at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:265)
         at org.eclipse.core.internal.resources.Project.build(Project.java:85)
         at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:156)
         at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:122)
         at org.eclipse.ui.actions.WorkspaceAction$1.execute(WorkspaceAction.java:279)
         at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
    java.io.FileNotFoundException: C:\Documents and Settings\mkosuri\Documents\SAP\workspace\.metadata\.plugins\org.eclipse.core.resources\.projects\NWP_ESSTRK4_Dhomeenrolment~deloitte.com\.properties.log (Access is denied)
         at java.io.FileOutputStream.open(Native Method)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
         at org.eclipse.core.internal.indexing.LogWriter.open(LogWriter.java:37)
         at org.eclipse.core.internal.indexing.LogWriter.putModifiedPages(LogWriter.java:26)
         at org.eclipse.core.internal.indexing.PageStore.commit(PageStore.java:209)
         at org.eclipse.core.internal.indexing.ObjectStore.commit(ObjectStore.java:181)
         at org.eclipse.core.internal.indexing.IndexedStore.commit(IndexedStore.java:137)
         at org.eclipse.core.internal.properties.IndexedStoreWrapper.commit(IndexedStoreWrapper.java:86)
         at org.eclipse.core.internal.properties.PropertyStore.commit(PropertyStore.java:449)
         at org.eclipse.core.internal.properties.PropertyManager.setProperty(PropertyManager.java:173)
         at org.eclipse.core.internal.resources.Resource.setPersistentProperty(Resource.java:1190)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceNew(GenerationEclipse.java:1344)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.access$1000(GenerationEclipse.java:76)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse$11.run(GenerationEclipse.java:1386)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.refreshResourceInBatch(GenerationEclipse.java:1391)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:268)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse.generatePersistentComponent(GenerationEclipse.java:307)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visitComponent(GenerationVisitor.java:297)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationVisitor.visit(GenerationVisitor.java:127)
         at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:106)
         at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:50)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:76)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:80)
         at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:119)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:60)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104)
         at org.eclipse.core.internal.resources.Resource.accept(Resource.java:82)
         at com.sap.ide.webdynpro.generation.eclipse.GenerationBuilder.build(GenerationBuilder.java:99)
         at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:427)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:125)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:181)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:191)
         at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:151)
         at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
         at org.eclipse.core.runtime.Platform.run(Platform.java:413)
         at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:165)
         at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:265)
         at org.eclipse.core.internal.resources.Project.build(Project.java:85)
         at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:156)
         at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:122)
         at org.eclipse.ui.actions.WorkspaceAction$1.execute(WorkspaceAction.java:279)
         at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
    Thanks for your time and consideration!
    Madhavi

    Solution:
    http://jira.pentaho.com/browse/BISERVER-5282
    Short Fix using find und sed:
    http://jira.pentaho.com/browse/BISERVER-5282?focusedCommentId=91528&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_91528

Maybe you are looking for

  • How to import Oracle .dmp file

    Hi ! 1. I want to import oracle .dmp file in to mySql database. 2. How it is possible. 3. I am using oracle 10g database. Plz help me. Thanks in advance. Regards.

  • MSS PCR form in german in production system

    Hi gurus, We are having a problem with the PCR Change Employee group and sub group. The adobe forms is coming out in English in both Development and Quality.But in production it's comin in german.We haven't changed anything in the form.But when we ch

  • Monitoring process chains: authorizations

    Hi, We have an issue about monitoring of BW process chains. We have a support desk in our IT department doing first-level support on basically all our it systems. The support desk have only limited SAP knowledge (they can do simple things like unlock

  • Off Topic: Business questions to business owners

    Sorry if this shouldn't be here (feel free to delete or let me know). Just thought you may be a good group to ask advice of. Looking for a new business bank account (preferably that ties into my personal accounts) and health insurance (for business).

  • ORA-39095: Dump file space has been exhausted

    Hello Friends, DB Version : 10.2.0.4 OS : SUN Solaris 10 We have a server with 10 RAC databases running on it. From 1st node we have a scheduled export job for all the databases. All the databases are using a common script and we are passing paramete