Update11.0.07 crashes embedded ActiveX Labview 2013 applications

I would like to know how to embbed a PDF File in an application and be able to programmatically generate events such as set a page or chenge the zoom level.
Additionally, it is compulsory for me to do it not depending on the currently installed Adobe Reader version because I am developing software for clients and I do not know what version they have installed in their computers.
I tried different alternatives:
1. I embedded an ActiveX container linked to an Adobe Reader X object (this one was the version installed in my computer when I tried doing this). It worked fine but after updating to Adobe Reader XI my ActiveX was broken. Therefore, I realized that using ActiveX containers is a version-dependent solution.
2. I embedded again an ActiveX container and linked this one to the web browser. I was able to display PDF Files but could not generate programmatically the events mentioned above. This solution is not depending on the installed version of Adobe Reader but unfortunatelly it is not enough to solve my problem.
Any advice?
Thank you very much
Víctor

Similar Messages

Labview 2013 crashing when restarting VI

My VI runs and I have no problems.
If I stop then Vi and re-run it, pretty much every second time it crashes. It does not point to anything and the only message I get is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: LabVIEW.exe
Application Version: 13.0.0.4051
Application Timestamp: 525595c6
Fault Module Name: NiViPxi.dll
Fault Module Version: 5.4.0.49152
Fault Module Timestamp: 51c243ad
Exception Code: c0000005
Exception Offset: 0000bbe0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 6153
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This only clue in the above I can find is NiViPxi.dll
I am using a PXI rack so maybe it is to do with one of the devices?
I would be nice to have more clues, does anyone know why labVIEW keeps crashing?
Rgds,
Sean
Solved!
Go to Solution.

Hi jinfone.t
I managed to root cause it to a netway 72 PXI dll and have fixed the issue, (took a lot of effort!)
- Does the crash only occur when you re run this particular VI that you are talking about?
Yes
- Is there any crash logs generated?
None that I know of apart from the output I pasted on the screen. It's possible there is something in the event monitor
- What does your VI do?
It function tests our product, (IOT)
- Would it be possible to show the code?
I'm afraid not as it is proprietary. However, the issue appears to be due to the dll. Netway may release the VIs but I believe you are required to buy hardware/ software.
The issue I have is that LabVIEW is not handling this crash well at all. It does not point to the problem dll nor does it drop a fail log that I know of.
Thanks for the feedback.
Ciao,
Sean

Labview 2013 are closing when I try read table from database.

Labview 2013 are closing when I try read table from database.
I don't get error message, Labview just crashes. I'm use Labview x32 and Database Connectivity Toolkit connective on Windows 7 x64. I connect to PostgreSQL with ODBC driver, connection is stable.
In my database I have many tables, I can read all them without one.
When I try read bad table I get data and then labview crash. When I restart Labview I don't have any message about error.
Also I try use LabSQL-1.1a. But it has same result.
Solved!
Go to Solution.
Attachments:
DBT.png ‏104 KB
LabSQL.png ‏67 KB

Try connecting using UDL file. What operation you are doing with database
You can create the same.. Do this Tools --> Create Data link..
Then go to http://www.ni.com/pdf/manuals/371525a.pdf link and see page 3-5. It will help
Kudos are always welcome if you got solution to some extent.
I need my difficulties because they are necessary to enjoy my success.
--Ranjeet

LabVIEW 2013: Source distribution, destination path for post build VI changed?

Hi,
In a source distribution for an embedded target (Real-Time for instance) you specify both "Local destination directory" and "Target destination directory". Let's say the local directory is "C:\MyProject\MyModules\", and the target directory is "C:\" for instance. Then on my build machine my source distribution will end up in "C:\MyProject\MyModules\c\<source distrib files>", and I can then FTP everything from <source distrib files> to the root of my target's c-drive (or in some cases I can just deploy directly after the build, and LabVIEW will move the files to the target for me).
You can also specify a Post Build VI that can do stuff to your source distribution after the build has completed. Such a Post Build VI has an input named "Destination Path" for use inside your Post Build VI, so you can find your files to operate on :-)
In LabVIEW versions prior to 2013 this destination path would be "C:\MyProject\MyModules\c\", but in LabVIEW 2013 the destination path is only "C:\MyProject\MyModules\" thus missing the target destination directory part. Now my Post Build VI can no longer find my source distribution files, unless I inside that VI hardcode the target destination directory - and that isn't a good solution.
Is this changed by design in LabVIEW 2013, or is it a bug?
Cheers,
Steen
CLA, CTA, CLED & LabVIEW Champion

