LV 2009 SP1 EXE Builder issue

Hi Guys:
I found that the exe file built from LV 2009 SP1 can be easily extracted by WinRAR , i can see all the main or sub vi , is this a bug? or a settings risk? I haven't found the same problem in LV 8.6 ,
thanks
Solved!
Go to Solution.

I do not think you should think to much about it. One of the first discussions about it is here http://forums.ni.com/t5/LabVIEW/decompiling-2009-executable/td-p/991662. It is correct that they will be able to extract the VIs But they will not be able to see any more than you show in your program.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Similar Messages

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.

2009 sp1 slow build

Trying to build my application after I just upgraded to sp1 on LabVIEw 2009.
It seems to take a long time, while using a lot of cpu power.
Progress is very slow. Hard drive is not being used intensly.
Running the same on the 2009 f2 version. Building from the same sources.
Very slow as well.
I'm new to the performance of the build feature in 2009. Coming from version 7.1.1
And I'm very surprised on the difference. Why does the build take sooooo looooonnnnggg on the 2009 version(s)??
We build smaller apps before on 2009, and did not seem a big deal. But this bigger application.
And then after about 15 minutes, I get an error message:
Error 8 occurred at AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
So this is running with the 2009 f2 version on XP pro with 1Gb of ram. And for the 2009 sp1 version on windows 7, with 8Gb of ram....
So do not expect any memory issues with the SP1. Could this be a windows 7 x64 issue?
Anyone any experience with building larger applications?

Hello Everyone,
We have observed that building executables in LabVIEW 2009 is slower than in 8.6. In most cases it was about 10 to 20%. However, in some larger builds we have seen almost a 3x or 4x slow down. This large slow down has been reported to R&D for further investigation (CAR 205343). In the case that was reported to us the build was about 8000 VIs and took 2GB of memory to complete.
There wasn't a difference between LabVIEW 2009 and 2009 SP1. The slow down occurred between 8.6.1 and 2009. Does your slow down occur between 2009 and 2009 SP1?
Message Edited by Jon S. on 03-09-2010 08:42 AM
Regards,
Jon S.
National Instruments
LabVIEW R&D

LV2010 SP1 Installer Build Issue- Cannot find the file it need on requesyed disk

I am migrating a project from LV8.6.1 to 2010SP1 and had issues building the installer that I was finally able to overcome, but something is amiss with the process.
Brand new development PC, running XP SP3, fresh install of LV2010SP Dev Suite and also installed VDM2010 SP1 (even though the project does not use any vision modules).
-          Copied 8.6.1 project to the PC, did a mass compile of it and built the exe from scratch without issues.
-          Now it’s time to build the installer from scratch. Additional Installers were:
LV2010 RTE, MAX 4.7, NI-DAQmx Full App Devel Support 9.2.3, and NI-VISA 5.03.
-          Get the message that it will need some disks to build it which I have on hand:
Dev Suite DVD#2, Drivers DVD, and VDM DVD (huh, why VDM?)
-          The installer build progresses through the first two disks fine but will not find the files it needs on the VDM DVD (it is looking for “NI System Components”).
-          Installer build bails out with a message box and no installer is created (1st attachment). The installer logs are also attached.
-          Try the build process gain, same result.
-          Copied the VDM DVD to my hard drive and point it to that folder to get the files, same result.
-          Try again saying I don’t have the disks on hand. It lists some alternate disks to use but to get all the files it still wants the VDM DVD to complete it. Not much use, the build still fails.
-          Try one last time again selecting that I don’t have the disks on hand. I now notice that the folder the VDM was copied to on the hard drive is an option to select. Select that one and lo and behold the installer is built successfully.
So I guess it boils down to:
            - Why does it need the VDM DVD when there are no components of vision used?
            - Why can’t the installer find the files it needs on the VDM DVD or a copy of the DVD on the hard drive?
            - Why will it only work if I choose that I do not have the disks and point it to a copy of the DVD that resides on the hard drive?
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
Attachments:
MessageDuringVDMCopyForInstaller2010.JPG ‏127 KB
TowersSPCv225Installer_build.log ‏3126 KB
TowersSPCv225Installer_edit.log ‏915 KB

