LabVIEW 8.6.1 Installation Builder Crashes Windows 7

Hello, my very helpful friends. I have what I think to be a rather complicated issue and for which I've run out of ideas. Recently, I had to go through the dreaded enterprise wide Windows 7 upgrade. Upon completing that slog, I reinstalled LabVIEW 8.6.1 onto my machine by going to the distributions folder and installing each piece one at a time. After completing this process, I opened a pre-existing project (stored on a separate server) which had some pending changes in a couple VIs which needed to be incorporated into the executable and installation builds. The executable build worked without a hitch, but when I attempt to build the installation, I get most of the way through the build, but then it crashes Windows 7 via the blue screen once it gets to this point in the build:
This is at the part where the progress bar stops proceeding for a minute or so. I've tried deleting the installation and executable builds from the pre-existing project and recreating them, but that didn't work. I've also tried completely reconstructing the project from scratch to no benefit either. I've been able to succesffuly build both executables and installers in other projects since upgrading to Windows 7 so it seems particular to what's going on in this project. The only other bit of information I can think of which might be useful is that every now and then, building the installer only crashes LabVIEW and not full Windows 7.
Any ideas or suggestions are appreciated. Thanks in advance!
Andrew

I never tried using this, but one of the options you could consider...
http://windows.microsoft.com/en-us/windows7/install-and-use-windows-xp-mode-in-windows-7
TailOfGon
Certified LabVIEW Architect 2013

Similar Messages

Labview 8.5 installer build *.exe wrong date code

In Labview 8.5 application installer build *.exe has a date code of 7/17/2007 even though it was built today. It will not update even after deleting it. Is this a known bug? SS

