Including TestExec.ini in Deployment

We need to include TestExec.ini into a TestStand Deployment to allow TestStand to automatically login to the Windows System user. Unfortunately when we include our TestExec.ini in our TS build, running the resultant image gives us a strange ActiveX Error.
Our system runs fine without TestExec.ini in the build but doesn't automatically login to the Windows User, can we use a cutdown version of TestExec.ini that just contains the auto windows login bit?
Regards
Steve
There are 10 types of people in the world that understand binary, those that do and those that don't.

Steve,
I take you have a customised IO.
If you dont initialy have the testexec.ini file once deployed on your target system, then the file is generated using the default setting when you first run the OI application.
What is this the strange error you are seeing.
Do you use a third party installer or are you using the TestStand installer created by the deployment tool?
You might be able to run a sequencefile which setups up the login by teststand API call StationOption.AutoLoginSystemUser.
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

Deploying testexec.ini

All,
I've got a custom OI and process model that I am trying to transfer over to another computer, to do this I've created a LabVIEW installer from 3 source distributions and one application. I went with 3 source distributions because each goes to a different path.
The 3 source distributions are as follows:
- Source vis
- process model
- config files (StationGlobals.ini, Users.ini and TestExec.ini)
My struggle enters the scene when I try and specify what process model I want to be used. My plan was to do this by transferring TestExec.ini to C:\ProgramData\National Instruments\TestStand 2012\Cfg and hoping that TestStand took the changes; well TestStand does not seem to load the correct TestExec.ini, so my questions are as follows:
- Is there a better way to specify what process model I want TestStand to use?
- I do not delete the old config files from C:\ProgramData\National Instruments\TestStand 2012\Cfg, does that cause me a problem to write over them?
Thanks,
Bill
John 3:16

http://forums.ni.com/t5/NI-TestStand/Setting-Model-in-Deployment/m-p/2411312#M40822
Check this link.

Testexec.ini access denied...

Hi,
While running on a test station using the teststand deployment, TestStand randomly crashes by the end of the sequence execution and a pop-up appears to specify: testexec.ini access denied... More precisely, it crashes between the end of my test sequence and before the "PASSED"/"FAILED" pop-up appears... Afterward, the testexec.exe just crashes and kills all remaining execution as the application closes...
When I go to my \cfg files, I can found a file INI$$0.TMP and if I compare it with the Testexec.ini file, they are identical and with the same date/time....
I should also precise that, this morning, the issue occured after the 8th consecutive execution... Therefore, this is not a write/access permission issue... Anyway, I configured windows to provide the "FULL CONTROL" permission on my test engine directory / deployment directory (including the cfg dir) which is located to "C:\ATE_Teststand_engine\".
I really need to get this fixed as soon as possible... Is there a way to prevent teststand updating this file after each execution?
PC Configuration:
Win7 SP1
Teststand 2013 base deployment
Labview 2013 f2 runtime engine
Thank you for help!
C.

Hi jigg,
You right, my config files are located at "C:\ATE_Teststand_engine\Cfg\", but my station options are configured accordingly... Furthermore, as mentioned in the issue description, the problem occured on the 8th consecutive execution, so the files should be loaded properly...
«« Look in Configure>>Station Options>>Preferences tab. Is that set to your cfg folder? »» yes
Maybe some additionnal info:
I use the Sequential process model
I run 3 instances of the test, i.e. I pressed "Test UUTs" 3 times. However, when the problem occured, only 1 thread was terminating, the others were running my sequence...
I use a custom opertor interface, but based on the teststand simple operator interface.
Attachments:
StationOptions.png ‏40 KB

Use networked Users.ini in deployed simple user interface

I'm using the Simple LabVIEW UI that comes with TestStand 2014. I have customised it to my requirements, but have a small issue. I want to deploy the interface to numerous production PC's but cannot workout how to get the interface to use a networked Users.ini, at Login on those PC's. Does anyone know how to make the user interface use a networked Users.ini? I know that in TestStand 2014 you can use the menus Configure>Station Options>User Manager to tell it where to find a networked Users.ini. I don't know how to make the Simple LabVIEW UI do the same thing. Hopefully I've missed something obvious and will soon be felling rather stupid.
Thanks
Colin

