Teststand 2013 is losing .seq extension in sequence editor.

Hi,
After I load my *.seq file and perform a couple of editing tasks and run it a few times it loses its extension and saves it as just file name, no extension. Then I am getting all sorts of error messages that my file was edited outside of the environment etc.
I fix it by forcing Save As and saving it manually. A little annoying. I thought it was related with creating a link to my seqeunce on my desktop, so I started running TestStand and then opening the sequence but that did not help. Any ideas?
Thanks
CT
Attachments:
Capture.PNG ‏21 KB

Hi Cimteker,
Can you make sure that there is no duplicate directory where the file gets saved. Like you have mentioned on the desktop. Can you delete that, and keep only one directory, and try again. What happens?
Also maybe deleting and rebuilding the ini file might fix the problem. See below:
If you have already seen a error -17500, and are unable to open any of the TestStand pop-up menus by right-clicking, the easiest way to fix the errors is to delete the <TestStand>\Cfg\TestExec.ini file. Note that this fix will not work if you saved your type palettes after seeing the -17500 errors. For best results, always shut down TestStand without saving files when you encounter this error.
Repair:
Since the TestExec.ini file contains all of the information that the application uses to build menus, removing this file will erase the source of the error. When TestStand cannot find this file at start-up, it will rebuild it using the default menu setup. You will see a fresh copy of the file located in the Cfg folder. Once this file is rebuilt you should be able to navigate your menus as before. Once you have restarted TestStand, you may see that your custom step types are missing from the MyTypes.ini file. To get the file to refresh itself, browse to the <TestStand>\Cfg\TypePalette folder and open the MyTypes.ini file in any text browser. Save the file without making any changes. TestStand detects the type file again and loads it into memory. Your custom types will be as they were last saved, so you may need to look for them in their original group locations.
Prevention:
The simplest way of avoiding this error is to make use of the Submenu Display Name Expression. You can access the Submenu Display Name Expression field by right-clicking on a step type in the Type Palette window and selecting Step Type Menu Editor. This field is only available when you have selected a group rather than a type. When you create new groups, this expression is blank by default. This expression is used by TestStand in order to sort groups by name when writing them to the TestExec.inifile and generating menus. Therefore, if there are several groups named "" (essentially groups with no name) then TestStand may be unable to distinguish among them. Enter any unique name in the Submenu Display Name Expression for every group before renaming or moving it to a new location.
National Instruments
Applications Engineer

Similar Messages

TestStand 4.0 reportgen_html.seq Type Conflict

We have converted from TestStand 3.5 to TestStand 4.0. We had created a custom reportgen_html.seq in TestStand 3.5 which we copied over to the TestStand 4.0\Components\User\Models\TestStandModels directory and updated using the Update Sequence Files utility (which is nice by the way). Everything works fine until we try enabling on the fly report generation. Then we get the following error when we run any sequence using single pass:
Details:
Type 'NI_BatchTestSocket' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the file with the type conflict in the Sequence Editor and resave it.
The sequence file 'C:\Program Files\National Instruments\TestStand 4.0\Components\User\Models\TestStandModels\reportgen_html.seq' could not be loaded.
Error Code:
-17329; Invalid type - conflicts with an existing type.
Location:
Step 'Process Step Result' of sequence 'SequenceFilePostResultListEntry' in 'SequentialModel.Seq
If we open the \User copy of reportgen_html.seq prior to running a sequence, the error does not occur. If we view the sequence file types for the \User copy of reportgen_html.seq, the Usage column shows reportgen_html.seq twice, which is a surprise and an indication that the \NI copy of reportgen_html.seq is involved. If we rename the \NI copy of reportgen_html.seq and restart TestStand, we can run without errors without having to open the \User copy first.
We had thought that if a copy of reportgen_html.seq was in \User, then the \NI copy would not be loaded or used at all, but it looks like TestStand is trying to load both the \NI and the \User sequences. Is that how it is supposed to work? If so, it seems like we have to modify files under \NI to avoid the error. It is our understanding that we really don't want to change anything under \NI so that future versions of TestStand won't stomp the changes.
Hans

