REPORT RUN TIME ENGINE EXCEPTION

I am creating many reports ,some of which are Stored Procedures based,mostly group reports and some are very simple LIST reports containing simple ONE table based query.
When i fetch report from a FORM(created in FORM BUILDER),some times the REPORT ENGINE generates an exception whose description is "DIVISIBLE by ZERO" and the REPORT ENGINE crashes down.This exception occurs after fetching the report 3 to 4 times,not every time we fetch the report.
I have tested those reports in Windows 98,Windows NT and
Windows 2000 Operating systems environment.The same problem occurs ever where.
If any body has experienced such a problem or knows the solution ,kindly respond me.
THANX

Can you please post any error numbers if any that you get while doing this ?
Ex REP-12345
FRM-13456
etc
This will help us to find out the problem faster
Thanks
The Oracle Reports Team

Similar Messages

  • LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

    Hi all,
    I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
    I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9B​D7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
    Solved!
    Go to Solution.

    Hello guys,
    thank you very much for your answers!
    @Ruediger:
    I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F​3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI. 
    To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
    @GovBob:
    I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE06​35E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
    I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
    Kind regards, Roman

  • Error involving Report Generation Toolkit and Labview Run Time Engine

    Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

    I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
    Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
    I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
    I displayed my App.Property of APP.DI
    R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
    Any ideas ?
    Greg Klocek

  • Labview using Report generation toolkit in 2011 run time engine

    is that possiblity to run the  word in labview using Report generation toolkit in 2011 run time engine

    It is possible to use the Report generaion toolkit with the run time engine.  But you will have to include a lot of VIs from User lib since the report generation toolkit uses a lot of dynamically called VIs and classses.
    Certified LabVIEW Architect
    Certified Professional Instructor

  • LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

    I'm having a problem building an installer in LabVIEW 2011SP1.
    It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
    Now when I try to build the installer I get "The build was unsuccessful."
    Possible reasons: Error generating preview for My Application 3.1.7.
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    *** Error: An internal error occurred for which the cause is unknown. (Error code -41)
    *** Error Details:
    Error in MDF API function: _MDFCommon_GetNextLogMessage
    Error in MDF::GetInstance - MDF static instance is not initialized!
    *** End Error Report
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
    Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle
    Solved!
    Go to Solution.

    I do have the LabVIEW 2013 discs but didn't install it.
    I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
    I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
    Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
    So now I need to distribute 2 runtimes with my application?!?!
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle

  • Error 1722 when uninstalling Labview run-time engine 7.1.1

    I have been trying to uninstall all NI software so I can start off with a clean slate. I have been going to the control panel under add/remove programs to remove the NI stuff. Everything is gone except the Labview run-time engine 7.1.1. Everytime i try to remove it, i get teh 1722 error followed by the 1603 error. I've tried repairing it but I still get the same results when i try to remove it agian. I've also tried removing it with MSI Blast. This did not work either. I've gone through the registry and manually deleted anything related to NI and that still didn't work. Is there anything else I could try?
    Thanks,
    Nick

    Hey Steve,
    I have tried repairing it through the control panel.
    I tried reinstalling just the run-time engine and it said it was already installed. So I reinstalled Labview 7.1 and repaired the 7.1.1 run-time engine through the control panel. Then I uninstalled everything. Thanks for all your help
    Thanks again,
    Nick
    Message Edited by Nick_C on 03-12-2007 03:57 PM

  • EXCEL Run Time Engine ?

    I'm using one of the vi that ships w LV7.1.  It basically reads in an EXCEL file.  I'm also using the Report Generation ToolKit to write the final report data of the UUT.  Do I need MS Excel installed on my target machine ??  Is there such a thing as a run time engine for Excel ?

    As far as I know in the past excel is an activeX object which is installed with excel or office and is part of the licence, so I was under the impression that inorder to communicate with excel (ei through automation) you needed to install the application.  HOWEVER, I was recently at a Microsoft developers event (included a session about office 2007 beta) which the speaker mentioned that this will nolonger be the case, you waill be able to automate both excel and work documents without having the application installed on the machine, but not powerpoint. This might have to do with the change in document formats from .doc and .xls to .docx and .xlsx.  Essentially the new format will be a zipped XML marked up doccument with much more open format so the office suite in not as needed for automation (opening the way for much more programability and 3rd party software interactions).  I could be wrong about needing to install office to get the office support to work for the report generation since I use LV 7.0 and OfficeXP.
    Paul
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA

  • You may not need to install the Run Time Engine...

    I know this has been mentioned before, but after a long search of the archives, I couldn't find the right person to give credit to - sorry!
    If you have a simple exe, you may not need to install the runtime engine on the target machine at all - all you need to do is include some of the engine's files with the exe for it to work. Try it out: copy the following files & folders into the folder containing your exe:
    ..\National Instruments\shared\nicontdt.dll
    ..\National Instruments\shared\nicont.dll
    ..\National Instruments\shared\LabVIEW Run-Time\your_version\everything (including all sub-directories)
    so, using 6.1 as an example, you exe's directory would like something like:
    ..\AppDirectory\MyApp.exe
    ..\AppDirectory\MyApp.ini
    ..\AppDirectory\My_Apps_DLLs,if_any
    ..\AppDirectory\nicontdt.dll
    ..\AppDirectory\nicont.dll
    ..\AppDirectory\lvapp.rsc
    ..\AppDirectory\lvjpeg.dll
    ..\AppDirectory\lvpng.dll
    ..\AppDirectory\lvrt.dll
    ..\AppDirectory\mesa.dll
    ..\AppDirectory\serpdrv
    ..\AppDirectory\models\heaps_of_stuff_in_here
    ..\AppDirectory\errors\more_stuff_in_here
    ..\AppDirectory\script\and_some_bits_in_here_too
    Take all of this data to a machine without LabVIEW or the runtime installed, and try to run the exe - all going well, it will execute without any problems. This exe distribution method can be really useful, especially when distributing autorun presentations on CD-ROMs.
    * DISCLAIMER: as far as I am aware, this method is NOT authorised or supported by NI - use it at your own risk!
    cheers,
    Christopher
    PS: I'd like your feedback: please give this posting a rating
    Christopher G. Relf
    [email protected]
    Int'l Voicemail & Fax: +61 2 8080 8132
    Aust Voicemail & Fax: (02) 8080 8132
    EULA
    1) This is a private email, and although the views expressed within it may not be purely my own, unless specifically referenced I do not suggest they are necessarily associated with anyone else including, but
    not limited to, my employer(s).
    2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
    3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

    Yes, this method is not supported. However, this method is good if you wish to write your own installer for a LabVIEW Application. (Note: The method above does not install DataSocket, NI-Reports, or any of the 3D Graph controls.)
    I would still suggest running the LabVIEW Run-time Engine installer so that more than one application can use it.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Minimizing LV Run-Time Engine installati​on size?

    Hi!
    Is there any approach how RTE installation size could be minimized by selecting only the components that are really needed in a certain application? This would be very useful because:
    1) Currently, if you select to install "NI LabVIEW Run-Time Engine" in RTE setup, you will get 160MB of components installed.
    There are relatively much extra stuff that is definitely not needed in most of the applications (like NI-Reports, TDMS etc). Where is the option to deselect these? 
    2) Installation takes quite much time, even several minutes. If the installation is run silently and as an external part of the application installation itself, it is quite hard to estimate RTE installation progress.
    3) There may be a bug in component installation
    (see http://forums.ni.com/ni/board/message?board.id=170​&message.id=239662&query.id=187629#M239662),
    which could be avoided if that component were excluded from install.
    Is it possible to customize the installation by editing Setup.ini or lv82runtime.msi's LabVIEW 8.2 RTE PDF.xml? Because NI does not seem to instruct how to do it, any 'hacker' solutions would be useful!
    Thanks,
    Wirer
    Message Edited by Wirer on 04-10-2007 07:54 AM

    The installer for the LabVIEW run-time engine can be found at \..\National Instruments\LabVIEW 6\AppLibs\installs. You will need separate run-time engines for the PC and Mac as executables are not cross-platform. To run an executable on a PC, you will need to use the PC version of the application builder and to run an executable on a Mac, you will need the Mac application builder. When you get 6.1, if you build an application with it, you will need to install a 6.1 run-time engine.

  • Fatal Error in LV8.2 Run-Time Engine install

    Hi,
    We have a serious problem with installation of LV 8.2 Run-Time Engine (RTE).
    When a Domain Administrator is trying to install the RTE, the installation stops with the following error (see RTEInstallFatalError.jpg):
    In error message path 'mk' references to domain Administrator user name.
    When a Local Administrator installs the RTE, there is no problem.
    Any explanations or suggestions? It is a very heavy bug, if even the domain administrator cannot install the RTE and therefore use the application.
    Thanks,
    Wirer
    Message Edited by Wirer on 04-04-2007 06:25 AM
    Attachments:
    RTEInstallFatalError.JPG ‏13 KB

    Found a solution to the problem...
    As the error indicates there is a problem with the user's profile folder 'My Documents'. Domain administrator did not have 'My Documents' in his profile. After creating such a folder there manually, RTE installation worked successfully.
    So now the question rises: why RTE installation requires such a folder to exist? Nothing is installed there!
    My opinion is that RTE installation needs to be much more reliable than it is currently. Professional developers who make commercial products using LabVIEW will have a lot of pain with the current solution.
    1) Customization options for RTE are poor. I think that most of the companies that deploy their LV-made application want no extra stuff installed. If the developer knows that e.g. TDMS or NI-REPORTS are not used in his application, there should be an option to NOT install these with RTE!
    2) There should be more documentation (by NI) on RTE installation and its error handling should be improved.
    I hope more discussion on RTE.
    Thanks,
    Wirer
    Message Edited by Wirer on 04-04-2007 08:48 AM

  • Installing NI-DAQ (MAX) also installs Run-Time engine?

    Hello all,
    I have noticed, on computers where I have installed MAX (which installs NI-DAQ) that the Run-Time engine also appears.
    Does MAX install the Run-Time? Or was it MAX that installed? Or was it probably already there....?
    Thanks,
    Richard
    Richard

    That would make perfect sense. It'd be "nice" if the CD eluded to that fact, so you don't have to bother with finding the RTE if it's already there.
    Thanks Analog Kid --- good Rush song by the way... but the're all good! (except maybe Rivendell, but only a true fan would know that one).
    Richard
    Richard

  • LabWindows/CVI 2009 Run-Time Engine update

    I wanted to let everyone know that NI has released an udpated CVI 2009 Run-Time Engine. Information on what bug(s) this update fixes can be found here. If you are currently not using the CVI 2009 Run-Time Engine, you do not need to install this update.
    This is an updated installation of the CVI Run-Time Engine, not a patch. If you download and install this update it will upgrade whichever version of the CVI Run-Time Engine you currently have to version 9.1.0.428 (CVI 2009 released with version 9.1.0.427). One way to find out which version of the CVI Run-Time Engine you have installed is to view the version number of c:\windows\system32\cvirte.dll. If you install version 9.1.0.428, any installer distributions that you create from any version of the CVI ADE will include version 9.1.0.428.
    If you have not yet installed LabWindows/CVI 2009, it's recommended that you install this update, either before or after you install CVI 2009.
    Luis

    To be clear, the original problem that you reported ("Attempt to free pointer to memory not allocated by malloc() or calloc()") might very have been the problem that this patch fixed, which was in fact new to 2009. But that problem only happens if there were actual plots in the graph.
    However, after looking at the "dynamic memory is corrupt" isse some more, it turns out that it is actually expected behavior, believe it or not. This is a limitation of easytab controls, caused by how they use callback chaining in their implementation. Whenever a panel or a control has its callback chained, you cannot change the callback, or make a copy of it after the chaining takes place. This is described in the EasyTab_ConvertFromCanvas function help ("...For the same reasons, do not call DuplicatePanel or DuplicateCtrl on any of these panels or controls after the Easy Tab control has been created.").
    As you probably have read elsewhere, easytab controls are quite obsolete. They were a stopgap "solution" to the problem of there not being a native tab control in the CVI user interface library. Native tab controls were finally added in CVI 8.0, and so we recommend that, if possible, users update their code to use these instead.
    Luis

  • Can't install run-time engine on Ubuntu 8.04. Get /bin/sh failed to load.

    Simply receive a message when trying to install the LabView run-time engine .rpm file that says /bin/sh failed to load (or is required, I forget exactly).  I checked, I have BASH installed, and /bin/sh is a shortcut to an executable on my machine.  Is this a bug in the installer, or is there something else I need?

    LabVIEW installation is not supported on Debian based Linux systems (of which Ubuntu is the most popular).  However, many people have had success installing to various flavors of Ubuntu.  You can search these forums using the key Ubuntu and find the problems they had and how they solved them.  If you cannot find an answer to your problem, let us know.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • Unable to run vi with labview run time engine

    Hi All,
    I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
    When I make a call to it from Test Stand 4.1 it works lovely.
    When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
    I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
    I don't really understand! And am tearing my hair out.
    The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
    I have attached the problemVI.lvproj.
    Thanks for any advice or help.
    Matt
    Attachments:
    problem VI.lvproj ‏41 KB
    teststand.JPG ‏43 KB

    Matt,
    it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
    Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
    Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Run-Time Engine error

    I have created an automated test and had it running as an executable on a stand alone test computer. I updated my LabView software to 8.6.1. I just made some changes to the test and recompiled it. When I tried to run it on the stand alone computer it gave me an error about the LabVIEW 8.6.1 run-time engine missing. I thought when the project was built all the files that pertained to running it were also built into the folder. Has anyone run into this that could offer some advice.
    Thanks
    Chirs
    Solved!
    Go to Solution.

    Did you create an installer or simply build the exe? If you only built the exe you will need to install the run-time engine on the target machine. If you created an installer you can include the installation of the run-time engine as part of the installer.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Maybe you are looking for