Hi SS,
The Date Modified property of setup.exe shows the date the MetaInstaller was built. This was true in earlier versions of LabVIEW as well. It was reported to R&D (# 3T87DAP4) but was determined to be expected behavior. The actual date and time the installer was built can be determined by looking at the properties of \bin\dp\install.msi. Feedback is always appreciated, so please feel free to create a product suggestion if you think this should be changed.
Jennifer R.
National Instruments
Applications Engineer

Labview 2012 Installer builder issues with Windows 7 64 bit

I have a clients project application program I am working on and am having a lot of trouble getting installed applications to work on Windows 7 properly. The Labview Installer sets the default installation directory to "c:\Program Files\" on Windows Xp and on Windows 7 64bit this defaults to "C:\Program Files (x86). When I install the application on Windows 7 and run it, because Windows 7 64 bit unreasonably protects this directory and every folder under it, if you try to write file to any subdirectory under it (like a reports directory), windows 7 will not let the file write to the directory and the file(s) disappear and you get permission errors. This has been difficult to address. Even logging in as administrator, I have difficulty changing the folder permissions. In addition, when I am in the file write process, if the default directory is coded to come up in the file Open/Save dialog, will not properly
go to and display these protected directories. So thinking that OK, I'll just chage the install directory to something direct to the C: drive and not the Program Files (x86) directory, so I have better control of the folder permissions. Now the Installer build gives errors. It built, but the install fails. Looks like National did not test this for Windows 7 very well. I have run into just about every issue possible with Windows 7 and Labview. Clearly Labview was not very well tested with Windows 7 6 bit. I do not have the Internet toolkit added to the application, only the VISA 5.2 driver. Anyone else having application issues with Labview and Windows 7 and have ideas how to work around this??
Attachments:
BuildErrors.txt ‏11 KB

It's no NI's fault and has nothing to do with 64 Bit either. It is something MS changed starting with Vista, namely tightening security of the whole system to a similar level as was usual on more professional OSes like Unix 20 years earlier. A user has not rights anymore to write into the location where applications are installed. This is for one reason to protect installed applications from being modified by malicious code.
Instead every application should write its runtime data in one of the user writable loacations such as the user's Documents directory for data files, or in the user's or the machine's configuration directory for configuration settings. For single installations you could always set the directory which your application got installed into to be user writable by changing the rights of that directory afterwards but for applications that get installed on normal user computers this is a VERY hacky and discouraged move. Same about installing your application into the root of your system drive. I think it was an oversight by MS to not protect that directory too from user modifications, but was most likely unavoidable to allow DOS application installations to still work.
LabVIEW has functions to retrieve a whole bunch of those preconfigured and user writeable locations and you really should change your application to make use of those locations, instead of trying to write into the installation directory or installing the application into the root location of the system drive, if you want to be compatible with Windows Vista/7/8.
Windows 7 also requires for a number of actions such as installing programs or drivers so called elevated rights. This means that even if you are logged in as administrator you have to explicitedly provide the admin password again to be able to perform the action. This can be done by starting the program as administrator, when this is available in the right click pop-up menu, and is also sometimes done automatically for applications that Windows determines to need those rights such as setup programs for installations.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Labview 2009 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

Labview logging program crash windows after 2 days

I am using Labview 8.0, and running the executable the program. What this program does is that it acquires data and then writes to hard drive. Each set of data is small but it writes also every second. It will create a new file every day so the file does not get too big.
After 2~3 days running, it crash windows. I think it somehow used up all the resource so the windows would not even response any more. And we need to run this program continually for at least one month.
So is this a memory leak problem of the executable program generated by Labview app builder? or could that be Labview does not release memory after it writes data to the file, and eventually used up the resource?
any suggestions?
Thanks

It is on a laptop with win xp, 1GB Ram. each data is only 40~50 bytes. The concatenate strings does not duplicate in memory, right? what about build path and open file? Do I need to close the file inside the loop? It is a very small program so I attached a screen capture here.
I am going to let it restart again and check memory usage tomorrow.
Thanks,
Attachments:
screen shot.gif ‏36 KB

Installer build error code-21 Labview 8.6.1

While attempting to build an installer I get an error code -21. What is the error and how do I correct it?

I also have this problem. The executable build itself works correctly, but the installer fails to build. There are a number of DLL dependencies, but they are all included and present in the build and in the installer Source Files. I put CDK.EnableLog=True in my LabVIEW.ini and logged the error from the installer build process. Here is an excerpt from the relevant section:
    [LOG ON] Fri Apr 30 13:46:02 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\MyPrograms\MyApp_Working\Install
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Fri Apr 30 13:46:02 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Fri Apr 30 13:46:02 2010
    [MDF END] Fri Apr 30 13:46:02 2010
     Closing MDF.
I've also tried the same with a simple test application and it build/installs correctly, so I know it is my project somehow. One notable difference is that I previously had namespace conflicts in the executable build that were resolved by the following these instructions:
http://digital.ni.com/public.nsf/allkb/47272B69E2C167DB862574AC006A258B?OpenDocument
I hope someone can help. I need to deploy this application soon.
Regards,
- Ray

LabVIEW Run-time Engine 7.1.1 installation failure on Windows 7 SP 1 32-bit

I am attempting an installation of LabVIEW Run-time Engine 7.1.1 on my Windows 7 SP1 32-bit OS computer and the installation hangs. This happens near the beginning. Is there a compatibility issue? The window does not have any error messages. It says: "Updating System, The features you selected are currently being installed." The progress indicator blinks periodically, but does not move forward. Please help. Thanks!

I recently tried to install the LabVIEW 7.0 runtime engine on my Windows 7 (64 bit) machine to try out an old software. Ended up removing it quickly again, since any LabVIEW version I started up after that, including LabVIEW 2013 showed an installation dialog on startup about (updating installation information, please wait!).
Basically there are so many possible problems why it could fail. Apparently the runtime engine installer had played with some other NI component that he had no idea would ever exist when it was created and caused that component to always think it needed to update itself to finalize its installation. In your case it could be anything from a missing Visual C runtime version framework that the installer simply expects to be present but doesn't since Microsoft has in the meantime released about 5 versions of Visual C and doesn't install all runtime versions anymore on newest Windows. Or it could be a conflict with your hyper-duper .Net Framework 4.5.x.y that the installer does not be prepared for. Maybe that or something else was not present on your 64 Bit machine where you could install the runtime engine.
Basically the reasons for the install to fail are legion, and trying to figure it out is always more hassle than moving on and let old software be old software.

Labview executable installer cannot find windows favorites

When attempting to install an LabVIEW executable, using the Installer created with LabVIEW, before copying any files or making any changes to the local PC, the setup.exe queries for the location ‘My Favorites’ from the registry (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Favorites). If this has been moved to a mapped network drive, the setup will error saying that it is unable to access this location. Using Sysinternals Process Monitor, the setup.exe process does not try accessing this location.
Thanks in advance for any help
Inigo Rotzer

mikeporter wrote:
But why have favorites mapped like that in the first place?
Possible reasons:
1) Internal IT procedures
2) floating user account setups across the entire network
It's not uncommon to do these things but I have found to many problems with this also outside of LabVIEW to find it a practical solution.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Installer build: When run, error: Windows can't open this file xyz.vi