Hi Hans,
It looks like you are having two problems. The first appears to be a type conflict. You can resolve this by opening the file in TestStand and saving it. The update utility will update the files to the 4.0 format, but it won't necessarily fix any custom types.
The second problem you are experiencing is because TestStand is still loading the reportgen_html.seq file from the NI directory. I would assume that you are still loading one of our process models from the NI directory. The process models have a relative path so they will find the reportgen_html.seq file in the NI side first. Renaming that file fixes your problem because the file is not found in the local directory (which I would assume is your first search directory) but is instead found in the User directory. If you copy everything from the NI directory to the User directory and use the user files, then everything should be taken care of for you.
Matt M.
NI

TestStand 2013 - Edit VI button disabled

Hello to everyone,
I am using TestStand 2013 development system, and I also have Labview 2009 SP1 Full development system.
I introduce a step with a labview action in my sequence. The Edit VI button is disabled, with the message "Requires LabVIEW Development System"...
Anyone can help me?
Much thanks for your time and dedication!
Solved!
Go to Solution.

What is your LabVIEW adapter set to? Is it set to use the development enviornment or is it set to use the run time engine?
You can check by going to Configure>>Adapters...
Choose LabVIEW and select Configure
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Programatically select a step in a sequence in a sequence file loaded in TestStand sequence editor using C#

Hi all,
I have written C# code to load a sequence file dynamically in TestStand Sequence editor. The code is as follows...
myEngine.PostUIMessage(mySequenceContext.Execution, mySequenceContext.Thread, UIMessageCodes.UIMsg_OpenWindows, 0, null, mySequenceFile, true );
The code is working fine and I could view the Sequence file opened in TestStand Sequence editor.
Now, I wish to select one sequence in the opened sequence file to get the details of the sequence programatically. In other words, I want to simulate a mouse click to a sequence and view the steps associated with that sequence.
Can anybody give some clues...
Thanks in advance.

Hi,
Also I am getting error like "Index out of range. Source: TSUISUPP.SelectedSteps at NationalInstruments.TestStand.Interop.UI.Support.SelectedSteps.AddStep(Step val)". Error code: "-17500; Operation Failed." My code is like
mySequenceFile = myEngine.GetSequenceFileEx(@"D:\dynamic loaded sequence.seq", 0, TypeConflictHandlerTypes.ConflictHandler_UseGlobalType);
mySequence = mySequenceFile.GetSequenceByName("First");
Step myStep = mySequence.GetStep(2, StepGroups.StepGroup_Main);
SequenceContext mySequenceContext = mySequenceFile.NewEditContext();
mySequenceContext .AsPropertyObject();
myEngine.PostUIMessage(mySequenceContext .Execution, mySequenceContext .Thread, UIMessageCodes.UIMsg_OpenWindows, 0, null, mySequenceFile, true);
ApplicationMgr applicationMgr = (ApplicationMgr)myEngine.GetInternalOption(InternalOptions.InternalOption_ApplicationManager);
SequenceFileViewMgr sequenceFileViewMgr = (SequenceFileViewMgr)applicationMgr.GetSequenceFileViewMgr(mySequenceFile);
sequenceFileViewMgr.SelectedSequences.Clear();
sequenceFileViewMgr.SelectedSequences.AddSequence(mySequence);
sequenceFileViewMgr.SelectedSteps.AddStep(myStep);
I am sure that my Sequence selected in the Sequence file loaded has more than 2 steps. Please help me in solving this problem and that in the previous post.
Thanks,
Biju kuttan

RunState.Caller.Locals.ReportOptions.Directory unknown in Teststand 2013

