Error handling / logging with asynchronous calls

Hi,
I want to log every error my app might throw. I thought it would be sufficient to surround either the launch method or the start method with a try...catch. But it doesn't work as excepted.
If an error occurs in an asynchronous call, e.g. in a button click, the exception is never caught.
Do you have an idea, how to solve this?
Example:
import javafx.application.Application;
import javafx.event.ActionEvent;
import javafx.event.EventHandler;
import javafx.scene.Scene;
import javafx.scene.control.Button;
import javafx.scene.layout.VBox;
import javafx.stage.Stage;
public class TestApp4 extends Application {
    public static void main(String[] args) {
        launch(args);
    public void start(final Stage stage) throws Exception {
        try {
            final VBox root = new VBox();
            Button button = new Button("Click");
            button.setOnAction(new EventHandler<ActionEvent>() {
                @Override
                public void handle(ActionEvent actionEvent) {
                    int i = 0;
                    int a = 5 / i;
            root.getChildren().add(button);
            Scene scene = new Scene(root);
            stage.setScene(scene);
            stage.show();
        } catch (Exception e) {
            // do logging here
            e.printStackTrace();
}

I'm not 100% sure how it works, but what I am pretty sure is that these Exceptions in EventHandlers are caught by JavaFX itself inside the JavaFX thread. They have to, because if they let the exception bubble up to the top, the FX thread would end (and with it, all response in the UI). It is probably caught at the level where Events are triggered somewhere (my guess is inside the QuantumToolKit).
Anyway, these exceptions are printed to System.err -- if you can redirect that stream to a log file or whatever you can have them all in one place. The error stream can be set in your application simply by calling System.setErr().
Note also that exceptions occuring in a Task are stored in the exception property -- sometimes these can be hard to find as they are put there silently -- you'll need to check your Tasks for exceptions and print them.

Similar Messages

  • Error handling, logging and monitoring business process

    I would like to know more about error handling, logging and monitoring in business process? Can someone give more information on this one?

    Chandran
    Please refer to following tutorials to understand each of these topics in detail:
    Validations:
    http://www.orafmwschool.com/validations/
    Exception Handling:
    http://www.orafmwschool.com/exception-handling/
    Fault Management Tutorial:
    http://www.orafmwschool.com/fault-management-tutorial/
    Business Activity Monitoring Tutorial:
    http://www.orafmwschool.com/bam-tutorial/
    You'll have to refer to Oracle documentation to understand more finer details.
    -Amjad.

  • Unexpected loop behaviour with asynchronous call

    I am having trouble with loop behaviour when using an asynchronous call.
    I am building an application to record simultaneously temperature (NI USB-TC01 thermocouple), displacement (DC voltage, read from an Agilent 34401a) and resistivity (using a Keithley 2400 sourcemeter).
    I am using a voltage sweep function on the Keithley 2400 to alternate current direction in a sample and measure the voltage drop - this is a common technique for eliminating thermal emf from resistance measurements. But what you need to know is that I set the number of current cycles I want and then wait for the instrument to measure and return the meausurements - up to 50 samples, which takes nearly 30 seconds. With the other two measurements, I have to programmatically call a measurement vi for each sample I want.
    I have set up my application to asynchronously program the resistivity measurement and then wait for the response, and I want to in parallel measure temperature and position until the resistivity is done. I then want to record the mean and standard deviation for each signal. I used an event structure to interrupt the temperature and position measurements when done.
    The problem I am running into is that after the first resistivity measurement is completed and I go to do the second one, the loop that measures temperature and displacement only runs twice, so I only get two samples, regardless of how many resistivity samples I want to collect. For example, if I want 50 resistivity samples at a time, the first iteration will measure rougly 40 samples of temperature and displacement, but any subsequent iterations will only measure twice.
    I know this is probably overwhelming to understand the operation, but can anyone help? I have attached my code ('Delatometer') as well as a test vi I built that uses the same structure but has no interactions with instruments ('asynchronousCall').
    The
    Attachments:
    Delatometer.zip ‏221 KB
    asynchronousCall.zip ‏29 KB

    I forgot to mention...the test vi that I uploaded executes as expected, so I am thinking that maybe its an issue with the instrument calls? I also found that if I run the Delatometer program in 'highligh execution mode' it runs properly, and it is my understanding that in 'highlight execution mode' there is no multi-threading.

  • ColdFusion.Ajax.submitForm error handler problem with AppleWebKit-based browsers

    All-
    When using an AppleWebKit-based browser (i.e. Safari or
    Chrome), the
    message argument of the Coldfusion.Ajax.submitForm error
    handler always contains the string "OK", regardless of what error
    was cfthrown by my CFM form handler.
    Recall that the signature for the error handler is this:
    MyFormErrorHandler = function( code, message )
    In other browsers (i.e. IE or Firefox), the
    message argument of the error handler properly contains the
    message that was cfthrown by my form handler.
    Can anyone offer any guidance for this problem? Thanks in
    advance for your help.
    -Josh

    I was testing on IE8, Windows7 Starter.  I don't have IE6 available to test on.  Can test on IE7 a bit later on, but I have to fart-arse around with a VM to get it ready, so I'll do that after work.
    I tested multiple submits both via clicking between the tabs within one main "request" as well as multiple entire requests (like via refreshing the whole browser window).  I had no problems.
    I think you're being quite optimistic ot expect AJAX stuff to work reliably on IE6.  IE6 crashes.  That's what it's most famous for doing.  One needs to expect crashes if one pushes it (push it anywhere than out the window, that is).  And your client company's IT dept should be lined up against a wall and shot for still running it.  That's professionally negligent IMO.  But... you probably don't need to be told that.
    Adam

  • Error handling problem with outbound idoc status 02 and  XML HTTP Port

    I set up an ALE scenario to send master data out of SAP via an XML HTTP port.  All goes well until the idoc receives error 02. 
    It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques.  Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
    Is there any solution to still use the standard ALE error handling ?

    Hi Karin,
    Looks like based on note 701597, you can only reprocess these idocs manually via a workitem.  I qouted the relevant text below:
    3. Error handling with status '02':
    An HTTP IDoc in status '02' should not automatically be sent once again.
    Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
    However, this report was adjusted and now deletes all IDocs in status 02
    to be routed to a HTTP port from the list of selected IDocs. IDocs to a
    HTTP port in status '02' should only be sent manually via a work item.
    Regards:
    Rex

  • Using AIA for Error Handling. Logging and Notification Services

    hi,
    In our project we usie OSB and BPEL for integrating different applications.
    There is a suggestion that we should use AIA to just use the Error Handling, Logging and Notification services from AIA. I am not sure about this use case, as most of these services mentioned can be replicated in BPEL. Except for the AIAAsyncExceptionHandling BPEL process, i guess all other functionalties provided by AIA can be easily developed in BPEL or OSB alone.
    However, would like to hear from you guys about this particular use case. Is it advisable?

    Hi,
    It's an issue with 10.1.3.4 OBIEE. (whem using IBM LDAP)
    References
    BUG:7363517 - INTERNAL BI FAILURE ON STARTUP
    They issue can be resolved by setting LD_PRELOAD=/path/libibmldap.so
    Here are the steps:
    . sa-init.sh
    export LD_PRELOAD=/path/libibmldap.so

  • Forward Error Handling - File interfaces?

    Hello Experts,
    Can we use Forward Error Handling (FEH) for implementing error handling in File Interfaces ?
    Like for simple Application Server file interfaces, if something goes wrong during the process of writing/reading a file on App Server, can we use FEH for showing the log?
    I know it is a concept used for PI...so we want to know if it can be used for file interfaces as well? Just want to keep similar approach for error handling and logging (for both PI and File Interfaces).
    Thanks.

    Edit 1 May 2015: Added inbound
    Just a slight correction.
    FEH is used in the ABAP backend systems and are only for asynchronous inbound proxy interfaces. It is not available for sync proxies, IDocs, BAPIs. Neither is it available for any error handling on the PI system itself.
    PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
    Message was edited by: Eng Swee Yeoh

  • How to activate Forward Error Handling in SRM

    Hello Gurus,
    I got an requirement to activate Forward Error Handling in SRM. I have searched on SDN but didn't find appropriate answer on it.
    Even I found some link: PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
    It explains me some points like activating FEH from SRM in SPRO. I have activated the same, plz check the screen shot:
    It also follows some development for the same.
    Here my concern is, should I follow this document? Does it applicable to all to all the scenarios?
    Step 8: it assign object id and type what does it mean...
    Does any one can explain me in detail..... Please provide me any document to configure the FEH in SRM.
    I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
    My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
    I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
    I have made some configurations like:
    The view FEHV_ACTIVE must have the status active.
    In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
    As stated in in the link :
    http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
    Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
    Resulted, the “Process” button get activated in the XML Post Processing screen.
    But can I reprocess my XML with edited value from there..?
    All the  configuration part of PI  is already done .
    I wanted to know  about the  FEH  Part. what are the  steps   i am  missing  or where  i am  going  wrong ?
    Please let me help.
    Thanks
    Regards
    Karan

    Dear Raz,
    I have gone with above mentioned note, it explains about creating Custom Proxy and configuration with PI scenario. Even the link in my previous post, explains about the custom proxies and configuration..
    I think I should must be descriptive about my issue.
    I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
    My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
    I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
    I have made some configurations like:
    The view FEHV_ACTIVE must have the status active.
    In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
    As stated in in the link :
    http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
    Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
    Resulted, the “Process” button get activated in the XML Post Processing screen.
    But can I reprocess my XML with edited value from there..?
    Can any one tell me, what are the steps I am missing here. As this is my first time to implement FEH, I am confused.
    Please let me help.
    Regards,
    Chandan

  • Teststand New Thread VS LabVIEW "Call & Forget" Asynchronous call

    Hi everyone,
    Here is an example taken from the ni.com website showing how to use LabVIEW to post a TestStand Notifier.  I have modified the example to fit the situation I needed to use it for.  I have an example which works fine (When I use a TestStand new thread to launch the Notifier VI) and an example which does not work (When I use a LabVIEW "Call & Forget" Asynchronous call to launch the Notifier VI).
    I would like to understand why it doesn't work in the second situation. The reason why I would prefer the 2nd situation which currently doesn't work is that I try to eliminate all multi-threads from an obsolete sequence written by someone else a few years ago so that I can troublesoot it and update the code to make it work with today's new reality.
    Also, for my personal knowledge.  I don't understand why the second strategy doesn't work.  The Testsand notifier reference is the same and hadled the same way.  I have included my example files with the 2 situations in seperate sequences files.
    Thanks in advance to the person who will be able to enlight me.
    Nien 
    Solved!
    Go to Solution.
    Attachments:
    New Thread Or Dynamic Call.zip ‏41 KB

    Hello Nien,
    This isn't a TestStand issue.  I suggest you take this to the LabVIEW forum.  Looking over your code your Notifer and Forget.vi is dependent on the notifier.vi.  So it's not necessarily anything wrong with the sequence steps but actually within your LabVIEW code itself.  One suggestion is to insert a simple error handler.vi in your Call Notifier and Forget.vi.  You have error wires connected to the functions itself, which is good practice but you don't have anything to inform you if an error occurs or not.  I would suggest you to run try to debug your LabVIEW code, such as using highlight execution, while you're running your code so you know where exactly the error is happening.  
    Thanks,
    Jonathan R.
    Applications Engineer
    National Instruments

  • Writing an error handler package

    I want to standardize on an error handling package, with a record type declared that is anchored to a table. Some obvious attributes I can think of for the table are the following:
    1. Time stamp
    2. The package that threw the error
    3. The method that threw the error
    4. Any textual content written by the programmer that invoked the package. Perhaps that could be a concatenation of relevant fields with a delimiter for example.
    5. The severity of the error. For example, it could be 'fatal' i.e. can't move any more, 'severe' i.e. threw out junk but leaves the result table with too little content to be practical etc.
    6. The author who wrote the code.
    My questions are:
    (i) In the experience of seasoned writers of libraries in this forum, are there other significant fields (and enumerated values of error types) that you capture, independent of the domain that you are writing this for?
    (ii) Is there an analog of argv[0] of the C language in PL/SQL that provides the package (and method)? names? this way, I can proof against the careless programmer mis-typing.
    (iii) Apart from writing to the db table and perhaps sending e-mail, are there any significant methods to this package that have escaped my admittedly cursory analysis?
    (iv) I am thinking of making it refuse to accept null values for the fields which would force the invoker to populate them when he or she throws an exception. Are there any other things I should force?
    Thanks,
    Srini

    Firstly this is not "error handling" it is logging. They are two different things.
    Secondly, before you go any further down this road I recommend you check out log4plsql. This does quite a lot of what you want and a whole lot more besides. It is not perfect (I discuss some of its shortcomings here but it is a very good starting point.
    Some specifics:
    6. The author who wrote the code.If you know the PACKAGE/METHOD names and you know the version of the software deployed in that environment surely your software version control software will tell you this info?
    ii) Is there an analog of argv[0] of the C language in PL/SQL that provides the package (and method)? names?No. Unfortunately PL/SQL lacks this sort of refection, it would be very useful. One tactic is to expand the logging to include INFO and DEBUG levels, which can be turned off (log4plsql does this). Then the developer gets some benefit from the logging package and that is an incentive to get the names right. Another approach is to use an IDE (such as TextPad) that supports clip libraries; include your logger registration call in the templates for PACKAGE, PROCEDURE and FUNCTION.
    (iii) Apart from writing to the db table and perhaps sending e-mail, are there any significant methods to this package that have escaped my admittedly cursory analysis?Syslog. It is then industry standard. Some people like files.
    (iv) I am thinking of making it refuse to accept null values for the fields which would force the invoker to populate themI think it is an important principle that logging should be as robust as possible - we don't want a gnarly exception thrown because the logging package failed to handle a trivial issue.
    You will get the maximum uptake of your logging package if its API is easy to use and developers can see ready benefits from making it work. Again, DEBUG is the key here: all you need do is make it easier to use your package than typing (and removing!) DBMS_OUTPUT.PUT_LINE calls.
    Cheers, APC

  • Can error handling framework use fault policies and BPEL catch blocks

    As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
    The problem we have experienced in our design is as follows:
    •     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
    •     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
    •     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
    The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
    It seems the two mechanisms "cannot play nicely together"

    As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
    The problem we have experienced in our design is as follows:
    •     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
    •     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
    •     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
    The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
    It seems the two mechanisms "cannot play nicely together"

  • Dml error handling in 10g

    i have a procedure with an insert statement that is using the new oracle 10g dml error handling LOG ERRORS INTO err$_dest ('INSERT') REJECT LIMIT UNLIMITED;
    i understand this will execute when you have a violation like not null columns etc.
    according to oracle website, this command will fail if there is a space problem and everything will roll back. will i get an error message in such scenario and can i use regular exception handling to handle this.
    example code
    begin
    insert into dest values(1, 'smith', 1234, 'dest')
    LOG ERRORS INTO err$_dest ('INSERT') REJECT LIMIT UNLIMITED;
    exception when others
    //login error cause by log errors command
    end;

    The inserts into the err$_dest table will NOT be rolled back as they are autonomous transactions. We were able to handle other errors such as tablespace sizing issues in the exception section.

  • General Error Handling - use of FEH (PPO/ECH)

    We are investigating the usage of Forward Error Handling, known with SAP as PPO (Post Processing) and ECH (Error Capture Handler) to be able to re-process errors (automatically or manually) from incoming messages.
    I am interested in talking with anyone who has implemented this. General questions are:
    - how have you found it to work in real life?
    - configuration/set-up straight-forward?
    - what scenarios have used it in?
    - incorporated into your custom services?
    But am interested in any comments.
    I am posting this within the PI forum as it ties into the fact we async scenarios inbound to SAP, typically from our PI system, and when those scenarios encounter an error we are looking for a way to have a business/end user - friendly interface for reprocessing the error. Implementing a proxy scenario, and thus having the errors show within sxmb_moni/sxi_monitor, is probably not going to work for us - too technical.  I am also aware of an add-on, AIF I believe, but our company is not interested in installing that.
    There are 4 blogs out there that I am aware of - 2 from Tobias and 2 from Michal. Very informative.  I am finding some config not as ours though.  Am really interested in anyone has really implemented and used this in a prod environment.
    Regards,
    Keith

    I think I am exactly at the same position as you in figuring out the usage of FEH in an environment. I just completed a small document (for internal purpose) that I prepared gathering all the information from those blogs, SCN and TechEd. Here are my 2 cents:
    >>- how have you found it to work in real life?
    We haven't implemented it yet. But we believe it will be quite useful in handling business specific errors. We are trying to find out if it can be merged with the existing BPEM infrastructure to generate BPEM cases.
    >>- configuration/set-up straight-forward?
    Yes, the blogs should be quite useful to provide this information.
    >>- what scenarios have used it in?
    Most importantly it will be used for standard service implementation where we consume enterprise services from ES workplace. These services have FEH capability built in (they have FEH method implemented within). The scenarios are of course inbound abap proxy.
    >>- incorporated into your custom services?
    We are still in design phase. But if you ask me about it, i would say yes you can and I think you should use it for custom ones as well.
    Kind regards,
    Prateek Raj Srivastava

  • Asynchronous Call Back Fault Handling through Mediator with Resequencer at Component Level

    Hello,
    As a part of an existing code extension we are introducing set of changes to the code to support new scenarios. The following are the composites involved in the end to end flow:
    1- Consumer_Mediator: A mediator composite with Resequencer enabled at the component level (With fault policy as human intervention in case of failure).
    2- BusinessServiceRouter_Mediator: A mediator composite - typical EBS in AIA - which routes messages to the provider components in BPEL and receive response in Synchronous pattern.
    3- BusinessServiceProvider_BPEL: A BPEL Process that is responsible for interacting with external Application and Provide return success response or throw failures to the EBS.
    Synchronous Interaction
    Typical Request Scenario is as follows:
    [Resequencer] ------------Consume------> [Consumer_Mediator] ----------Sync------> [BusinessServiceRouter_Mediator] -------------Sync---------->[BusinessServiceProvider_BPEL]
    1- First Message in the resequencer group is picked up.
    2- Mediator route the message to BusinessServiceRouter Route message and waits for the response.
    3- BusinessServiceRouter routes the message to the BusinessServiceProvider_BPEL Process and wait for response.
    4- BusinessServiceProvider_BPEL process makes successeful call to the External Application Service and is prepared to return Successful response.
    Typeical Response:
    Through a Synchronous flow, all instances are waiting for the response to commit the transaction, once the response comes back and routed back to the Consumer_Mediator one of two cases happen:
    1- Success: instance is Complete, and the next message in the resequencer group is processed.
    2- Failure: instance is marked as recovery needed and the next messages in the resequencer group are held off till the first message is recovered or aborted.
    New Requirement - Asynchronous Interaction
    A new Application Service is introduced and it can take up to 6/8 hours to process the request. Which means we need to change the interaction to Asynchronous request and Callback with the Provider long running BPEL Process that will interact with the BPEL process.
    Request in the new Code:
    [Resequencer] ------------Consume------> [Consumer_Mediator] ----------Sync------> [BusinessServiceRouter_Mediator] -------------Async--------->[BusinessServiceProvider_BPEL]
    Response in the new Code:
    1- Success: There is absolutely no issue here, it works fine and all instances are marked as complete.
    2- Failure in BusinessServiceProvider_BPEL. This is mainly the issue. When there is a failure that this BPEL process wants to throw. The following happens:
              -  BusinessServiceProvider_BPEL instance is marked as failure.
              - BusinessServiceRouter_Mediator instance is marked as failure.
              - Consumer_Mediator instance is marked as complete and the next message in the resequencer group gets processed - which is the main issue.
    Any Help or suggestion is much appreciated. Thanks.

    1. You can update the message payload when 'recovering' the faulted mediator instance for msg2 in EM console. So if it's a data issue, fix/update the data at the source, and do not trigger the service; instead, update the payload in the recovery page in EM console as needed and retry. This will be a manual activity only. I don't think there is any other easy approach/option/configuration available for this.
    2. Not sure if there is a direct option to automatically process suspended messages in a timed-out group once the missing message arrives. It needs a manual intervention where you 'Skip' to unlock the group from time-out and process further message. I think there are Resequencer APIs available that probably can be used to automate such error handling/recovery.

  • LV7.1 Strange behavior with Automatic Error Handling occuring when it shouldn't [LV 7.1 Pro on WinXP for Tablet PC's]

    [LV 7.1 Pro on WinXP for Tablet PC's]
    I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File.  I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
    Subsequent investigation revealed:
    Neither AEH option in Options>Block Diagrams were checked.
    Network problems had occurred around the time that the app had hung.  All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
    My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled.  The error out cluster of New File in my subvi is wired.
    My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled.  Nor does any of their calling VI's.  All three instances also have their error out cluster wired.
    A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true.  That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
    As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions.  As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
    In other words I can find no reason why I should have gotten the problem AEH dialog...
    I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
    Any ideas?

    Very good.
    Write Characters to File.vi>Open/Create/Replace File.vi>New File
    New File throws the error.  Open/Create/Replace strips the hierarchy from the source of the error.  Write Characters passes it to the General Error Handler.  I never looked above O/C/R file in the hierarchy except for enable automatic error handling property.  The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that. 
    The real irony is that Write Characters was being used to log error cluster data to an error log file...
    Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
    Thanx (a bunch)

Maybe you are looking for

  • Repair Management Scenario

    Hi MM Gurus.. Have a business scenario I hope someone can help me blueprint. The scenario is to basically to just “manage” the repair process with OEMs (or one of several major airlines) being the “Customer” and all real work being done by subcontrac

  • FAQ: Why is Photoshop Elements cheaper? What's different about Photoshop?

    What is Photoshop CS/CC (PSCS/PSCC)? Photoshop is a professional tool used throughout many industries as the standard for digital image manipulation and painting. It has very rich, and often complex, tools and options. As such, it comes with a profes

  • When new record instance trigger at Fire Enter Query event is throwing erro

    HI I have the following code on when new record instance which is set to fire at Enter Query Mode IF :SYSTEM.BLOCK_STATUS <> 'QUERY' THEN rec_num:=Get_Block_Property( 'MASTER', CURRENT_RECORD); GO_ITEM('DETAIL.ITEM_NAME'); CLEAR_BLOCK(NO_VALIDATE); G

  • Reinstalling Adobe Acrobat 9.5.5?

    I have recently removed Adobe Acrobat 9.5.5. from my second computer.  I did not deactivate it. I have the following questions: - How do I re-install Adobe Acrobat 9.5.5?  I still have the Serial Number from my other computer, if this helps. Once ins

  • Final Cut Express - Aspect Ratio

    Where do I set the aspect ratio in Final Cut Express? I find that often I import 4:3 clips, and FCE wants me to work with them in a 16:9 Sequence, so I get letter boxing. Sometimes, FCE seems smart enough and says "hey should I fix this", but sometim