Hello all, I've taken my vi. I"ve created it as an executable. I've taken that...and made an Installer project... This is with LV 2011, and installing to Win7. The installer seems to work fine...but when I try to run the application from the start menu, I get a windows error, saying it doesn't know what to do with my file xyz.vi...that it needs to know what application to open it with....? Any ideas what to do here? The installer seems to install the NI runtime engine just fine...? Would this be due to, on the Installer builder...setting the vi to be read-only and hidden? When I'd done this a previous time, I believe it all worked then... Suggestions? Thank you, cayenne
Attachments:
screen_shot_windows_error.jpg ‏35 KB

Please disregard...I found the problem after going through the older working one....
Late nights and working two jobs...you start to overlook things.
FOr the dependency, I'd put the vi instead of the exe of the vi.....that did the trick.
Thanks all,
cayenne

Why will a stand alone executalbe with an installer work on windows 2000 and crashes on windows xp professional?

When I run the setup.exe file on a Windows 2000 system it installs properly, but the same file run on a XP Professional system I get an error stating Fatal Error: Installation ended prematurely because of an error.
See here for more information on the specific installer I'm trying to use.
In fact I get this error for any stand alone executable I try to install on any XP machines. I am using LV 7.1. Is there a way to manually install eve
rything?
Thanks

Sure you can Install a lv application manually. just copy the exe-file,
support files in a folder. For the runtimeengine just copy the file
lvrte.dll in the folder of your application or in the windows system folder.
Hope that helps, Niko
BB Herman wrote:
> Why will a stand alone executalbe with an installer work on windows
> 2000 and crashes on windows xp professional?
>
> When I run the setup.exe file on a Windows 2000 system it installs
> properly, but the same file run on a XP Professional system I get an
> error stating Fatal Error: Installation ended prematurely because of
> an error.
>
> See
> HREF="http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=50650000000800000...
for more information on the specific installer I'm trying to
> use.
>
> In fact I get this error for any stand alone executable I try to
> install on any XP machines. I am using LV 7.1. Is there a way to
> manually install everything?
>
> Thanks

Sometimes the Flex Builder design window crashes

Sometimes the Flex Builder design window crashes in that when
you click on components, you don't see the usual outline transform
box out side the component you clicked on. Also things like the
toggle button bar doesn't switch the viewstack. I have no errors or
warnings in the problems windows.
Any ways round this?

Actually I found the answer to my question. You can find it
in my blog.
programmatic
skinning in Flex Builder Design view

Labview 2010 error during exe build active x control

During the build of an exe of a labview vi, I get the following crash ( see attached jpeg). It has something to do with the activex control that is used in the vi. The activex control is registered with windows and functions properly. Any ideas?
Attachments:
TCAS DISPLAY ERROR.JPG ‏209 KB
TCAS Virtual Display 32 bit.vi ‏19 KB

Here's a Knowledge Base article that walks through a few things that you could try to prevent these Access Violation Errors.
Could you try building this executable on a different computer to see if it's related to that specific machine or installation of LabVIEW? If you find that it does work, it would be a good idea to do a reinstall of LabVIEW on the computer throwing this error.
When you said that you couldn't post the ActiveX control DLL, would the forum not let you post this? If that's the case, you can put your files into a .zip file and include an obvious filename (example: TCAS Error.zip ). Then upload the file to our FTP site at: ftp://ftp.ni.com/incoming and we can take a look at it that way.
I find the windows ftp the easiest ftp client to use. Just open windows explorer by pressing windows key+e then type the address into the bar at the top. Then just drag and drop your files in to the window.
Regards,
Austin S.
National Instruments
Academic Field Engineer