Hello,
I have a problem due to migration between TestStand 4.1.2 and TestStand 2013.
In previous sequences I used the variables: RunState.Caller.Locals.ReportOptions.Directory, RunState.Caller.Locals.StartDate.Text, RunState.Caller.Locals.UUT.SerialNumber, RunState.Caller.Locals.ReportFilePath and others... without problem.
Now in TestStand 2013, the variables cannot be evaluated , generates an Teststand error and thus I cannot personnalize my report name and directory.
Hereafter the complete expression that cause problems:
RunState.Caller.Locals.ReportOptions.Directory=FileGlobals.Report_Directory + "\\" + RunState.Caller.Locals.StartDate.Text + "\\" + RunState.Caller.Locals.UUT.SerialNumber ,
RunState.Caller.Locals.ReportFilePath=FileGlobals.Report_Directory + "\\" + RunState.Caller.Locals.StartDate.Text + "\\" + RunState.Caller.Locals.UUT.SerialNumber + "\\" + "Report ["+ RunState.Caller.Locals.UUT.SerialNumber +"][" + Str(RunState.Caller.Locals.StartTime.Hours) +" "+ Str(RunState.Caller.Locals.StartTime.Minutes) +" "+ Str(RunState.Caller.Locals.StartTime.Seconds) + "]" + ".html",
FileGlobals.UUT_Time = "[" + RunState.Caller.Locals.UUT.SerialNumber+"][" + Str(RunState.Caller.Locals.StartTime.Hours) +" "+ Str(RunState.Caller.Locals.StartTime.Minutes) +" "+ Str(RunState.Caller.Locals.StartTime.Seconds) + "]" , FileGlobals.fileDir=RunState.Caller.Locals.ReportOptions.Directory
Thanks for your help.

If you using these expressions to set the report path and directory, then, do consider using TestStand expression to specify the report path in Report Options dialog. Its lot easier to use compared to setting values to subproperties of Runstate.Caller.Locals.ReportOptions variable.
You can get more information in the following links
http://zone.ni.com/reference/en-XX/help/370052K-01/tsref/infotopics/specifyreportfilepath_byexpressi...
http://zone.ni.com/reference/en-XX/help/370052K-01/tsfundamentals/infotopics/reports_expressions/
http://digital.ni.com/public.nsf/allkb/78E88742D0F8C3C5862576D4006B8E44
Coming to your error, please provide more information regarding which sequence file and sequence did you modify.
Also note that, in TestStand 2012, process models had major change to support plug-in architecture. Process models without the plug-in architecture (like the one used in TestStand 4.1.2) is installed in "<TestStand>\Components\Models\TestStandModels\TestStand 2010 Process Models (Legacy)" directory. If you want to migrate your process model changes, it might be valid to update the legacy process models instead of new models.
You can see brief description of TestStand 2012 process model changes in http://zone.ni.com/reference/en-XX/help/370052K-01/tshelp/infotopics/2012whatsnew/#plugin
- Shashidhar

Teststand 2010 code work under teststand 2013

Hi,
We have some code developed in Teststand 2010 and planning to migrate to Teststand 2013 by adding some improvements to the existing code.
Question is will the existing Teststand 2010 code works fine in Teststand 2013 without any changes?
please clarify me on this.
regards,
Ramjee

ramjeev wrote:
Hi,
We have some code developed in Teststand 2010 and planning to migrate to Teststand 2013 by adding some improvements to the existing code.
Question is will the existing Teststand 2010 code works fine in Teststand 2013 without any changes?
please clarify me on this.
regards,
Ramjee
In general, we strive to make TestStand as backwards compatible as possible, and in many cases you can just open a sequence file in the newer version of TestStand and it will work without any changes. Though since TestStand allows for a wide variety of customization, the ease of the migration somewhat depends on how and what you have customized, for example, process models, step types, etc. might require some additional work to migrate to the newer version of TestStand. There is a migration tool in newer versions of TestStand that should be able to help you with this process when you install on a machine with an older version containing the customizations you wish to migrate.
Hope this helps,
-Doug

TestStand 4.0 Sequence Editor Comments

We are in the process of upgrading from TestStand 3.5 to 4.0.
We use mostly Custom Steps and the Comments in the steps are used as "Help" instructions for each Custom Step Type.
In TestStand 4.0, the comments show up in the Sequence Editor and for us are mostly repeatative.
Is there a way to suppress the comments from showing up on the Sequence Editor but still allow reading them in the Step properties?
I searched through the Station Options and other system configuration options but can't find anything.
Mike

Check out:
http://forums.ni.com/ni/board/message?board.id=330&message.id=15113#M15113

How to Install Inspection Step in Teststand 2013?

