LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error building installer: this application has requested the runtime to terminate it in an unusual way

Solved!
Go to solution

Hi,

 

I build an appliction using LabView 8.2 with Report Generation Toolkit for MS Office V1.1.1 on a WinXP SP3 system without any errors. When I try to build a coresponding Installer, I got the following error message:

 

This application has requested the runtime to terminate it in an unusual way.

 

Can anyone help me????

 

 

0 Kudos
Message 1 of 6
(5,769 Views)

Hi Gunnar,

 

Good Morning and I hope your well today. Thanks for your post onto the NI Discussion Forums. 

 

There are several considerations and potential causes of the error. I will try my best to cover some of the potential causes.

 

Firstly, you've suggested that the Report Generation Toolkit is being used:

 

When building applications with Report Generation Toolkit VIs, you must complete the following additional steps:

 

1. From the Source Files tab of the Build Application or Shared Library (DLL) dialog box, click the Add Dynamic VI button to add the following two VIs to the application:
– _Excel Dynamic VIs.vi in vi.lib\addons\_office\_exclsub.llb
– _Word Dynamic VIs.vi in vi.lib\addons\
_office\_wordsub.llb

 

2. If the application you are building contains the MS Office Report Express VI, you must add any Word or Excel templates that you use to the built application. From the Source Files tab, click the Add Support File button to add the template files to the application. By default, the custom destination for the templates is the same as the path that appears in the Destination directory field on the Target tab with a data subdirectory appended. Do not change the custom destination for the files you add.


For example, if you are using the basic Excel template with the MS Office Report Express VI, add MSOffice_RGT_Template.xlt to the application. The basic template files are located in the templates\Report directory.

 

Have you done this?

Could you please send an image of your project and your installer options?

 

The problem was that I use Office toolkit and it was not compiled with LabVIEW 8.2:
I found a forum where the toolkit wasn't complied for LabVIEW 8.2. Could this be an issue I wonder?
 
I mass compiled the complete directory c:\program files\National Instruments\LabVIEW 8.2 (it took quite a long time) and afterwards the directory lvjpeg disapeared.
 
Have you tried this?
 
Runtime to Terminate Error:
 
1. Have you been having any trouble with LabVIEW - crashes or bug installation?
 
I would suggest repairing your installation of LabVIEW and the toolkit(s) using the Add/Remove Programs.
 
2. Also would it be possible to try building an installer on another machine?
 
3. I have seen that not enough Hard-disk space can cause this error - what is the status of yours?
 
4. Are you using any other drivers such as DAQmx or VISA?
 
I hope this information starts to help us locate the root cause of the trouble your having, and if you could answer the questions above and try my suggestions that would be great! if you could also gather the extra information about your installer options that would also really help supporting the issue further.
 

 *edit:

 

5. Also the runtime error would suggest you've selected to include a runtime in your installer options - have you tried de-selecting this and see if it installer builds correctly? If it does, then we could then work on how to add the additional installer to your build. 

 

 

Message Edited by Hillman on 04-01-2009 10:01 AM
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
Message 2 of 6
(5,762 Views)

Hi James,

 

thanks for your quick answer!!! Good to have such a comfortable support!!!

 

1. Yes I'm using the Report Generation Tool Kit VIs and I has already included the Dynamic VIs to the project.

2. I'm not using a Report Express VI

3. I'm sure the toolkit is compiled for LabVIEW 8.2 (Application is running well)

4. There were absolutely no problems insatlling or running LabView on this machine.

5. I tryed to build the installer on another machine before, the problem is that I have no access to this machine any more ..., but I can say that the PC configuration (WinXp SP3, ...) was the same on that one.

6. Hard-disk space is absolutely no problem ....

7. Yes I'm using the DataSocket VIs within the program (should be part of the DAQmx)

 

In my opinion the project settings must be OK, because there are no problems building and running the application. Only when I try to build the installer LabVIEW crashes. For detailed information about the project- and installer settings see the screenshots below.

 

Hope this will help us to solve the problem...

 

Kind Regards

Gunnar

0 Kudos
Message 3 of 6
(5,744 Views)

Hi Gunnar,

 

Thanks for your kind words and I hope your well.

 

Also thanks for your detailed reply. 

 

I have two suggestions, 

 

1. Can you build the installer without the LabVIEW run-time selected?

 

2. LabVIEW has the ability to create a very detailed log of the events that occur when building an application or installer. To enable this feature, open up the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom of the file. Save the changes and close the ini file. The LabVIEW.ini file is usually located in C:\Program Files\National Instruments\LabVIEW X.X

  1. Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
  2. To find out where this temp directory is located, go to Start>>Run. Type in "cmd". Then type "set". This will return all of your computer's variable names.
  3. Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
  4. Navigate to this directory using Windows Explorer.
  5. You should see a file named "Name.log" where "name" is the name of your build specification. For example, you might see "My Installer.log" if the name of your build specification is "My Installer".
This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.

 

It could well be the installer can't find the correct location / or even that the file isn't stored on the system/correct path. 

 

If you could please try removing the additional installers and reviewing/posting the log that would be really helpful,

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
Message 4 of 6
(5,736 Views)

Hi James,

 

thanks for the info with the log file! The Application Builder couldn't find the Installer Files for DataSocket.

When I put in the distribution CD everything works fine !!!

 

The Problem is that I don't have the distribution volume all the time. So I  copied the DataSocket Installer files to my local disk. When configuring the Installer project I try to promt the new path for the installer files, but the application builder don't accept it (see attached file). Is there any way to install the additional installer files on the local disk (like the runtime engine installer files)?

 

Kind Regards

Gunnar

0 Kudos
Message 5 of 6
(5,717 Views)
Solution
Accepted by topic author Gunnar Jonas

Hi Gunnar

 

Firstly just save the contents of the disk to your computer. Then..

 

The local cache paths are stored in registry keys.  You can modify the registry through the following steps:

1. Select Start > Run and enter regedit
2. To create a backup copy of the registry, select File > Export from the Registry Editor window
3. Make sure the Export Range is set to All, and save the registry
4. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\ProductCache, find the correct key, and modify the path as necessary

 

Hope this helps, 

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
Message 6 of 6
(5,665 Views)