06-15-2009 05:48 PM
I've installed TestStand 4.2 on two Windows XP machines. On one machine it worked fine first time. On the other machine I receive the following message in the login box, and also in the templates pane: 'String not found in language resource files." I have tried uninstalling and re-installing TestStand twice but still get this error. This error prevents me being able to login as an administrator so I am unable to use TestStand 4.2. I understand that these language resource files are provided by the installer but for some reason it seems that the machine with the error cannot locate these.
The only difference between the two XP machines that I can find is the location of user profiles. I note that on Vista compatible TestStand versions that TestStand user settings are stored to C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2\Components on XP machines. On the XP machine with the error all user profiles are stored under C:\profiles, rather than C:\Documents and Settings. This is the standard profile used by our company so I am unable to change this. The TestStand installer does recognise this and installs TestStand user settings to C:\profliles\All Users\Documents\National Instruments\TestStand 4.2\. Does anyone know whether the location of the user profiles is important, or whether there is another cause for this error?
Regards,
David
Solved! Go to Solution.
06-16-2009 10:08 AM
David,
This KnowledgeBase article addresses part of this issue. It mentions that it does matter where we install the langauge files because TestStand is looking for them. It will first look in the TestStand Public directory (which is the one you mentioned), however if it can't find them it should look in the TestStand directory under Program Files to find the default files there. Did you install TestStand to the default directory (C:\Program Files\National Instruments\TestStand 4.2\)?
I would also try to change the TestStand Public Environment Variable. This was introduced as part of the Vista compatibility, so you can simply change this variable to control where TestStand looks for those files. It points to the C:\Documents and Settings\... directory by default, but if you change it to point to C:\profiles\... it may fix your issue. If you look at the screenshot below, I would simply replace the 'Documents and Settings' part of the path with 'profiles' and that should point TestStand to the correct directory for your machine.
06-16-2009 10:15 AM - edited 06-16-2009 10:20 AM
David -
You might want to delay messing with the above variable settings until we have more information. The article that is references is also for TS 2.0, but the issue that it discusses is about an error that occurs before even getting the GUI to display. In general, TestStand cannot create the engine unless you have minimally have read access to the configuration directory that is typically stored under the profiles. Since you are not seeing that error, it is safe to assume that TestStand is locating its information stored under profiles. I played a little to see if not having write access could cause a problem, but the results were not similar to yours. If the sequence editor has English text on it and looks normal, the mechanism that we use to resolve error text that we display is likely to be working properly. Can you post screenshots of the two messages that you are seeing, which might help? For the OS user that is running TestStand, what permissions do they have on the system (admin, power-user, guest)?
06-16-2009 04:25 PM
Hi Scott,
I've held off on the changes suggested by John for now. You are correct in that the knowledge base article referenced by John does not apply since the engine does initialise.
I've attached two screen shots. The first one is the standard login box which displays the "String Not found in language resource files" message in place of the usual "administrator" user name. If I overwrite the "String Not found in language resource files" user name with "administrator" and click OK to log in then I get an "Invalid User Name" error dialogue box. Therefore I am unable to log into TestStand.
The second screen shot shows the TestStand sequence editor with the String Not found in language resource files visible in the templates pane.
Regards,
David
06-17-2009 11:41 AM
David -
The cause of the strings not being found is likely when first launching TS, the language files were not found. The language files contain some default display values, and these values are persisted as actual values when saving some configuration files. For example the default administrator name and the default folders in the insertion palette. I would recommend that you delete the Users.ini and Templates.ini file in the configuration directory and this should address your current behaviors. I am not sure why login was giving you a problem because I was able to use the default empty password on the "String Not found in lanuage resource files" user. If you still have problems with login, let us know.
Do you remember anything unique about how you got to this situation that caused this to occur?
06-17-2009 04:13 PM
Hi Scott,
I deleted the Users.ini and Templates.ini files from C:\Profiles\All Users\Application Data\National Instruments\TestStand 4.2\Cfg, restarted TestStand and all is working now.I've also installed my custom files and process model and they work now as well.
I didn't do anything unusual during the installation. All I did was insert the CD, do a full install (minus Device drivers) to all the default directories. I went through this process twice (after uninstalling my first installation) but got the same behaviour. Maybe there is a problem installing on XP when there is a non-standard profile directory set up on the machine as was the case here? My XP laptop had a standard profile configuration (all profiles saves under the C:\Documents and Settings directory) and TestStand worked first time on that.
Thanks for your help,
David
06-18-2009 10:23 AM
David -
I am glad that you are up and running. We had an application engineer attempt to install using an alternate profile location and they did not seem to have any issues however, there might be some subtle issue that you are hitting. I assume that you will be instalingl on a clean system again since this is your configuration that your company is using, so please let us know whether you see the same problem again.