Event callback engine error

I modified the TS 4.0 HMI to where it has a button (in the execution view) that launches (adobe acrobat) a summary .pdf report.  This is not really a callback question, but more of a what am I doing wrong question.  In the attached bitmap, (please pardon the mess, but I kept trying stuff to isolate the problem and didn't clean up)  this callback is called when the user clicks the "LaunchReport" button in the Execution View.  It currently is called when a MouseUp event happens with this button, but that was just an attempt to find the real problem.  Anyway, I've disabled the troublesome code.  If I hard-code a path to a pdf, the button click causes that pdf to open up in adobe. 
What I need to do, however, is get the sequenceContext so that I can get to a FileGlobal containing the report path and pass that in instead.  I cannot seem to set a breakpoint in this code to find where the error is.  All I know is that if I enable the code, adobe never comes up.  I thought it was possibly in my GetFileGlobal VI, so I commented him out still the same behavior.  In the final code, I'd like to route the reportpath found in fileglobal upto the LaunchExternalViewer 'FilePath' input. 
As experiments, I kept the hard coded value there, but I tried wiring the Engine reference to the GetUIMessage Node, etc - with and without my GetFileGlobal VI, the code just does nothing.  I'm wondering if there's anything obviously wrong here. 
Attachments:
launchReport.PNG ‏40 KB

Hi,
Are you sure your FileGlobals is valid ie its available when you are trying to read it?
As an experiment have you tried using the StationGlobals, if you can get it from there, then  at least you know the mechanism works.
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

  • Event Callback from a Reentrant VI Recursion Error

    Greetings,
    I am using Register Event Callback with an ActiveX object to respond to user mouse events. The problem is that when I run the VI (the main, calling vi) as reentrant, Labview gives an error that the "Callback.vi" is attempting to recursively call "Main.vi".
    Is there a way around this problem? I intend to run two copies of "Main.vi", so reentrant execution seems necessary.
    - Colin Holbrook

    Hi Colin,
    Are you placing the Register Event Callback inside of the Main VI and then wiring the same Main VI to the VI Reference terminal?  If so, then that explains why you are getting an error.  You cannot use the Register Event Callback to call a VI within itself.  If this is not the case, then please post a simple VI that demonstrates the problem. 

  • Executable and Register event callbacks

    Hi,
    I have been running into an issue regarding the building of an executable that has register event callbacks (specifically Test Stand Callbacks).  The VI that is responsible for setting up the event registration is an asynchronous VI.  During development everything works but during deployment of an executable the Callback is either not running or capturing the event from the Test Stand engine (I am looking for the end of execution event).  The setup is not reporting an error, and the pathing to the callback VIs is correct.  Any Ideas on this?
    Does the Teststand engine not post a endexecution callback when running from a executable labview environment?
    Thanks,
    Andrew
     

    akonecki wrote:
    Hi,
    I have been running into an issue regarding the building of an executable that has register event callbacks (specifically Test Stand Callbacks).  The VI that is responsible for setting up the event registration is an asynchronous VI.  During development everything works but during deployment of an executable the Callback is either not running or capturing the event from the Test Stand engine (I am looking for the end of execution event).  The setup is not reporting an error, and the pathing to the callback VIs is correct.  Any Ideas on this?
    Does the Teststand engine not post a endexecution callback when running from a executable labview environment?
    Thanks,
    Andrew
    The TestStand engine is singular regardless of what is hosting the components so it will post the appropriate callbacks. Try some tracing and see what flags up in your callback VI.

  • NI Variable Engine:Error:

    I have a systemthat has been running fine for over a year. Upon failure the customer returned the processor to us and I took it to a known working unit to see what was going on with it.
    First thing, in MAX you cannot see anything under Devices and Interfaces, only thing that shows up is Software.
    I connected a monitor and keyboard to the PXI directly and the following errors are displayed (no way of doing a screen shot so I caught as much as I could):
    tStatus2 Contents:
                  Error code = -2147220721
                  Component Name = nidevldp
                  File Name = p:\Measurements\Infrastructure\devld\trunk\1.8source\mxsCon
    figWrapper.cpp
                 Line # = 103
                 Address of StatusDesc = 0x0
                 Stack Trace = 0x1F6EB46
                                       0x2167730
                                       0x216BFC3
                                       [and a bunch more]
    NI Variable Engine: Error: Unable to load the MXS conf plugin: Failed to get MAX Configuration Interface: 0x80004005
    NI Variable Engine: C:\ni-rt\system\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected error: Unable to get the interface from plug-in
    Nothing has changed on the system in over a year so I know it is not software. One day it just would not start running the machine.
    The processor is a (now obsolete) PXI-8184.
    Any clues or do I have to replace it, which will be fun because the newer PXI-8183 is a different size.
    Thanks for any input.

    This is a fairly common problem, in my experience. We use PXI RT controllers for several test stands, and I have found that the MAX Configuration database is quite easily corrupted if the controller is powered down without closing and cleaning up all the DAQmx tasks. I have no idea why an embedded system would be so easily corrupted, but here are the steps I have taken to deal with the (inevitable) corruptions:
    I created a "Shutdown RT System" button accessible via a remote front panel from my Host PC that will trigger an interrupt to stop all DAQ tasks and loops on the RT system. I make sure that any time the system needs to be powered down/rebooted, that the operator first presses this button to put the controller into a safe-to-shutdown state.
    I used the RTSystemReplication toolset to create a backup image of the RT controller HDD on my host PC. I created a separate compiled executable that I configured in Windows scheduler to create weekly backups of the RT controller. I have another application that redeploys the backup in the event of a database corruption. Note that the RT controller must first be completely formatted before the backup image can be applied.
    It is very frustrating that such a procedure is necessary (and it is necessary--even with uninterruptible power supplies, we still have the occasional power outage that outlasts the backup battery, not to mention oops situations where the system is restarted without stopping all DAQmx tasks). But by taking the steps listed above, I have managed to reduce the downtime associated with these gross system failures to roughly one hour per incident, as opposed to the 4+ hours it used to take to fully reinstall all the software components and recalibrate channels as necessary.
    If anyone else has any other ideas as to how to avoid/deal with MAX configuration corruptions on PXI RT controllers, please respond with descriptions.

  • Active x and event callback in Labview

    I have an active x written by Aanderaa Instruments (makes
    weather and hydrology sensors), it contain various methods and events to get
    the next line of records from a sensory scanning unit. The connection is
    through the COM1, so far i have wired it up only using the methods to get next
    record level, but then I have found that sometimes it does not get the complete
    record from the COM port. So to solve that I have to use an event in the active
    x to check for new record available. So what I want to do is send the event
    (when complete record available) to VI that uses the get next record method to
    pick up the data from the COM1 port and then send the data back to the main VI
    for processing, plotting and writing.
    My problem is that when I connect the output from the GetNextRecord method to a
    indicator that I then wire on the connector pane to be an output from this
    VI  get an error that there is a wire function conflict. I have tried to
    explain a bit better in the attached pdf file with diagrams.
    The reason why I want to export the data back in the main VI is because it runs
    continuously collecting data every 2 min and I plot them on a graph and write
    them to a file so it will no work to have all that done in the event callback
    VI that will only run ever 2 min, then it will reset the graph the whole time
    and I want continuous data plotting for 10 days of historic data records. I
    also have a few other sensors that come in through a connector board that are
    written o the same file.
    hope somebody can give me some hints
    Attachments:
    labview question.pdf ‏721 KB

    Duplicate post, click here for the original: http://forums.ni.com/ni/board/message?board.id=170&message.id=135639#M135639
    LabVIEW Champion . Do more with less code and in less time .

  • Event callback with active x in labview

    I have an active x written by Aanderaa Instruments (makes
    weather and hydrology sensors), it contain various methods and events to get
    the next line of records from a sensory scanning unit. The connection is
    through the COM1, so far i have wired it up only using the methods to get next
    record level, but then I have found that sometimes it does not get the complete
    record from the COM port. So to solve that I have to use an event in the active
    x to check for new record available. So what I want to do is send the event
    (when complete record available) to VI that uses the get next record method to
    pick up the data from the COM1 port and then send the data back to the main VI
    for processing, plotting and writing.
    My problem is that when I connect the output from the GetNextRecord method to a
    indicator that I then wire on the connector pane to be an output from this
    VI  get an error that there is a wire function conflict. I have tried to
    explain a bit better in the attached pdf file with diagrams.
    The reason why I want to export the data back in the main VI is because it runs
    continuously collecting data every 2 min and I plot them on a graph and write
    them to a file so it will no work to have all that done in the event callback
    VI that will only run ever 2 min, then it will reset the graph the whole time
    and I want continuous data plotting for 10 days of historic data records. I
    also have a few other sensors that come in through a connector board that are
    written o the same file.
    hope somebody can give me some hints 
    Attachments:
    labview question.pdf ‏721 KB

    Hello!
    I checked the PDF file with snippets of your code and it looks alright, no issues or comments regarding that from my side. However it is really difficult for us to troubleshoot when we don’t have the ActiveX control available and even though we had access to the control it would still be quite tricky to find the cause of the problems you are experiencing since we don’t have the hardware and so on.
    I found one link only that mentioned wire conflicts when talking about COM objects and ActiveX and you can find it here:
    http://digital.ni.com/public.nsf/websearch/0CED780​C5D5EDCD5862569D9005AE1FA?OpenDocument
    Regards,
    Jimmie A.
    Applications Engineer, National Instruments
    Regards,
    Jimmie Adolph
    Systems Engineer Manager, National Instruments Northern Region
    Bring Me The Horizon - Sempiternal

  • Photoshop crash on mac in 'slct' event callback

    Hi,
    I am getting consistent  Photoshop crash on mac (12.0.4) when handling 'slct' event callback in my extension
    The crash itself produce the same repor (see bellow) t as described  here: http://forums.adobe.com/message/3473893#3473893
    I narrowed it down to the case when you have 2 or more documents in "consolidate all to tabs" mode and you try to  pull out one of them.
    If you have a callback registered like this for 'slct' ExternalInterface.addCallback("PhotoshopCallback" + CSXSInterface.instance.getExtensionId(), eventCallback) and you try to access Photoshop.app.activeDocument Photoshop crashes with the bellow report
    It's hapening onlyon mac.
    Do you have any advice how to workaround it or even better a fix?
    Regards
       Lukas
    Process:         Adobe Photoshop CS5 [2734] Path:            /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/MacOS/Adobe Photoshop CS5 Identifier:      com.adobe.Photoshop Version:         12.0.4 (12.0.4x20110407.r.1265) (12.0.4) Code Type:       X86-64 (Native) Parent Process:  Adobe Flash Builder 4.5 [1259] Date/Time:       2012-04-03 17:57:37.438 +0200 OS Version:      Mac OS X 10.6.8 (10K549) Report Version:  6 Interval Since Last Report:          -2676258 sec Crashes Since Last Report:           36 Per-App Interval Since Last Report:  -1577868 sec Per-App Crashes Since Last Report:   36 Anonymous UUID:                      3253FFFA-8C14-41BE-B83D-82BE373CCD9F Exception Type:  EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Crashed Thread:  0  Dispatch queue: com.apple.main-thread Thread 0 Crashed:  Dispatch queue: com.apple.main-thread 0   com.adobe.owl                      0x000000010371d186 OWLDockGetAnchor + 8186 1   com.adobe.owl                      0x0000000103683bc2 0x103652000 + 203714 2   com.adobe.owl                      0x000000010368acb6 OWLHandleNSApplicationEvent + 40 3   com.adobe.Photoshop                0x000000010024e831 0x100000000 + 2418737 4   com.adobe.Photoshop                0x0000000100278615 0x100000000 + 2590229 5   com.adobe.PSAutomate               0x0000000121ccfbcf CPsWActionControl::Get(CPsWActionReference const&, CPsWActionDescriptor&) + 31 6   com.adobe.PSAutomate               0x0000000121cac44b CPsDocuments::DocumentCount() + 85 7   com.adobe.PSAutomate               0x0000000121c93b3f CPsApplication::GetActiveDocument(MultiScript::InterfacePtr&) const + 77 8   com.adobe.PSAutomate               0x0000000121c47ffe CPsApplication::HostGet(int, ScCore::Variant&) const + 2606 9   com.adobe.PSAutomate               0x0000000121ce72d8 MultiScript::TProxyBase::get(int, ScCore::Variant&, ScCore::Error*) const + 240 10  com.adobe.AdobeScCore              0x00000001221d72e2 ScCore::LiveObject::get(ScCore::String const&, ScCore::Variant&, ScCore::Error*) + 242 11  com.adobe.AdobeScCore              0x000000012222c4a1 _getProperty(APEDOMObjectRef*, ScCore::Variant const&, ScCore::Variant&, ScCore::Error&) + 113 12  com.adobe.AdobeScCore              0x000000012222dad7 APEObjectGetPropertyCB(Opaque_APEPlayer*, void*, void*, APEOpaqueAtom*) + 263 13  com.adobe.adobeswfl                0x0000000122932cf3 APXGetHostAPI + 21603 14  com.adobe.adobeswfl                0x0000000122fa4914 SWFLPlayer_Initialize + 2208548 15  ???                                0x000000012ab64e0e 0 + 5011557902 16  ???                                0x000000012ab652ec 0 + 5011559148 17  ???                                0x000000012abc2883 0 + 5011941507 18  com.adobe.adobeswfl                0x0000000122fa2915 SWFLPlayer_Initialize + 2200357 19  com.adobe.adobeswfl                0x0000000122f85d6d SWFLPlayer_Initialize + 2082685 20  com.adobe.adobeswfl                0x0000000122fa4914 SWFLPlayer_Initialize + 2208548 21  ???                                0x00000001267cb5e3 0 + 4940674531 22  ???                                0x00000001267cbc43 0 + 4940676163 23  ???                                0x000000012a04b807 0 + 4999919623 24  com.adobe.adobeswfl                0x0000000122a273b7 APXGetHostAPI + 1022759 25  com.adobe.adobeswfl                0x0000000122a28a83 APXGetHostAPI + 1028595 26  com.adobe.adobeswfl                0x0000000122d317dc APXGetHostAPI + 4210508 27  com.adobe.adobeswfl                0x0000000122d91276 SWFLPlayer_Initialize + 31878 28  com.adobe.ape                      0x00000001207c7946 APEInitialize + 1398

    Sure, I know about PSEvenScrubber. This on is different beast though. When activeDocument is null it's just it and you get an exception in the script if you try to use it, but in this case code like this:
    var ho:HostObject=app.activeDocument.hostObjectDelegate or
    var d:int=Photoshop.app.documents.length;
    cause the crash of the whole Photoshop
    Keep in mind that if i just switch between the documents without pulling them out of the dock everything works fine.
    But it can be releated though as it seems that something is not initialized properly, but in this case on deeper level than actionScript

  • Event Callback Problems during compilation

    Hi
    I try to register a callback vi with the "Register Event Callback"-node. I
    pass a reference of an array as user parameter into to the "Register Event
    Callback"-node. Everything works well in the development environment. But
    when I try to build an executable I get the Error "1003 . The vi is not
    executable".
    What is wrong?
    Mareike

    Hello Mareike,
    you can surch in the http://www.ni.com/support/ for "error" and "1003". There you will find a lot of links where this error is discussed. With a little luck, there will be an answer.
    Regards ThomasD 

  • Configure Event Callbacks in test stand using labview

    Hi,
    I was going through Full OI - Configure Event Callbacks.vi in the test stand example. Can you please explain me how the vi works and what is techniwue behind it?
    When i open the individual VI's in the reference, I could see more that 1 control in the front panel. But Only the user parameter is wired in the vi? Why is it so?
    Regards
    Gopal

    Hi Gopal,
    When the TestStand Engine fires events, this VI specifies how your Operator Interface will respond.  For example, let's examine the first event callback registered in Full OI - Configure Event Callbacks.vi , Exit Application.   When the TestStand Engine receives the message to shutdown, and then finishes its neccessary shutdown procedures, it will send a message to the Operator Interface.  For the Operator Interface to receive this message, it must "listen" for it.  In LabVIEW, this is done by Registering an Event Callback.  See the links below for details on how to implement this. 
    The answer to your specific question is in step 7 of the first link below.  When TestStand sends the message to LabVIEW, there is information that is always passed.  The other input controls contain this information.  To create a VI that always includes these controls, right-click on the VI Ref input to the Reg Event Callback Property Node, and then select Create Callback VI.
    Here are two references that talk about handling ActiveX callbacks in LabVIEW in general:
    Registering and Handling .NET and ActiveX Events
    Register Event Callback (Not in Base Package)
    Cheers,
    David Goldberg
    National Instruments
    Software R&D

  • Event callback insanity

    Can anyone tell me what might be causing
    such a serious error?
    #Date: Mon, Jan 26, 2004 1:56:37 PM
    #OSName: Windows NT
    #OSVers: 5.0
    #AppName: LabVIEW
    #Version: 7.0
    #AppKind: FDS
    D:\lvworm\src\lvsource\eventoracle.cpp(370) : DAbort: event callback insanity
    $Id: //labview/branches/Wormhole/dev/lvsource/eventoracle.cpp#112 $
    0x00589B50 - LabVIEW + 0
    0x0058A245 - LabVIEW + 0
    0x0058CFDB - LabVIEW + 0
    0x0040AF57 - LabVIEW + 0
    0x0DDAA9C7 - tsui + 0
    0x0DDA9FC3 - tsui + 0
    0x0DDA1FEF - tsui + 0
    0x581777B0 - teapi + 0
    0x77E3A2D0 - USER32 EnumClipboardFormats + 76F
    0x77E145E5 - USER32 GetDlgCtrlID + 1E
    0x77E15B51 - USER32 wvsprintfW + 132
    0x00B
    84CA0 - LabVIEW + 0
    0x00B3C46B - LabVIEW + 0
    0x00C0813C - LabVIEW + 0
    0x7C5987E7 - KERNEL32 SetLocalTime + 4FC

    Hi William,
    I can not off hand explain this to you beyond the obvious stuff.
    If you can reproduce this error at will, I suggest you share the details on how you did this.
    I also suggest you report this to NI as a possible bug. I am not sure if Win NT is still supported.
    Ben
    Ben Rayner
    Certified LabVIEW Developer
    www.DSAutomation.com
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • References won't close in UserMessage Event Callback example.

    I download the following example:
    http://zone.ni.com/devzone/cda/epd/p/id/2606.
    I was going to use some of the features of this example to pass variables from my OI to TestStand.  Well unfortunately, this example with the modified UserMessageCallback locks up everything with an R6025 error.  Well, it actually will also give me the Property Object warning dialog ONLY if I have the Debug Options set within the Station Options->Preferences tab set to report Object Leaks, otherwise I get the R6025 error.  Only solution is to go to Task Manager and close out LabVIEW.
    I attached a picture of the callback, I believe I am closing ALL possible references.  I don't understand why TestStand still thinks that the SequenceContext reference is open?   Is there something I have to do special to close the SequenceContext reference because of the Variant to Data function?
    I am running TestStand 4.2.1 and LabVIEW 2010.
    Thanks,
    PH
    Attachments:
    UserMessage Event Callback.png ‏53 KB
    Debug Warnings.PNG ‏19 KB
    R6025 Error.JPG ‏12 KB

    The original example failed, hence it did not work  Again, it did not work with TS 4.2 and LV 2010.
    All I was trying to do is use that example, to pass data from my Operator Interface to TestStand using the SequenceContext.  It was mentioned as an example in a previous post here:
    http://forums.ni.com/t5/NI-TestStand/Passing-Variable-from-Operator-Interface-to-Process-Model/td-p/...
    I attempted to add a fix for the Variant to Data function per reference to the KB, proposed by Anand Jain, in the previous posts!
    In the long run, I will have to go with the method proposed by Ray Farmer. 'The simplest way is just store it in the StationGlobals.'   Not exactly the method I prefer to use, but it seems to be working.
    Thanks,
    PH

  • While Installation of 11g database creation time error ORA-28056: Writing audit records to Windows Event Log failed Error

    Hi Friends,
    OS = Windows XP 3
    Database = Oracle 11g R2 32 bit
    Processor= intel p4 2.86 Ghz
    Ram = 2 gb
    Virtual memory = 4gb
    I was able to install the oracle 11g successfully, but during installation at the time of database creation I got the following error many times and I ignored it many times... but at 55% finally My installation was hanged nothing was happening after it..... 
    ORA-28056: Writing audit records to Windows Event Log failed Error  and at 55% my Installation got hung,,,, I end the installation and tried to create the database afterward by DBCA but same thing happened....
    Please some one help me out, as i need to install on the same machine .....
    Thanks and Regards

    AAP wrote:
    Thanks Now I am able to Create a database , but with one error,
    When I created a database using DBCA, at the last stage I got this error,
    Database Configuration Assistant : Warning
    Enterprise Manager Configuration Failed due to the Following error Listener is not up or database service is not registered with it.  Start the listener & Registered database service & run EM Configuration Assistant again....
    But when I checked the listener was up.....
    Now what was the problem,  I am able to connect and work through sqlplus,
    But  I didnt got the link of EM and when try to create a new connection in sql developer it is giving error ( Status : failure - Test Failed the Network Adapter could not establish the connection )
    Thanks & Regards
    Creation of the dbcontrol requires a connection via the listener.  When configuring the dbcontrol as part of database creation, it appears that the dbcontrol creation step runs before the dynamic registration of the databsase with the listener is complete.  Now that the database itself is completed and enough time (really, just a minute or two) has passed to allow the instance to register, use dbca or emca to create the dbcontrol.
    Are you able to get a sqlplus connection via the listener (sqlplus scott/tiger@orcl)?  That needs to be the first order of business.

  • Engine error HP LaserJet 100 color MFP M175 PCL6 wireless

    Hi folks,
    I would like to help with the "engine error" you're experiencing. I would like you to download the HP LaserJet Pro Series Firmware Update Utility. With this utility we can install a firmware update for the printer hardware. Please read all the steps below before clicking the above link. If you are using a mac operating system Click here instead.
    Flash Firmware Update Notes:
    The Firmware Update Utility uses the USB connection to the printer.
    The HP LaserJet 100 color MFP M170 series print driver software must be installed prior to using this utility.
    The HP LaserJet 100 color MFP M170 series printer must be on and in a READY state as shown by the LCD display on the control panel and remain powered on during the entire firmware update process.
    Depending on the processor speed of your pc, the firmware update process may complete on the printer before the update status progress bar in the flash firmware update utility on the pc screen completes, this is normal.
    Once the update process has started, do not use your pc for any other activity until the process is complete.
    Do not power cycle the product or the pc until the firmware update process is complete
    Steps to take :
    1. Download the flash firmware updater file by clicking the appropriate  link above. (The first link is for Windows operating systems and the second is for Mac)
    2. Turn the printer off and then back on to clear main printer memory. 
    3. Double click on the file M170_colorMFP_Series_FW_Update-20111021.exe flash firmware update utility file. An HP firmware update window will open.
    4. Select the appropriate HP M170 MFP series driver in the dialog window. If you assigned a different name to the HP M170 MFP, choose the name that represents the correct printer.
    5. Click on ""Send Firmware"" when ready to proceed.
    6. The progress bar will begin to move to the right indicating information being transferred.
    7. DO NOT power cycle the product or the pc during this process or the product may become unstable and or unusable without further attention from HP. The flash firmware update can take up to 5 minutes to complete. Please be patient.
    8. During the product flash firmware update, the display on the product control panel will display ""Printing Document- Erasing - Programming - Complete - Hewlett-Packard - Ready - Initializing - Ready"". Once the download is finished the printer will be in the Ready state.
    9. At the conclusion of the firmware update, the dialog window will show a smiley face. Click on exit.
    10. The flash firmware update process is complete
    Please let me know if this resolves the issue and/or if you would like further assistance.
    Sunshyn2005

    After each print job I get the message on printer screen  "Engine error press [OK]"  It will print again only after pushing Ok button.  Is there a fix?  HP printers have not been that reliable, I 'm will not buy onother if this cannot be fixed.

  • Problem with register event callback in use of instrument control

    now, i use the register event callback to register a value change of a boolean control on the front panel, and wire the cluster's ref of the instrument control parameters to the user parameter input, then create the callback vi. In the callback vi, i select the pump-control subvi, and pass the user parameter to the subvi. The problem is that,  when i press the boolean control, the instrument (here is pump) can act, but immediately, the code crashes.
    I use labview 8.6
    Attachments:
    callback vi.png ‏8 KB
    register event callback.png ‏8 KB

    You would wire the event registration wire that comes out of the Register for Events node into an event structure.  You will need to right click on the event structure and check off "Show Dynamic Event Terminals" and it into that.  Then you can create a new Event Case that uses the dynamic event.  You can place your subVI in that event in whatever way you want.  (Just drop the subVI in or do a Call by Reference there, or whatever.)  Look in the Example Finder for "Dynamically Register for Events.vi".

  • How to get Alerts mail for adapter engine errors in SAP PI 7.0

    Hi Friends,
    I configured Alerts in PI 7.0. with the help of t-code u2018ALRTCATDEF and created a new alert catergory.
    In container tab i have mentioned all give below elements.
    SXMS_MSG_GUID, SXMS_RULE_NAME, SXMS_ERROR_CAT, SXMS_ERROR_CODE, SXMS_FROM_PARTY, SXMS_FROM_SERVICE, SXMS_FROM_NAMESPACE, SXMS_FROM_INTERFACE, SXMS_TO_PARTY, SXMS_TO_SERVICE, SXMS_TO_NAMESPACE,SXMS_TO_INTERFACE
    I am getting alerts when I manually test the alerts configurations by running the report u2018RSALERTTESTu2019.
    I am getting mail as :
    Alert ID: ##00009##
    Dear Administrator,
    This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
    Message ID:
    Interface:
    NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
    Double click on that message ID and click on error in left hand tree.
    Please take appropriate action in co-ordination with respective functional and BASIS consultant.
    But When I am getting a error , I am not getting an alert mail. Right now iam doing in XI Development.
    I am not getting an Alert mail , when my message is in status of : System Error . Error catergory is : XI_J2EE_ADAPTER_JDBC.
    Kindly tell how to get alert mail for error catergory : XI_J2EE_ADAPTER_JDBC and in Adapter engine errors.
    How to get alert mail when my message is failed with any reason in Adapter engine.
    Waiting for quick replay. Please help me out.
    Regards,
    Ahmed.

    Hi thanks for quick reply.
    As per your given link : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14877. [original link is broken]
    I have done all these steps. But still little problem.
    as per link he is getting Error  description , error message id , alert rule..
    In my case I am not getting these information. when my messages failed. When I am doing manully testing the alert getting an mail as :
    Alert ID: ##00009##
    Dear Administrator,
    This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
    Message ID:
    Interface:
    NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
    Double click on that message ID and click on error in left hand tree.
    Please take appropriate action in co-ordination with respective functional and BASIS consultant.
    Is it okay the body of mail??.
    I am not getting alert mail when my messages failed in adapter engine and Integration Engine.
    Ex my message is failed in AE:as below.
    My messages flow as : SAP --> XI --> DB.
    Messages is success (in ECC moni)> XI moni also success> XI Adapter engine getting error as (Status: System Error) and (Error Category : XI_J2EE_ADAPTER_JDBC).
    Regards,
    Ahmed.

Maybe you are looking for