Che:
It gave no specific indication of what it was looking for, the only message that came up was in the screenshot jpg I originally posted.
The only other vague clue I had was it needed NI System Component from the VDM DVD.
Does not make sense that it required the VDM DVD since there were no vision components in the project. I presume it would have taken VISA off of the Dev Suite DVD's.
I can't replicate the problem since I had the build cache the system components required for the project. I'd rather not start deleting folders at this point since I have a viable installer at this time (after many hours of troublshooting expended).
Thanks
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Labview 2009 SP1 - Create exe option does not appear

Hello everyone,
I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other computer with the appropiate labview run time engine).
I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
Thanks for advance!
Much thanks for your time and dedication!

I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
The best solution is the one you find it by yourself

Application builder for Lab View 8.6.1 , 2009 SP1 and 2010 SP1

All 3 Versions seem to have huge flaws. With 8.6.1 When trying to build and application I get a duplicate name error and the application won't work. With 2009 SP1 I get Error 1003 broken VI when I have no broken VI's. Again Application won't work! With 2010 SP1 After the application is built for some reason lab view can no longer find the Excel sub VI's no matter how I place them in the build. And again application doesn't work. With all 3 versions the Vi's and over all programs work perfectly in the development environment. The application builder seems extremely flawed.
I would currently like assistance with 2009 SP1 problem the Error 1003 broken VI. I have reinstalled and rebooted my machine several times , tried including as much as possible in the build and still get the error about a broken VI. That works perfectly in the development environment. Please HELP?
Thank You
Attachments:
Broken VI.gif ‏8 KB

Scott,
Good afternoon, I'm sorry to hear you are having problems working with the application builder, hopefully I can help you get to the root of this problem.
What steps have you taken to try and resolve the error? This error can be caused by a variety of things. The link below details 8 potential solutions that may help resolve your error.
http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument
I would recommend starting with these steps. Let me know if any of these solutions work for you.
-Nick-
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

LV 2009 SP1 Build Error NI

While trying to make a build on LV 2009 SP1, I get this error:
The build was unsuccessful.
An error occured while saving the following file: Sample.VI
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference: Error 1 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Note I do not use any GPIB. Also when I build the project on VL 2009 (no SP1) on a different machine, I get no errors. Any ideas?
Solved!
Go to Solution.

Ugh. I've seen this in 2009 as well as quite a few others here. There seems to be no real explanation or consistent solution to this error. 1st thing to try is to remove all boolean constant-driven case selectors. For some reason the compiler gets confused with those - sometimes. See how that goes. Eventually this problem seems to resolve itself after a few days of development. That's been my experience. Sorry I can't be of more help.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

Avoid MathScipt Comments in EXE, Build & Run Problems - NI Please Fix these Bugs!

Hello,
After 4 days of intensive work, I have finally found the solution for two major MathScript Problems:
1) Mathscript Comments are included in your EXE File !!
    - Yes, if you do not watch your steps, the EXE will include all your % Mathscript Comments!
2) Problems building, but even worse: An app that builds with NO Error and NO Warnings will not RUN and creates the following misleading Erro Message:
    "The VI is not Executable. The full development version of LabView is required to fix the errors"
    With absolutely NO hint to what VI have the problem.
