09-28-2009 07:31 PM
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
09-29-2009 12:41 AM
Hi,
When you say right place, do you mean right for TestStand. Have you check the Station Options and ensured the paths are what you expect.
What TestStand version are you using?
Regards
Ray Farmer
09-29-2009 01:09 AM
Ray,
Thanks for the quick reply.
The .ini failes are in C:\Documents and Settings\All Users\Application Data\National Instruments\TestStand 4.1.1\Cfg
Wouldn't the UI expect these files to be at the same path as for the development system?
Walt
09-29-2009 02:20 AM
Walt,
That's where I would expect them. I seem to remember something about the deployment tool over written the user files with the default files. There was a post about it. I'll see if I can track it down.
It may not be related.
Regards
Ray
09-29-2009 12:35 PM
Even when I copy the original files from my development machine to the deployment machine, the UI still ignores the files. It behaves like its either unable to access them (I checked the premissions and I don't see any problems), or it isn't looking for them there.
Walt
09-29-2009 02:16 PM
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?
09-29-2009 04:02 PM
This is interesting. The Station Options->Preferences->Configuration Directory shows as <Test Stand Default Location>.
When I click the browse icon, it takes me to C:\Documents and Settings\Admin\Desktop, which I know is wrong.
I saved a copy of users.ini, created a user, and users.ini modified dated changed to now and the copy is smaller than the newly saved file.
Walt
09-29-2009 10:00 PM
I looked on the deployment machione at StationOptions, and it is looking for users.ini at \Program Files\National Instruments\TestStand 4.1.1\Cfg
Normally this is a short cut to the copy in \Documents and Settings\All Users\Application Data\... but on this machine there is a directory with default files as well as a link to the "right place". I copied the correct files into the directory and everything works as I expect.
Now, the question is why did installing what was built by the Deployment Utility create a Cfg directory in parallel with the short cut, but put the configuration files on the other side of the short cut?
Walt
09-30-2009 01:47 PM
Hi Walt,
I just wanted to verify that I understand what you are seeing. Do you now have a Cfg folder along with a Cfg shortcut in \ProgramFiles\National Instruments\TestStand 4.1.1? Would it be possible to attach screenshots of both of the folders that you mentioned in your previous post.
09-30-2009 03:43 PM
Kelly,
Yes, that is correct. And when I delete the local Cfg directory, the UI ignores the shortcut and creates a new local directory with default files. Only when I copy the correct files into the local directory does it work correctly.