Cisco VPN Client installation freezes on Windows 7

Hello,
I am in need of some help installing the Cisco VPN Client on a Windows 7 workstation.
Here are some details:
Cisco VPN Client Version: 5.0.07.0410
Operation System: Microsoft Windows 7 Enterprise, 32-bit, version 6.1, build 7600
PC Hardware: IBM Thinkpad T42, Type 2373-7WE
Issue Description:
I attempted to install the Cisco VPN Client on the computer with the local administrator account in Windows 7. The computer was given a clean installation of Microsoft Windows 7 Enterprise (Existing HDD partitions were deleted and formatted). After the OS installation, I installed the network driver via Windows Update, and proceeded to run the installation for the Cisco VPN Client. The installation apears to proceed smoothly until the installation progress indicator reaches the point where it states that it is installing the "Deterministic Network Enhancer." Shortly reaching this point, the Windows CPU Usage monitor reaches 100% and the operating system freezes.
I have tried the following actions, which failed to successfully install the software:
a) Installing Cisco VPN Client 5.0.00.0340 produced the same problem.
b) Reformatted the hard drive, installed Windows 7, and tried to install the Cisco VPN Client again, but failed.
c) Used Windows 7 System Restore to restore OS state prior to the installation of the Cisco VPN Client. Then, ran Citrix's winfix.exe tool. After that, I ran Citrix's dneupdate.msi program for 32-bit Windows operating systems, but that also crashed the OS mid-way through the installation/update.
d) This URL from Citrix (http://www.citrix.com/lang/English/lp/lp_1680845.asp) suggested changing a Windows registry key, then try re-installing the Cisco VPN Client. However, that did not work.
I am at a loss as to how to resolve this issue. If anyone can provide some suggestions or a solution to this issue, I would greatly appreciate it.
Regards,
Samson

Welcome to the forums !
The only version of 10gR2 that is certified/supported on Win 7 Pro or higher is 10.2.0.5. Pl see this related thread for further information
Re: Oracle 10g 64 bit install on Windows 7 platform
http://download.oracle.com/docs/cd/B19306_01/relnotes.102/b14264/toc.htm#CHDFHIEA
10.2.0.5 is only available on My Oracle Support, access to which requires a valid support contract purchased from Oracle
HTH
Srini

Form Builder crashes whenever I try to run form locally

Hello,
I am using Oracle Developer Suite 10g (Forms 9.0.4.0.19) on Windows XP SP3, IE8.
Whenever I try to execute (run) form from Forms Builder locally Forms Builder just crashes (get error: Oracle Forms Designer has encountered a problem and needs to close ).
Any help please
Best regards.

First, the Builder crashing has nothing to do with what browser you are using. The Builder crashing is a Builder issue. It is possible that the Builder is crashing due to a corrupted installation or permissions issue at the OS level. It could also be a bug. So, as I mentioned already, it may be time to upgrade to a more 21st century version of the product or at least consider applying a current patch to what you have. Patches are only available to customers with access to MyOracleSupport.
https://support.oracle.com

Application builder Error: Windows SDK function returned an error. (Error code -12) *** End Error Report

try to create an installer in Labview 8.6. The build fail and I got this message.
CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> CDK_InstallerConfiguration_Editor.vi
>> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'NI LabVIEW 8.6.1 Datalogging and Supervisory Control Module' from:
D:\software\application\LabView\NI.LABVIEW\NI-Labview 8.6.1 DSC Module\ to: C:\Documents and Settings\Lidaoling\桌面
\Builds\generate waveform\My Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
Creating merged database...
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
Done building deployment

Solution

LabVIEW 8.6.1 Installation Builder Crashes Windows 7

Similar Messages

Maybe you are looking for