I have made myself an internal note how to avoid this problem. I am using LabView 2009, 2010 DS1 Release (I think this is 9.01) under WInXP SP2.
Rather than retyping everything, I will post the full text of my Notes below. I also mention several other LV BUG in this note, so pleae read carefully.
One is the TagSrv Error that occurs in LabView 2009 if I programatically deploy Shared Variables under the WinXP Development Environment. After this problem has occured, it will occur every time I restart XP, and in essense I have to restore to before I did this (thanks Nortong Ghost !!!).
Below you can find the full unabridged version of my Build, Run and Bug Notes for LV 2009 / 2010 DS1 (9.01). Hope they can be helpful to my fellow LabView programmers!
2010-07-03:
Building under LabView 2009 / 2010 DS1 Release (version 9.01)
Follow the steps below:
a) To successfully build an EXE that also runs
b) Avoid that MathScript Comments are included in the EXE !!!!!!!!!!!!!!!!
Before Building:
I) Recompile All by pressing Ctrl+Shift and pressing the RUN button on the Application_References.vi
   Then Save All (about 1200 Vis are saved)
II) Make Sure that NO User Defined Mathscript (and Mathscript Nodes?) define Empty Functions:
    This seemed to cause the following problem with the built EXE: The main VI will be broken, and a dialog reports:
    "The VI is not Executable. The full development version of LabView is required to fix the errors"
    MathScitp BUG: Empty Functions causes no Build Errorm but RUN Error:
    The following User Defined MathScript .m files are candidates:
    log_write() and log_clear() whith do_log_write() and do_log_clear() commented out, these functions are empty.
    When calls to log_write() and log_clear() where removed, the problem above vanished !
Building the EXE:
1) Additional Exclusions:
-"Disconnect type definitions": YES
- "Remove unused polymorphic VI instantces": YES
- "Remove unused members of project libraries": NO (do not know if this is important)
2) Advanced:
- Enable Debugging: "NO"
3) Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE if you use the New Build File Layout:
   IMPORTANT !!!!!!!!!!!!!
   Advanced:
   "Use LabView 8.x file layout": YES !!!!!!!
   Using the new layout, causes ALL COMMENTS FROM USER DEFINED MATHSCRIPT .M FILES TO BE INCLUDED IN THE .EXE !!!!!!!
4) BUG: DSC Reference Problem in LabView 2010 DS1 release:
   In VI Deploy_Shared_Variables.vi we deploy alle Shared Variables using the "Deploy Libraries.vi" which is a part of the DSC option.
   As long as only deploying of Variables is used, using this VI should NOT require any DSC Runtime license.
   We have used this before with no compilation problems.
   However, starting with LV 2009 SP1 (or was it the DS1 2010 upgrade) LV will start nagging us to resolve references to tens of VIs
   in the DSC lib file ! Solution: Used press "Stop" on the dialog, and the Build will succeed and the EXE will work !
   Optionally, we could use the following Invoke node for the deployment:
   (see: http://digital.ni.com/public.nsf/allkb/04D9A85B6967EE87862571140065EEC6). Excerpt from this description:
<<Right-click the block diagram to bring up the programming palette and go to Programming»Application Control and place the
    Invoke Node on the block diagram. Using the hand tool, click Method and select Library»Deploy Library>>
5) LabView BUG: Do NOT RUn the Application under the WIn XP SP2 Development Environment if the APP Deploys Shared Vars:
   This will cause the Dreaded TagSrv Error: "TagSrv.exe: This application has requested the runtime to terminate in an unusual way".
   After this Error has occured, it will reoccur each time WinXP SP2 is restarted, and (Network) Shared Variables will NOT work any more!
Geir Ove
Attachments:
LabView_Tagsrv_Error.jpg ‏26 KB

Hello Geir,
I have tried to reproduce the behavior you are seeing where .m file comments appear in the final built executable. However, I am unable to do so using LabVIEW 2009 SP1. I have a caller VI with a MathScript node that calls the adder function in adder.m. The contents of adder.m are as follows:
% ADDER This function adds 3 to its input variable
%   y = adder(x)
%   INPUT: x
%   OUTPUT: y, equal to x + 3
function y = adder(x)
y = x + 3;
I have configured the build specification as you mention in steps (1) and (2):
Additional Exclusions
- "Disconnect type definitions" Yes
- "Remove unused polymorphic VI instances" Yes
- "Remove unused members of project libraries" No
Advanced
- "Enable Debugging" No
At first, I did not include the adder.m file in the project. I built the application and was not able to find the text "adder" anywhere in the EXE. Then, I added the .m file to the project and put it in the "Always Included" section in "Source Files." Again, I was not able to find the search text in the built EXE. In step 3, you mention
geirove wrote:
   "Use LabView 8.x file layout": YES !!!!!!!