Hello
I try to install the NI Vision Builder Inspection Step to Teststand 2013. I Installed NI Vision Builder Automated Inspection 3.6 and Ni Vision Acquisition Software 8.5.1 and I Installed from "ts_vbai_36_and_older_july10.zip" the inspection step to TS2013.(http://www.ni.com/white-paper/4007/en/)
But when i try to run inspection step connect target i got an error message. (See screenshot) I dont know what s wrong and how to solve!?

The only way I can reproduce this error code is by specifying a different version than 3.6.0 in the "VBAI Version". Tested in TestStand 2010 SP1 with VBAI 3.6.1.
Attachments:
VBAIConnect.png ‏21 KB

Teststand Sequence Editor has stopped working

I get the following message and error code when running my sequence file. This sequence files works ok on another machine. It is a display message to the screen for user input. Software version is 4.2.1
Teststand Sequence Editor has stopped working.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: seqedit.exe
Problem Signature 02: 4.2.1.83
Problem Signature 03: 4af027d1
Problem Signature 04: PresentationFramework
Problem Signature 05: 3.0.0.0
Problem Signature 06: 4f350630
Problem Signature 07: 6263
Problem Signature 08: e1
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033

Kingme wrote:
I get the following message and error code when running my sequence file. This sequence files works ok on another machine. It is a display message to the screen for user input. Software version is 4.2.1
Teststand Sequence Editor has stopped working.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: seqedit.exe
Problem Signature 02: 4.2.1.83
Problem Signature 03: 4af027d1
Problem Signature 04: PresentationFramework
Problem Signature 05: 3.0.0.0
Problem Signature 06: 4f350630
Problem Signature 07: 6263
Problem Signature 08: e1
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Do your code modules use System.Windows.Markup.XamlParse? Is the process close to running out of memory (i.e. over 1GB of memory used)? Do you have any DLLImprorts (if C#) or any native code (i.e. C/C++) being called by your sequences? Does the error happen every time you run? Always on the same step? If so, what is that step doing? Have you tried to debug the process?
-Doug

TestStand 3.1 doesn't launch sequence editor

TestStand doesn't launch sequence editor, it is not coming up with login screen.

Hi,
Need a little bit more help.
Any there any errors generated. Is the TestStand Splash screen seen?
Regards
Ray Farmer
Regards
Ray Farmer

Utilisation d'énumération sous TestStand 2013

Bonjour.
Je travaille sur un projet sous TestStand 2013 où je dois créer des Step Types à partir d'une dll en .NET.
Certaines fonctions de cette dll appellent des énumérations en entrée (exemple ci-dessous).
Je load ensuite ce Step dans un Type afin de créer un Step Type.
J'aurais aimé que ceux qui plus tard créeront des séquences à partir de mes Step Type accèdent directement à ces énumération dans leur séquence.
Cependant je n'arrive pas à créer de structures équivalentes à une énumération sous TestStand.
J'ai essayé avec des Containers et des Objects Reference mais impossible de faire apparaître un énumération dans le Step Type.
Du coup, j'ai crée une fonction par élément de la liste ("SetBayerPatternBGBG", "SetBayerPatternGRGR", ...) mais ça ne me plaît gère car multipie les Step Type similaires.
Exemple pour la fonction précédente avec le cas BGBG :
Y'a t'il un moyen de créer un paramètre équivalent à une énumération sous TestStand ou de récupérer celle de la dll.net pour la mettre en paramètre d'entrée de mon Step Type ??
Merci.

Bonjour.
Oui, j'avais déjà vu cette discution lors de mes recherches et vu que l'on pouvais utiliser des containers.
Du coup, c'est ce que je m'apprêter à faire
Ce qui m'ennuie un peu avec cette méthode, c'est que je suis obligé de re-créer toutes les énumérations de ma dll sous TestStand. Certaines de ces énumérations comme "Parity" ou "StopBits" proviennent du Framework 4 et j'aurais préféré les utiliser directement. Ainsi, les personnes qui feraient les séquences avec mes Step Type par la suite accederaient directement à l'énumération plutôt que d'utiliser mes containers.

TestStand 2013 ships with invalid SQL scripts

Hi all,
I tried to submit this through the official support channel, but ran into this roadblock. So, I'm reporting the issue here.
=================================================
I wanted to set up TestStand to log results to an SQL Server 2008 R2 database. I followed the instructions at http://zone.ni.com/reference/en-XX/help/370052M-01/tsfundamentals/infotopics/database_logging/
I tried to run C:\Program Files\National Instruments\TestStand 2013\Components\Models\TestStandModels\Database\SQL Server Create Generic Recordset Result Tables.sql However, SQL Server reported that the script contains syntax errors.
To fix the issue, I had to modify the script (replace "//" with "--", and replace "~" with ";") before running it.
It looks like other scripts in this folder have syntax errors too. Please fix the SQL scripts shipped with TestStand.

Hey JKSH,
Thanks for reporting this--we've filed an internal report for one of our developers to examine the syntax of our SQL files.
In the meantime, it sounds like you were able to work around the issue by changing the characters in the scripts, but have you run into any other problems using the scripts? I'd be happy to help out in any way I can. Just let us know if there's anything we can do to assist!
Daniel E.
TestStand Product Support Engineer
National Instruments

Teststand 2010 SP1 Sequence Editor Lauch Error

Hi, everyone.
Today I have installed the Teststand 2010 SP1 eval version on Windows XP but an error pops up when I run the sequence editor, as per shown in the attached screenshot.
Hopefully, someone can help and advise me on this.
Thanks.
Attachments:
Error.JPG ‏16 KB

Yes, there is an error.
Please refer to the attached picture.
When I tried to make active of Teststand 2010 SP1, there is also an error.
Attachments:
error4.JPG ‏5 KB
error5.JPG ‏7 KB
error2.JPG ‏89 KB

TestStand 2013 error 80004005

For some reason whenever I try to run the Sequence Editor I get a "System Level Exception" followed by " Creating an instance of the COM component witch CLSID {B2794EF6-C0B6-11d)-939C-0020AF68E893} from the IClassFactory failed due to the following error: 80004005"
I have followed the published fixes including deleteing stationglobals.ini, running "Version Selector" etc to almost no avail. The exception is that after a PC re-boot it will run but quite slowly; closing the Sequence Editor and re-starting it brings back error 80004005.
I have also tried un-installing and re-installing TestStand as well as complete re-installtion of DS 2014.
Short of re-formatting my hard-drive and starting again I'm not sure what else I can do.
Any suggestions would be most gratefully received.
Keith
Solved!
Go to Solution.

1) Do you have any idea what might have changed around the time it used to work versus when it stopped working? Any new software installed? Some utility programs like graphics card utilities and virus scanners hook into all processes on a machine with Windows hooks and can sometimes cause unexpected problems. If you have anything like that installed recently, try disabling or uninstalling them and see if the problem goes away.
2) Do you have visual studio installed on your machine? What is likely happening is that an exception (really an access violation most likely) is being thrown inside the constructor of the engine when this problem occurs. If you can run seqedit.exe as the process to debug (with native debugging) with the Debug->Exceptions... dialog set to stop on thrown for "Native Run-Time Checks" and "Win32 Exceptions". And then when the exception occurs, break in the debugger, and do Debug->Save Dump As... to save a dump of the state of the process. Then attach the dump file here and we can take a look to see if it gives us any clues as to what might be the problem.
-Doug

DCOM problem Teststand 2013

I receive attached error everytime i try to launch Teststand 2013 on a PC i recently installed.
My user is administrator and the operating system is Windows 7 Pro.
I tried all the instructions at http://digital.ni.com/public.nsf/allkb/ABA98DF5D5A824DB862570AD007C55E7 but it still doesn't work.
I never received such an error before for my many previous installations
Please help me on that
Attachments:
Adsız.jpg ‏310 KB

Hey hedehodo,
As a first step, could you try running the TestStand Version Selector and setting TestStand 2013 to be the active version, even if the Version Selector already reports 2013 as active? This operation re-registers TestStand components with the operating system and can sometimes resolve these types of issues.
I would also recommend restarting the machine--this can often reset the configuration to a working state.
Let us know how it goes, and we'll be happy to help you troubleshoot further if needed.
Daniel E.
TestStand Product Support Engineer
National Instruments

Teststand 2013 is losing .seq extension in sequence editor.

Similar Messages

Maybe you are looking for