Colin,
This setting is stored in TestExec.ini. You can deploy this by following this link: http://digital.ni.com/public.nsf/allkb/E5E4FEADEFE6023D862571590000C5CC
Here's another link:http://zone.ni.com/reference/en-XX/help/370052N-01/tsdeploysystem/infotopics/includingcfgfiles/
TestExec.ini is just 1 of many cfg files for TestStand. They all need to be in the same folder. Generally the ProgramData\National Instruments\<TestStand>\Cfg folder. The exception is Users.ini. It is the only cfg file that can be in a different location (as you have discovered)
So I recommend pointing to the users.ini on your development machine and then adding TestExec.ini to your workspace. Then you need ot put it in the Cfg directory on the deployment machine. Be careful though because there are a lot of other settings stored in that file.
Hope this helps,

Can't write to TestExec.ini

I had made some changes to a 1st level subsequence (one that is called by the main sequence) and ran some test and all was fine. Then I opened another 1st level subsequence to make similar changes. It opened but I got a message stating that TS couldn't write to TestExec.ini. That was because it was not checked out from ClearCase. Why did TS want to update this file at this time?
Inquiring minds want to know.......
Thanks,
jvh

Hi Larui,
When does this error occur? I've found a KB on error code -17205 that might help you out. It's listed below.
Problem
The NI DataFinder is indexing files on my machine (installs with DIAdem or LabVIEW DataFinder Toolkit or DataFinder Server Edition), and I sometimes receive errors -5001 and -17205 when generating XML or ATML reports from TestStand example sequences. I am able to generate HTML and ASCII reports without any errors – what is causing these errors?
Solution
An explanation of the cause of these errors is provided below. This issue (as described below) is fixed in the NI DataFinder 2011 when TestStand 2010 SP1 or newer is installed.
The NI DataFinder periodically indexes files in certain default directories, one of which is the National Instruments Public directory. When the DataFinder attempts to index a file, it grabs exclusive read access to the file such that no other process can read or write to the file.
When generating an XML or ATML report, TestStand obtains and releases write access to the file on multiple occasions when creating the file, writing to the file, adding/removing root tags, etc., and TestStand does not expect other applications to lock the file. By default, TestStand will attempt to generate a report file in the same directory as the sequence file being run.
You may encounter the above mentioned errors if all of the following apply:
You install a DataPlugin for TestStand XML or ATML report files
You generate an XML or ATML report for a TestStand sequence, such as a TestStand example sequence file
DataFinder is configured to index the directory where TestStand generates the report, such as the <TestStand Examples> directory.
To work around this issue, you can manually exclude a directory where TestStand generates reports from NI DataFinder’s list of Search Areas (directories to index).
The Version Selector application installed by TestStand 2010 SP1 automatically configures DataFinder 2011 to exclude files in the <TestStand Public> directory for all version of TestStand installed on a machine. Thus you will not encounter the above mentioned error when running TestStand example sequences if TestStand 2010 SP1 or newer is installed and DataFinder 2011 is indexing files on your machine.
I hope this helps.
Josh L.
Applications Engineer
National Instruments

Testexec.ini reload

Hi,
In my custom user interface, I would like to reload the TestExec.ini after it has been changed on disk.
I start the interface and ApplicationMgr. The TestExec.ini is then overwritten later on disk.
Is it possible to reload it without restarting my interface or applicationMgr?
I tried ApplicationMgr.ReloadConfigFile without success.
There’s no return value to tell if it was successful and the help about the command is very simple:
ApplicationMgr.ReloadConfigFile: Reloads the application configuration file from disk.
I would also like to have the confirmation that the application configuration files are actually all the files in the CFG folder.
Thank you.

To answer a part of your question, ApplicationMgr.ReloadConfigFile has nothing to do with TestExec.ini.
It doesn't relate to your original problem, but for more information about the ApplicationMgr config file, see ApplicationMgr.ConfigFile, ApplicationMgr.ConfigFilePath, and TestStand Reference Manual>>Creating Custom User Interfaces>>Persistence of Application Settings.

UI is ignoring stationglobals.ini and users.ini on deployed system

I have built a TestStand and LabWindows/CVI application, and used the deployment tool to deploy it to a workstation. I included the user.ini and stationglobals.ini (which contain my users/privileges and my station global values, respectively) in my workspace. When I install the app on the workstation, I see that these two files are deployed to the machine in the right place, but when I launch the full UI, none of my users or station global values are there. I'm currently stuck as to why the UI can't see my users and globals.
I also tried putting the entire cfg directory contents on the deployment station, but nothing changed.
Has anyone seen this, or better yet does anyone know how to fix it?
Thanks
Walt Wallach