I don't do a lot of (actually any) source distributions of embedded files, but I can tell you that there was a bug in earlier versions where during an application build, the destination path was reported incorrectly. Perhaps this is related.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Request for Conversion from labview 4 to labview 2013

Dear Support,
Could you please update these vi to be readable by Labview 2013?
Thank you in advance, Mary

Mass compiled in 8.2.1, which you can open with 2013.
One of the VIs kept crashing my LabVIEW, so it is not included in this zip file.

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

Report Generation Toolkit labview 2013 64bits?

Muy buenas tardes.
Estoy buscando el Report Generation Toolkit para labview 2013 64bits, lo he buscado pero no logro encontrarlo y con este mismo pero de 32 bits me marca error al instalarlo.

Hola Antonio,
Intenta con esta liga : http://www.ni.com/gate/gb/GB_EVALTLKTREPGEN/US
Espero que por aqui lo puedas descargar,
saludos
Erwin Franz R.

Report Generation Toolkit failure with Win 7 and Labview 2013

I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files. If I try to run the New Report.vi with report type Excel selected I get error -2146777998. Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error. Selecting Standard Report or HTML also run without errors.
I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
Solved!
Go to Solution.

I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt. The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

Labview 2013 report generation toolkit word 2010 insert table problem

Hi,
I am currently evaluating LV2013 with respect to the report generation toolkit for use with word 2010. My Vi/program won't insert the correct table and gives me an error message. see below:-
Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table.vi->NI_Word.lvclass:Append Text Table to Report.vi->Word Table save.vi
I have since run the following word example.vi provided by NI within LV2013 office examples:- Growable table.vi. this gives me the same error!
Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table.vi->NI_Word.lvclass:Append Text Table to Report.vi->Growable table.vi
It would seem that regardless of my own Vi there is a fundamental problem in the office example vi.
I have found examples of a similar problem in LV2011/2012 but the work around code doesn't seem to match the LV2013 vi's code for a direct replacement.
Can anyone help/shed some light on this?
Thanks in advance,
Dan.

Because the upgrade of Word from 2007 to 2010 I needed to upgrade an existing application from LabVIEW 2009 to 2013. This didn't work because of the insert table error. I discovered that the problem is the vi called "Word_Insert_Table.vi" located in the ..Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\addons\_office\_wordsub.llb. There is a "Cut" command implemented, this command removes the created cell instead of clearing it. Therefore the table will be filled half and then returnes with an error. I have removed this command. I have posted the changed vi (LV 2013).
Attachments:
Word_Insert_Table.vi ‏30 KB

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

LabVIEW 2013: An error occured trying to load the assembly

Hey all,
I'm trying to load a .NET 4.5 dll into LabVIEW 2013.
When I place any of the .NET VIs and try to select the one I'm after it says "An error occured trying to load the assembly" and won't let me load it.
I also tried importing the dll, but that gave errors too.
It's defintely a .NET 4.5 dll as the .NET reflector gives me
[assembly: ComVisible(false)] [assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName=".NET Framework 4.5")] [assembly: SecurityRules(SecurityRuleSet.Level1)] [assembly: SecurityPermission(SecurityAction.RequestMinimum, SkipVerification=true)]
To try and get around the import issue, I added the following to my LabVIEW.exe.config file
<?xml version ="1.0"?>
<configuration>
<runtime>
<loadFromRemoteSources enabled="true" />
</runtime>
</configuration>
but it made no difference.
Any suggestions? All the things I've read so far are for 2010.
Solved!
Go to Solution.

