dsc 8.2.1 cannot find files with built application

[Kenny_K]

I am building an application using the DSC 8.2.1 with LV 8.2.1.  I am running into the problem where I go to start the .exe and I get asked for varxnode.xnode and a ton of other files.  It feels like I have to copy almost all of my labview development folder over to get all the vis required, which is VERY tedious and will make for a huge .exe.  I am sure I am doing something wrong.

My program is using Fieldpoint 5.0.1, DSC 8.2.1, and LabVIEW 8.2.1.  In the .exe I have debugging enabled (I get an error that the vi became broken when I try to disable debugging.), Enhanced DSC support (I read that I need this enabled to use the netowrk published shared variables).

THanks for your thoughts.

[Coal_Man]

Kenny,

In order to eliminate the problem, you will probably want to disable enhanced DSC support.  Here is a description of what the Enhanced DSC Run-Time support actually does:

Enable Enhanced DSC Run-Time support (LabVIEW DSC Module) - Enable this feature if your application uses VI server refnum (green) methods and/or properties to programmatically modify a library file. If your application uses the VI server refnum methods and/or properties to programmatically modify a library file and you do not enable this option, then those methods and properties will return errors when run from the built executable. You do not need to enable this option if your application uses the online (purple) variable refnum properties to manage processes and shared variables. You do not need to enable this option to programmatically deploy or undeploy a library file. Enabling this option will increase the size of the built executable and reduce start-up performance of the built-executable and should be enabled only for applications that use the VI-server refum methods and properties for modifying library files.

If your program is not programmatically modifying libraries using the VI-server refnum methods, you will probably not need that support.  However, if you are, you will need to install the DSC Run Time System onto the machine.  There is a KB on this topic here:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019MECSA2&l=en-US

I hope that this helps.  Have a great day.

Regards,

Message Edited by Coal Man on 05-16-2007 10:19 AM

[Kenny_K]

Ok, I am progmatically changing the library files while the program is running, so I need to have the Enhanced DSC enabled.

If I am running this program on a computer where I work (but not on the development machine) looking at the KB you sent, I need to buy a DSC run time liscence so I can get the DSC run time installer.  Is this correct???

[Coal_Man]

Kenny,

Yes that is correct.  The DSC module comes with a single run time license, but to distribute an application, you would need to purchase a license for each machine.  The purchasing site can be found here:

https://www.ni.com/en-us/shop/product/labview-datalogging-and-supervisory-control-module.html?partNu...

Have a great day.

Regards,

[dwb]

I am running into a similar problem, but I have the runtime license installed on the machine running the exe's. My program exe is running normally for

8 hours to 4 days with no problem, then suddenly the program becomes non responsive.  This is bad!!!  I have the error system turned on and no

errors are thrown during these events.  Are there other reasons that I am not aware of.  Please Help!

DB

[Jennifer_R]

Hi DB,

Does the executable hang when it runs on the development machine?  You may want to try creating a debuggable executable if the program only freezes when it is an executable.  Have you seen similar behavior with other exe's, or just this particular application using DSC?  What is the CPU usage when the executable is running and when it hangs? 

[dwb]

Jennifer,

I have tried to run it on the development machine and it does not seem to hang. I have since my last reply found a thread that explained that I should turn off

the Enhanced DSC feature when creating the exe.  This has worked as far as the exe looking for files on the non development machine. It no longer requires

these files and the program operates normally.

After I installed this, it ran 16 hours of production and then the program froze.  I looks as if it is only this program because the other 2 NI exe's are still running and

functioning. 

The debugging has been installed with the exe and when the program froze, there was no error message or any help about why it quits?????

This is the only exe I have trouble with and it is the only one that includes the DSC variable list and such.  Also, the computer usage / ram / processor

ect. all seems normal.  Nothing seems out of the ordinary.

In order to get this program to work, all I have to do is shut it and reopen.  I works fine until the next freeze many hours from then.

I am starting to believe that there is something wrong  with the DSC runtime 8.2.0.

Doug

[Jennifer_R]

Hi Doug,

It seems from your post here that unchecking Enable Enhanced DSC Run-Time support has eliminated the problem.  If so, that's great.  As Brian's post above mentions, you only need DSC support if you are using VI Server to change a library programmatically.  Otherwise it is unnecessary and can increase executable size and decrease performance.