Labview 2013 error 1304

Hi
I have the latest version of Labview 2012 on my computer. It has been running well now for over 6 months. I now wish to update that with Labview 2013
First question do you have to remove Labview 2012 and two modules first before you install Labview 2013?
Problem 1. Within a few minutes into the installation process l obtain error 1304. When reviewing the file location reported in the error popup, the file states its a Labview 2013 template. I do not how that occurred but l have installed the last critical updates for Labview 2013 including the NI 488 driver updates for Labview 2012
Problem 2. If you ignore error a second error box pops up with no code.
A month ago l contacted our local NI support but they could not help. I have been away for a month and now l was hoping to have the bug fixed. But it still occurs. I could not find anyone who has had this error in the search for errors. The closest was error 1303
So at the moment l cannot install Labview 2013.
Has anyone had this problem. The word file illustrates the pop up messages.
Regards
Wetland
Attachments:
Labview 2013 installation error.docx ‏60 KB

Hi
Thank you for your response. I am downloading Labview 2013 onto my own home computer using the supplied DVD. I have full administrative privileges.
When l get Labview working at home l then download it at work. I cannot afford to have Labview not operating at work.
Last night l received a critical update for Labview 2013 patch f2. The update program seems to think l now have Labview 2013 installed. If l get no solutions to the problem l will install the patch just to see if that will fix the problem.
At the moment it seems that no one else is having the same problem since you are the first to respond. Thank you for your information
Regards
Wetland

Similar Messages

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

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/

Fix overlapping controls in error cluster (LabVIEW 2013)

In LabVIEW 2013, the "Error In.ctl" and "Error Out.ctl" have overlapping controls. If you run the VI Analyzer, you get an error from this arrangement. That shouldn't happen in something that's built-in.

Has an answer been determined for this?
I am getting this error for a few objects, but the error is not consistent and there doesn't seem to be alot of information on it.
See the attached images.
The Standard "error out" cluster is reporting 2 overlapping errors,
Status indicator
code indicator.
My "BioSig Control" is reporting 3 overlapping errors,
Bump/Offset F3
Yoke Connection Control
Programmer Connection
My question, are these really errors? or is this a defect in the analyzer and these indicators pose no threat to VI performance?
-Regards
eximo
UofL Bioengineering M.S.
Neuronetrix
"I had rather be right than be president" -Henry Clay
Attachments:
Overlapping control error labview.PNG ‏56 KB
Overlapping control error labview error output.PNG ‏5 KB

How to remove error 59 which occurred while using Send Email Using Smtp Client .VI in Labview 2013.

Hi,I am trying to run Send Email Using Smtp Client .VI in Labview 2013 examples ,but it gives error 59.Please can anyone suggest how to remove the error.The printscreen is attached below.
Solved!
Go to Solution.
Attachments:
error.docx ‏310 KB

Thanks for the help,but i have set the parameters right but still it does not work for me.Please suggest me reasons and how to correct them.
Attachments:
error.docx ‏270 KB

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

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 slow after building application

I have Labview 2013 with the DSC module installed.
I am running on Windows -64bit with 4 GB RAM
After I build my application, Labview slows to a crawl. There are no errors when I create my application and my application runs fine
All other programs run fine.
The windows task manager shows CPU use ranging from 2 to 20%
I have to shut down the computer and restart it. Then Labview is again running fine. Until I build my application again.
My application was originally developed in Labview 2012
I have not yet tried to create a new application to see if it is specific to my application or my Labview setup. I will try that next but I wanted to see if anyone else had this issue.
Thanks

Is this Windows 8, 7, Vista, etc?
Are you running 32-bit LabVIEW or 64-bit?
I would definitely recommend seeing if this problem happens when you try to build any application, or just your specific application?
Assuming the problem only occurs with your specific application, I would recommend that you try to build it on a different machine (assuming you have access to one) and see if LabVIEW behaves the same way on that other machine.
When you originally built your application in LabVIEW 2012, did you encounter this problem?
You could also try repairing both LabVIEW and the DSC Module to see if that makes a difference.
Regards,
Ryan K.

Using "panelresize.vi" in Labview 2013, in code originally written for Labview 2006.

Hello,
I'm updating code written in Labview 2006 to make it compatible with Labview 2013. My code calls a custom TDMS file viewer vi. This viewer calls a function called "panelresize.vi". This is a NI vi that has been updated since the 2006 version. The new version includes a "help - boolean refnum" in the input cluster, so that the vi now expects a cluster of 9 elements instead of the 8 that I am sending it. I am not sure what this "help refnum" is, how to use it, or how to add this to my input cluster in the calling function so that the error goes away.
Any suggestions?
Thanks!
Attachments:
Untitled.png ‏392 KB

Hi,
it is a help button. You can add a help button to your customized File Viewer. If you don't want this button, you can make it invisible.
What requirements drive you to make your own customized File Viewer?
FYI. In LabVIEW 2013, we made changes to improve the performance of the file viewer. For the compatibility, we kept the panelresize.vi and added a specific panelresize_tdms.vi for this improvement. panelresize_tdms.vi requires more than 9 elements.

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

LabVIEW 2013 SP1 Compile Worker Fails

Hello,
after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
At the Moment I hav not Idea what to do. Perhaps someone can help.
What does I have to do to convert my system back to the Version 2013?
Attachments:
FehlermeldungCompileWorker.jpg ‏41 KB
ErrorwhenstartingFPGACompileServerConfiguration.jpg ‏15 KB

dfschunk,
Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
Go to Control Panel >> Programs and Features and select National Instruments Software.
This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

Windows 8 and Labview 2013 FPGA

I installed Labview 2013 including the FPGA design suite on a Windows 8 (x64) host. I was surprised to see Windows 8 on the list of supported OS as I was aware that up to this day no Xilinx design suite supported Windows 8.
But as a matter of fact it didn't took long before I hit:
ERROR: Simulator:861 - Failed to link the design
following this tutorial while clicking on check syntax (using one of the VHDL file provided with the tutorial). The error is clearly linked to a lack of Windows 8 compatibility from the XIlinx tools running underneath. Is there a known workaround? Thanks.
Solved!
Go to Solution.

That I could do but Linux is not listed here ... but Windows 8 is listed as supported for the farm server and not for the development environment. Isn't is the other way around? On top of that it looks like we should read GB instead of MB for the farm toolkit.

Labview 2013 error 1304

Similar Messages

Maybe you are looking for