Hornless.Rhino wrote:
Wart wrote:
I had the same issue a while back. Unfortunately mine magically resolved itself, but I made a post with what I'd been reading and got a reply with another suggested link. It sounds like you've gone down the same road, but I figure every little bit helps:
http://forums.ni.com/t5/LabVIEW/Error-Loading-NET-Assembly-in-2013/m-p/2521098
Thanks.
Hopefully mine will resolve itself too. LV2013 is meant to support the newer stuff without me having to mess about.
We shall see...
So far no dice.
It's really bizarre. It works with sample c# code in visual studio (see link below), but for some reason LabVIEW doesn't like the dll (tried both LV 2012 and 2013).
Sample code (not mine) is available at http://elbruno.com/2013/12/01/kinectone-hello-world-with-kinectsdk-v2-body-count/

Conversion of VIs from LabView 2013 to 2011

Hi,
I would be grateful for conversion of zipped VIs from LabView 2013 to 2011.
Thank You,
Michal
Solved!
Go to Solution.
Attachments:
main VIs.zip ‏38 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
main VIs 2011.zip ‏27 KB

FPGA FlexRIO SCTL LabVIEW 2013 Compilation Problems

Hi,
I have an FPGA FlexRIO (7962R) VI that interfaces to a 6585 LVDS board that consists of a SCTL running at 200MHz and using a Xilinx Coregen FIFO.
In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
The Xilinx FIFO is probably irrelevant as I have tried cloning the VI and removing the FIFO and still get the same problem.
Any ideas, things to try or solutions?
Thanks,
Dave
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

Have you tried optimising the Xilinx compiler for Timing?
You can't modify the Xilinx compile options of a FlexRIO target.
In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
What compile error are you getting? Does not reliably mean that sometimes it does compile correctly? Can you upload a simple example of a piece of code that works in 2012 but not 2013?
National Instruments
FlexRIO Product Support Engineer

DAQMX vi files missing in Labview 2013

I try to open this file slinger-logger.vi [see attachment], but I can't open it, because it is missing files such as DAQmx Clear task.vi
I already tried to install several versions of DAQmx (14.1, 9.9, 9.4):
http://digital.ni.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248
But I couldn't get the file working without those missing vi errors. Can anyone get this file working in Labview 2013? Or Labview 2012?
Attachments:
Slinger-logger.vi ‏70 KB

kihans wrote:
I already tried to install several versions of DAQmx (14.1, 9.9, 9.4):
http://digital.ni.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248
But I couldn't get the file working without those missing vi errors. Can anyone get this file working in Labview 2013? Or Labview 2012?
Why do you install random version of DAQmx, especially since 9.4 does not even support the LabVIEW 2013 or 2012 versions you mentioned. You even show the link outlining that! Pick the neswest one only!
Tell us exactly what you did:
Did you install DAQmx after installing LabVIEW and did you select support for the installed LabVIEW version?
Did you reboot after installation?
LabVIEW Champion . Do more with less code and in less time .

Labview 2013 executable works only on develoment machine?

Hi all
I created an executable so as to distribute my test software but it only runs on the development machine. I have successfully distributed my executables before with labview 2012 on target machines by simply creating the .exe in project explorer and then installing the nessary labview drivers and run time engine without problems. Now I created a new test programme with Labview 2013 and I can't get my new .exe test software application to run on the target machine. Has anyone seen this type of problem before? Any assistance will be appreciated.
Thanks
Solved!
Go to Solution.

In addition to the run-time engine you are likely missing some other installers. Lets say you used RS-232 code in your EXE well now you need to install VISA run-time on the new machine. Did you use DAQ? Now you need DAQmx. Did you use NI-Scope? NI-DMM? NI-Power? NI-Switch? You'll need to install those as well.
In 2013 the process of making an installer can detect what installers you need. In previous versions you just have to know which you used and select them in the Additional Installers section.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Update11.0.07 crashes embedded ActiveX Labview 2013 applications

Similar Messages

Maybe you are looking for