but in the 5th post in this thread, you state
geirove wrote:
Compile using the new compile method ( Use LabView 8.x file layout": NO),
I have tried both settings in the Advanced section, but again, I am not able to find any comments in the EXE. I even added a call to the "path" function in adder.m. This puts a warning glyph on the caller MathScript node and generates different code. The EXE will return an unknown symbol error for adder (any VI with a warning glyph will not work in a built app), but I am not able to find any comments in the EXE. This project is attached below.
As for your other item with a broken EXE if you call empty functions, I am unable to reproduce this as well. I have taken the last attachment to your third post in this thread (the log_write function) and called it from the caller VI as well. The EXE runs just fine and I do not find any comments in this EXE either.
Unfortunately, there was a rather serious issue in the LabVIEW 2009 MathScript RT Module, where some internal MathScript VIs could become corrupted when building executables. Have you tried running the "Find Bad Instantiations" tool from this Knowledge Base article? Simply installing the SP1 version on top may not have corrected any VIs that may be corrupted.
Due to our difficulty in reproducing the issues you mention, could you modify the attached project or else attach a new project, appropriately configured, that builds an EXE with .m comments embedded in it? This way, we can uncover any minute details that we're overlooking.
Grant M.
Senior Software Engineer | LabVIEW MathScript | National Instruments
Attachments:
MComments.zip ‏186 KB

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

2009 SP1 Debug Deployment Only

I've install LabVIEW 2009 SP1 and it works fine but it indicates "Licensed for Debug Deployment only" on the opening screen. We use the Volume License Manager and it correctly checks out a Development License which is correct for me.
Is this something I should be concerned about? It doesn't seem to be constrained in any way, i.e. I can build executables.

Here they are. I'm "DC10020"
Attachments:
VLM_Screenshot.jpg ‏511 KB
NILM_Screenshot.jpg ‏227 KB

Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

Timer( ) resolution in CVI 2009 SP1

In the CVI 2009 SP1 Contents Help for Timer() function I find
The resolution is normally 1 microsecond. However, if you set the useDefaultTimer configuration option to True, the resolution is 55 milliseconds.
But if you click on the useDefaultTimer hyperlink, a new page is opened, where you can read that the resolution is 1 millisecond if you set useDefaultTimer to False.
Which is the right resolution?
I wrote my application considering 1 microsecond, but I found strange problems, and I think it is 1 ms.
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Hi vix,
Thanks for bringing those documentation problems to our attention.
1. There does seem to be a problem with a lot of the function prototypes in the .chm help in the CVI 2009 SP1 and 2010 versions, where an extra asterisk seems to have been added to a number of output parameters. We'll fix this and post a corrected version of the affected .chm files as soon as possible. In all these cases, the parameter data type as it appears in the Parameters section of the help topic is correct, as is the prototype in the corresponding function panel.
2. Concerning the timer resolution issues, the async timer resolution is in fact 1 millisecond, as confirmed by the GetAsyncTimerResolution function. But note that asynchronous timers are a library in and of themselves, and are not covered by what is discussed in the documentation of the Timer() function or the useDefaultTimer option.
The resolution of the Timer() function should be 1 microsecond, as of CVI 9.0 and later. The function documentation is correct. When that change was made, however, the documentation of the useDefaultTimer option was incorrectly not updated. It should say that "the performance counter timer provides a resolution of 1 microsecond".
You mentioned that you didn't think that the resolution of the Timer() function was 1 microsecond. If you run the following code, what do you see?
int     i;
double time[10];
for (i = 0; i < 10; i++)
    time[i] = Timer();
for (i = 0; i < 10; i++)
    DebugPrintf ("timer = %f\n", time[i]);

Exe build with database conn and report generation vi's?

I tried to build an .exe and learned the hard way that there are many things needed to be included for this to work. As is now my program is not working.
I wanted to get a list of necessary steps to make a successful build. Please correct me if I am wrong or missing anything:
1. For the report generation toolkit I must include a few support files (_exclsub.llb and _wordsub.llb)
2. For the database connectivity: I must follow NI's User guide by implementing the toolset build script function? Is there an easier way?
If there are any simpler ways to get this working please let me know.
Dev machine=vista LV2010 office 2007
Target machine=XP office 2007
Solved!
Go to Solution.

Thanks for the response,
Yes I have the runtime installed. I also got the program working correctly by doing the following:
LV 8.6 and greater-->
1. added two folders to the project from the project explorer menu.
      a. Utilities folder
      b. LVClass folder
2. during the .exe build I had to:
      a. add LVClass folder to always include in source file settings
      b. browse in the Utilities folder to NIReportLLB folder and add that to always include as mentioned above (note: if you add the whole utilities folder you will get a broken vi error when building it, even if you fix the vi it still didn't work properly for me so I just included the folder I needed for word/excel)
took about a day to troubleshoot and fix but the program is working as expected. Hope this helps someone else in the future.
Bernie

LabVIEW Run-time 2009 SP1

When I try to install LabVIEW Run-time Engine 2009 SP1 on a Windows 2000 machine I get an error message that states "Windows XP SP2 or greater required"
The compatability chart http://www.ni.com/labview/os-support/f/ states that LV 2009 is supported on Windows 2000. What gives?

Do you have administrator privileges? Also, do you have any security programs installed on your computer that could hinder the installation?
Applications Engineer
National Instruments

[Help]PT 8.51 pscfg.exe config Issue

Hello,
Recently, I just install a PT 8.51 system on the same box (a Virtual Machine). (Platform: Win2008R2x64, MSSQL2008R2, PT8.51 Media Pack, HRMS 9.0)
Everything works fine, but just the pscfg.exe configure issue for Application Designer to launch.
During the installation, the pscfg.exe can be updated and setup to correct value, for example, PS_HOME field, Cache Folder, Default Profile Edit, etc, and can be saved. This works fine as expected during installation.
After the installation complete (including Online Doc Library deployment), rebooting the server, test some created windows service if work proper, then reboot again, manually startup App Server, Prcs Server, Web Server, PeopleBooks, all works fine.
But when I try to launch the Application Designer to view some objects, it prompted me an error message something like this: variable %PS_SERVDIR% not found. Then I check the pscfg.exe setup, found that some field is clear out, for example, PS_HOME, SQR Bin, SQR Flag from Profile Tab, Cache Fodler is changed to some other value. However, even I update the value via pscfg.exe again, Apply & OK. Then Open again, the value is changed back without any of my updates. (I run the Application Designer on the same server as where DB, App, Prcs, Web Server runs.) [However, despite the error message, the application designer still can logged in. But the Cache Folder, Debug Trace log, etc file path will changed to somewhere else.]
Is there anyone of you having encountered this issue before or not?
Would you please help to give any advise on how to solved it?
Any response will be appreciated.
Thanks,
Saxon SI

What is the exact folder path you're extracting things to? I know that the setup.bat file in the disk1 directory doesn't like spaces in the path to the directory. If you extract the disk 1, disk 2 and disk 3 in for example C:\PSINSTALL\disk1 (and disk 2 etc.) you should be able to run the setup.bat. When you run the setup.bat you don't have to select the next disk, the installation will pick it up automatically.
If you still want to select it manually I think you have to select the parent folder instead of the disk 2 or 3. If you select the disk 2 or 3 folder the installation will not pick it up for some strange reason.

LV 2009 SP1 EXE Builder issue

Similar Messages

Maybe you are looking for