Hi Walt,
I would like to try a few tests to narrow down what is going on. First, I would like to verify with you what the path is for the Configuration Directory on the development machine. You can access this by launching Station Options, and clicking on the Preferences tab and then checking the Configuration Directory drop down.
Also, I would like you to save off your prior users.ini file on the development machine. Then I would like you to open up the sequence editor, add a new user, close the sequence editor and then reopen it to verify that the change persisted. Then I would like you to do a diff on the two users.ini files to verify that they are different.
Also, do you get this same behavior when using an OI shipping example?
Cheers,
Kelly R.
Applications Engineer
National Instruments

SSIS 2012 Project Deployment with included EXE application not deployed in Catalog

Hi,
I have converted a SSIS solution consisting of 20 packages, two exe applications, and a web service to the project deployment model. My question is: where are the exe applications deployed to? I don't see them in the catalog on the server. If I exclude
these from the solution and disable the steps in the packages using them, everything works fine. In BIDS, I can include the exe applications and run the solution locally and it works fine. I have parameters for the path to the EXEs, but when configuring
the path in the catalog, I am unsure what to set it to. Do I need to manually move these EXE applications to the database server separately from the deployment?
THanks much,
Pat

You can even put exes as files in file system in a shared folder and access them from packages in catalog. Just pass the paths (UNC) using parameters in package
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

TestStand 2010 Deployment not including TestStand VIs in deployment

Hi all,
I have a question about a deployment I am trying in TestStand 2010, having just recently upgraded from 4.2.1. I was building a particular deployment with no issues in TS 4.2.1, using LV 2010. The VIs in the project use the TestStand Get/Set Property VIs quite a bit, and in the 4.2.1 support VIs directory, you can see them there.
However, using the same deployment configuration, I tried to build the deployment in TS 2010. This deployment didn't have any of the TestStand VIs which were present in the 4.2.1 deployment. As a result, VIs that call the TestStand VIs are reported as broken. Note that the VIs were created while I was using 4.2.1, so the TestStand VIs are for that version (it has never been an issue for previous upgrades, however).
Recap:
TS 4.2.1, LV2010 - Deployment works fine
TS 2010, LV2010, using same deployment configuration file - Deployment broken, no TS VIs included in support VIs
Ideally I'd like to sort this out at a deployment level, rather than employ any workarounds. Is there a difference in the TS 2010 and 4.2.1 VIs? Or am I missing something glaringly obvious?
Any help is greatly appreciated!
Thanks,
Rob
Rob Greene,
ATE Engineer,
Benetel Ltd.

Rob,
I tried a small demo using TS2010 and LabVIEW 8.6.1 (only have this on my system at present)
When I created my deployment image, I open the LLB that was created and present in the LLB was TestStand - Get Property Value (Number).vi.
I then changed one of the options in the LabVIEW VI Options dialog so that I excluded files from VI lib and then rebuilt the Deployment image, TestStand - Get Property Value (Number).vi was missing, as expected.
So It seems to be working for TS2010 and LabVIEW 8.6.1.
Can you check that you haven't got any options selected that are excluding files.
Regards
Ray Farmer

TestStand: Access Denied to testexec.ini file

When changing search directories, or any station property, I get an access denied error, and the changes to the search directories don't get saved.

Hello Shay,
If you are using Windows 2000/NT and your drive in which TestStand is located is partinoned as NTFS, you can set security permissions on folder or on a file basis. You should check your security settings for the folder \Cfg. This folder contains all the INI files that store the station options, and search directory settings. You may have the folder set to deny write access, when it should be set to full control. You can access the security options by right-clicking on the file/folder and selecting Properties from the context menu. Hope this helps.

Trouble deploying TestStand

Hi,
I have tried many suggestions and configurations but I still cant get my deployed TestStand to run in other PC. I kept getting "Unable to launch the 'LabVIEW .Application' ActiveX automation server. TestStand cannot find a LabVIEW Development System installed in this computer." My test sequence also uses custom process model. Below are the things that I have done:
1. Configured the LabVIEW adapter to use RTE and enable "Always Run VI in LabVIEW RTE" in the LabVIEW Advanced Settings under Module tab.
2. Added configuration .ini files that will be used, including TestExec.ini and TestStandModelModelOptions.ini in workspace.
3. Enable "Install TestStand Engine" and leave Engine Options/ Drivers and Components as default.
Below are my questions:
1. Since I am using custom process model, where should I save this .seq in?Is it in my working directory or TestStand components folder? Reason why I am asking this is because I tried both ways, the latter gave me
"Warning: This problem will cause an error when building a deployable image or an installer. The following file(s) were not found:
rfid_read_write.seq in step 'Reset Test Sequence', sequence 'MainSequence', sequence file 'C:\Program Files (x86)\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\SequentialModel_RFID.seq'"
Obviously rfid_read_write.seq has already been included and present.
2. Should I also include this custom process model .seq file in the workspace/deployment?
3. How to solve the unable to launch LabVIEW.Application issue?
Thanks.

