stationGlobals disappeared from build

[jvh75021]

TestStand 4.2, LV 2010

We keep our NI software in clearCase snapshot views since only one of us we be making an update at any one time.Only I have been working on the system the past several days but today when i ran the .tsd is spedified the other's .tsw file as though there had been an update (though the file properties say no). So I fix the path and run the build and it runs normally. However the deployment now only has TS under stationGlobals, my other variables have disappeared. I rechecked the station option dialogs and the cfg directory is where it is supposed to be. The global variables are all still there in the main sequence file on my development system too.

Any idea why my deployment has lost some of the stationGlobal variables?

thanks,

jvh 

[RayFarmer]

Have you deployed the correct StationGlobals.ini file?

If the SeqEditor or UI is opened without have a StationGlobals file in the correct place then a new one will be created with the default StationGlobals.

Have you deployed the correct testexec.ini file which probably defines your path to the StationGlobals file?

Also you refer to globals in a SequenceFile, these are not StationGlobals but are FileGlobals.

[jvh75021]

Hi Ray,

Thanks for posting. This system has been working for over a year but after I used the wrong .tsd one time it has not worked right.

Have you deployed the correct StationGlobals.ini file?

I am not sure. It and testexec.ini are checked in the deployment list.

As an experiment I added new StationGlobal variables and changed the cfg location in station options a couple of times but the .ini file does not update.

Another clue is that copying the StationGlobals.ini file to the deployment system does not help.

If the SeqEditor or UI is opened without have a StationGlobals file in the correct place then a new one will be created with the default StationGlobals.

Have you deployed the correct testexec.ini file which probably defines your path to the StationGlobals file?

Maybe a dumb question but how do I control the directories specified by testexec.ini?

Also you refer to globals in a SequenceFile, these are not StationGlobals but are FileGlobals.

I reference them that way because that is where the variables were added to the StationGlobals when the main sequence file was created. When I open the main sequence I see all the varialbes: Locals, Parameters, FileGlobals, StationGlobals with our added variables, etc. So maybe I

mischaracterized them but I open the sequence file to access them.

Thanks,

jvh

[dug9000]

Maybe you customized the location of the cfg directory on the deployed machines and it's not the directory you think it is? Check the station options. That's the only thing that would explain why manually copying over the stationglobals.ini didn't work.

Hope this helps,

-Doug

[jvh75021]

Thanks Doug, that helps.

Is there a way to have the deployment build process control the cfg location so it does not need to be updated on the deployment targets?