NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

error 'SpecifyExeByExpr' error

Solved!
Go to solution

Hi,

 

I'm using TestSTand 4.2. 

I start a new sequence and select the step 'call executable'.

Before i get a chance to do anything, TS display this error:

 

 unknown variable or property name 'specifyExeByExpr'.

Error accessing item 'SecifyExeByExpr'.

  

Error code: -17306, unkown variable or property name.

  

Any idea?

Thanks

Rafi

0 Kudos
Message 1 of 11
(4,979 Views)

Hi Rafi,

 

Is this in the SeqEditor, and is the new sequence in a new Sequence file or an existing one?

 

Does this happen to any other step types.

 

 

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 2 of 11
(4,981 Views)
0 Kudos
Message 3 of 11
(4,973 Views)
0 Kudos
Message 4 of 11
(4,972 Views)

Hi Ray,

 

Yes this is in the sequence editor.  it does not happen with any other step. It happens both in new and existing files.

 

This missing variable is not one of my variables but something the system is waiting for...

 

Any idea?

 

thanks

Rafi

0 Kudos
Message 5 of 11
(4,967 Views)

Hi Rafi,

 

My guess is that maybe the default setting is incorrect (maybe be a bug), have you actually tried to set the value a known expression.

 

Maybe you can post your example that generates the error and I'll look at it later on today when I have access to teststand.

 

Regards

Ray

Regards
Ray Farmer
0 Kudos
Message 6 of 11
(4,949 Views)
Solution
Accepted by topic author Rafi2003

It sounds like you have the wrong version of the call executable step type loaded. Make sure that you are loading the correct type palettes for 4.2 and that you didn't accidently merge in an older version of the step type from a sequence file or something. You can view the types and their versions in the type palettes document. Go to the All Types section if you aren't sure what type palette file it's in. This step type is named "CallExecutable" should be version 4.2.something and should have a subproperty called "SpecifyExeByExpr".

 

 

-Doug

Message Edited by dug9000 on 05-04-2010 09:49 AM
Message 7 of 11
(4,937 Views)

Hi Rafi,

 

Doug is right, TestStand 4.2 added new features to the Step Type.

 

You need to remove the NI_Types.ini from the Shared Area which is probably at a lower version. As you said that it happens with a New Sequence File and existing file, that would suggest the old Step Type is not in a Sequence File but in the pallete.

 

You could have a look in the Sequence File View to chek out want version the Step Type is.

 

Regards

Ray Farmer

Regards
Ray Farmer
Message 8 of 11
(4,919 Views)

Hi and thank you Dough and Ray,

 

I reinstall TestStand4.2 on a machine which had TestStand 4.1. (due to Windows crash).    When I tried to run the sequence I was asked to choose between new types and old.  I always choose the old.... This, probably caused the problem.  However, everything else is working fine.  The only problems is the CallExecutable.

 

I've solved my problem, in the meantime, by creating a vi with system executable.  However, I still want to FIX this problem.

 

Ray, you said to delete the NI_types.ini that points to TestStand 4.1.  I do have NI_types.ini that points to TestStand 4.2 and to 4.1  Do you still think (based on what I explained above) this is what I should do?

 

Wouldn't TestStand force me to change every step of my program to the new type?  It's a big program that runs fine now.

 

If I look at the list under "All Types"   and then "Step types"  I can see most steps with 4.1 and other with 4.2

for example:  CallExecutalbe, MessagePopuop, NI_CloseDatabase  and most of the steps are 4.1.

 

How can I fix only the call executable?  Can I just delete the one from the 4.1 list and use the one from the 4.2.  I don't really know how to accomplish that....

 

 

Thanks

Rafi

0 Kudos
Message 9 of 11
(4,906 Views)

Hi Rafi,

 

Try the Diff Tool, that should sort your problems with the types.

 

http://decibel.ni.com/content/docs/DOC-4070

 

As long as your 4.2 version is in the correct location now. Do you still have your old 4.1 folders still on your system?

Are you seeing the 4.1 version because there are part of existing sequence files?

 

 

Regards

Ray

Regards
Ray Farmer
0 Kudos
Message 10 of 11
(4,897 Views)