Hi, it looks like the app has trouble starting up:
05/01/17 10:21:47 - ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
Did you have any errors on the compile of the code?
You also want to check if the app is deployed (if so you may want to remove it before re-deploying it)

Not reporting after deploying

My seq is working fine on my development computer, both via the development editor and the simple/full-featured userintyerface.
I have setup reporting in ATML, Access DB and offline report format.
Reports are located on a server inhouse.
When i deploy my system, and install in on my production machine, and run it via the Simple or Full-featured UI, it says "no result from main seq", and none of the 3 reports are being updated !
I store files via my teststequence, on the same server, during the test, and those files are updated. I.E. the test-station see the server and folder ok
any ideas ?

Hi Nikolaj,
The station options settings are stored in the testexec.ini file. Search directories is another example of what is stored here. You can find that file and other configuration files in the <TestStand Application Data>\Cfg directory.
You can find more information here:
How Do I Include My Station Globals, Search Directories, Tools Menu, etc. in My Deployment When Using the TestStand Deployment Utility?
And here:
TestStand 2014 Help: Configuration Files

Deployment and modelsupport.seq

I use a customized process model in my design. I'm building the deployment, and I tell the deployment to get the process model and put it into a certain \user folder. This model, like the default sequential model, references ModelSupport.seq, ModelSupport2.dll, reportgen_xml.seq. I did not modify these files at all. Do I have to somehow point to these files in the deployment. All of those files are already installed on the target machine.

Hello Mr. Bean,
By default, NI's process models store code module path as a relative path. So, the path to the ModelSupport2.dll is stored as ModelSupport2.dll instead of C:\Program Files\National Instruments\TestStand 4.0\Components\NI\Models\TestStandModels\ModelSupport2.dll. TestStand finds this file by appending the relative path name to all of the search directories until it finds a file. If your target computer has the default search directory of C:\Program Files\National Instruments\TestStand 4.0\Components\NI\ enabled to search through all sub-directories (which it should), then your custom process model should not have a problem locating ModelSupport2.dll and all of the other model support components.
You can also deploy your search directories by including <TestStand>\cfg\TestExec.ini in your workspace (and then in your deployment), as your search directories are stored in TestExec.ini.
Also, "TestStand 4.0" can be replaced with "TestStand <version>" for the above paths. I hope this helps!
Best Regards,
Software Engineer
Jett R

How to Deploy Station Preferences

I am deploying my application to my target PC along with the test stand engine. In the development PC, I have set few things in the station preferences like use computer name as station id. When I deploy my application. Does these station configuration also transfered to the target PC? If not how do I deploy the station preferences to the target PC.
Thanks,
Senthilnathan A.

Hi Senthilnathan,
All your TestStand station configuration is stored in a file called TestExec.ini located in the <TestStand>/cfg folder. So if you'd like the same settings on your deployed computer, then you have to include this file into your TestStand Workspace. Now when you deploy, this file will replace the original settings.
I hope this helps
SijinK
National Instruments

TestStand Deployment Issues

Right now we are in the process of building deployment packages for our test stations in TestStand. We basically have some model customizations as well as the actual client sequence file, which calls VI's. These VI's do have sub-VI's which are distributed with the package. I can get the whole package to deploy (both install and image files), but when I try to run the deployed package on the target computer using a customized user interface, I recieve error -18001. The error dialog box informs me that the VI cannot be run, because the NI LabView Development System cannot be found. In my client sequence file I went through all the VI's and made sure they always run in runtime mode. I also set the LabView adapter on my development computer to runtime v8.5 for when I deploy. I'm quite baffled at this point as to why I'm still having issues. Could it be an issue with my user interface instead, or how do I remedy this issue?
Message Edited by schm1347 on 10-26-2007 10:42 AM

Hi, schm1347,
The adapter info is stored in <TestStand>\cfg\TestExec.ini file. So when you make your deployment, you should include this file and deploy it to the same folder on the target computer, as shown in the attached screenshot.
In general, if you want to keep the TestStand settings on the target machine the same as the development computer, you should include the cfg folder. It includes user management, station global, execution options, etc.
Regards,
Song D
Message Edited by Song D on 10-29-2007 11:36 AM
Regards,
Song Du
Systems Software
National Instruments R&D
Attachments:
ss.JPG ‏72 KB

Including TestExec.ini in Deployment

Similar Messages

Maybe you are looking for