TestStand 4.1 manual

Hi Ni-Guys,
Thank you for releasing TS.4.1
But before downloading and installing. I would read the Teststand Reference Manual (the big pdf one).
I am especally interested in the multicore stuff.
Please post it as an attachment here or show me a link.
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

Hi Ray,
Thank you that was exactly what i need !
I also opened the Relase Notes and looked for multicore support
BUT: These documents do not deal with Multicore support.
as in http://forums.ni.com/ni/board/message?board.id=330&thread.id=19993
It seems this is an OS feature and you have no control on which
core your executions are running.
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

Similar Messages

CVI UI Panel updating from TestStand

I'm experimenting with using a CVI graph strip chart in TestStand(4.0). I'm new to threading in TestStand. I would like to do two simple things at first:
1.Load the CVI UI graph panel
2. Update the graph attributes.
Attached is a solution that uses a separate thread for running the CVI GUI and the main thread for updating the title,axis names and data . For some reason, I seem have to have a generic wait to allow the separate thread to update the seqcontext (FileGlobals being updated in TS). If I don't wait, the FileGlobals have not been updated yet, so the UpdateGraph function fails.
Is there anything besides a blanket wait statement that I can use to know when the separate thread has updated the FileGlobals so that I can continue with my UpdateGraph function? I thought about a loop/timeout function, but I thought maybe there was some other thread/synch mechanism that I missed.
Attachments:
CVIGraph.zip ‏1191 KB
GraphTest.seq ‏7 KB

Hey jsmalley,
A Wait step is definitely a good and simple solution to your challenge, however, you could also try taking a look at some of the other TestStand Synchronization steps, which are often used when multithreading. Documentation on these steps can be found on your machine by browsing to Start»Programs»National Instruments»TestStand»Online Help»Manuals»TestStand Reference Manual. The documentation I'm referring to can be found in Appendix B of this document.
Furthermore, there should be some synchronization examples found on your machine at <TestStand>\Examples\Synchronization.
I hope this helps!
Derrick S.
Product Manager
NI DIAdem
National Instruments

S'interfacer avec NI TestStand

Bonjour, je suis débutante en TestStand et malgré avoir lu beaucoup de documentation , je n'arrive pas à résoudre mon problème. Voila j'ai crée une IHM sous Labview (lancer le test, le test OK , le test NOK, le test en cours,voir pièce jointe) en plus j'ai crée plusieurs séquences sous TestStand qui permettent de faire le test de ces cartes . Mon besoin est d'interfacer l'IHM avec ces séquences de test et voir tout le déroulement de test. j'ai déjà vue plusieurs post mais je l'ai pas bien compris.
Merci d'avance.
Pièces jointes :
GUI.zip ‏23 KB

Bonjour,
Vous pouvez sinon regarder le pdf "UsingLabVIEWLabWindowsCVIwithTestStand" présent à l'emplacement suivant :
"C:\Program Files (x86)\National Instruments\TestStand 20XX\Doc\Manuals"
Cordialement,
Jérémy C.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

ActiveX and TestStand

Well I just finished CVI training and have been working TestStand for about a year. I guess this query could have been sent in CVI as well as TestStand. We discussed briefly how ActiveX kind of works. I have the TestStand and CVI manuals and other literature, but what about ActiveX. If I'm to do ActiveX work within TestStand or CVI, what text or manual can someone recommend that discusses ActiveX?
Tony

TonyJ,
Here are some links to ActiveX tutorials and example code in TestStand and CVI:
http://digital.ni.com/public.nsf/websearch/C4ABFFC75C5E6A7186256C4B0083BF3C?OpenDocument
http://zone.ni.com/devzone/cda/tut/p/id/2984
http://zone.ni.com/devzone/cda/tut/p/id/2981
http://zone.ni.com/devzone/cda/tut/p/id/2982
http://www.developer.com/net/vb/article.php/1539541
http://digital.ni.com/public.nsf/websearch/610540BB3EA4EBDD862568960055E498?OpenDocument
http://zone.ni.com/devzone/cda/tut/p/id/4978
http://zone.ni.com/devzone/cda/epd/p/id/1987
Test Engineer - CTA

Input output parameters

Hi, I don't know if this message should be posted in the Test Stand or LabView forum.
I
need to call a LabView VI from within TestStand which will update a
station global upon exitting. How do I specify input parameters into my
VI and return parameters out?
I'm sure there must be documentaion somewhwre on how to do this and it must be fairly straight forward but I can't seem to be able to find it or figure it out.
Solved!
Go to Solution.

Dennis Knutson wrote:
There is documentation on this. Included with TestStand is the manual 'Using LabVIEW with TestStand'. It's even a printed manual though an electronic copy is also included. Try using Help>Guide to Documentation.
When you add a LabVIEW step, In the step settings window, you will see something like the image below once you have picked the VI. To assign TestStand variables to the VI's inputs or outputs, click on the 'f(x) button and browse to your TestStand variable. For inputs, make sure you unselect the 'Default' box.
Hi Dennis, thanks for your response. I do have quite a bit of Test
Stand experience so calling a VI isn't an issue for me. However, I have
very limited experience with LabView and am not sure how to specify
input and return parameters to and from a VI i built. I've attached a
screen shot of my current VI. I would like to pass in a refernece to an
error container and return the platform selected from the combobox.
Attachments:
get_platform.PNG ‏52 KB

CTD Exam questions

Hi I am planning to take the CTD exam. I have few questions and I would greatly appreciate any comments or recommenda
I have gone through the TestStand 1 course manual and started to work on Advanced architecture series
1) Do I need to go through the TestStand 2 course manual and Advanced architecture series for CTD?
2) How the questions are look like? I know there is no sample exam but do I need to memorize all the definitions or ..
Are the questions like the ones after the end of each chapter in TestStand 1 course manual?
3) I know LabVIEW but I am not familiar with CVI or other languages. Do I need to take a look at the Adapter configuration for all the adapters?
4) There is a TestStand Pallete in LabVIEW. Could you please let me know if I need to learn how to use the blocks to pass CTD?
Also I would really appercaite any other help on this exam.
Solved!
Go to Solution.

1) Do I need to go through the TestStand 2 course manual and Advanced architecture series for CTD? No. The exam is for TS I
2) How the questions are look like? I know there is no sample exam but do I need to memorize all the definitions or ..
Are the questions like the ones after the end of each chapter in TestStand 1 course manual? Multiple Choice. Yes you need to memorize names and definitions. They are like the ones in the chapter.
3) I know LabVIEW but I am not familiar with CVI or other languages. Do I need to take a look at the Adapter configuration for all the adapters? Yes. If it's in the manual it can be on the exam.
4) There is a TestStand Pallete in LabVIEW. Could you please let me know if I need to learn how to use the blocks to pass CTD? No. That is more for the CTA.
Check this out: http://forums.ni.com/t5/NI-TestStand/Sample-Application/m-p/2394366#M40647
Regards,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Unable to include Operator Interface in TestStand deployment

Hello. I have created a test system using TestStand 3.5.
There is only one sequence file, and this sequence calls several VIs
that I have created in LabVIEW 8.0. I would like to distribute
this test system to a target computer, which will then run the default
Operator Interface. No bells and whistles, just plain and
simple. However, I'm running into problems.
First, I created a Workspace file in TestStand. I then added a
Project to it. In the Project, I added all necessary files for my
project (the sequence file as well as all of the custom VIs).
Then I proceeded to follow the TestStand reference manual in order to
deploy my system.
For reference, text in italics is the reference guide and text in bold is my comments.
Deploying the TestStand Engine
1. Launch the TestStand Deployment Utility by selecting Tools»Deploy
TestStand System from within the sequence editor.
I did this, and set up my build how I wanted it.
2. On the System Source tab, enable the Deploy Files in TestStand User
Directories option.
This option collects files from the <TestStand>\...\User
directories, so that any customizations that you have made to process
models, step types, language strings, and so on, will be distributed to
the target computer.
I did this, and copied my Operator Interfaces\NI folder to Operator
Interfaces\User. This would assure (I hope) that I would have the
default operator interfaces included in my project.
3. On the Installer Options tab, enable the Install TestStand Engine
option.
Done.
4. On the Installer Options tab, click Engine Options to launch the
TestStand Engine Options dialog box, which you use to select the
TestStand components that should be present in the installer.
Done. Everything is checked.
In the TestStand Engine Options dialog box, expand Operator
Interfaces»Full-Featured in the tree view.
a. Click the X next to LabWindows/CVI to include the
Full-Featured LabWindows/CVI Operator Interface in the engine
installation. The X should become a green checkmark.
b. Click OK to accept the new settings and close the dialog box.
This is where things go wrong. There is NO Operator Interfaces box in my tree view. It simply doesn't exist.
I've tried several different builds using different strategies.
I've done builds with the CVI operator interface in the User directory,
and I've also tried copying over the files manually. On the
target computer, I've always gotten either an error message (Could not
open the TestStand Engine), or else TestStand opens in evaluation
mode. In both cases, my custom VIs and sequence files are nowhere
to be seen. Can anyone shed some light on this? It's
driving me a bit crazy!
Thanks very much,
Brett Gildersleeve

Hi Brett,
Whenever you deploy your TestStand application to target machines, you will always needs a license. The licenses for distributing TestStand are different than for distributing LabVIEW and LabWindows/CVI code modules.
LabVIEW does not require you to purchase any run-time licenses for a deployment system. You can even run LabVIEW VIs in VI format (not executables) from TestStand without using the development environment and without an additional license.
In order to run LabWindows/CVI code modules, you will need the LabWindows/CVI Run-Time engine which is also available free of charge.
Regarding TestStand, you will need a license for each machine that runs a TestStand sequence. TestStand has three types of licenses which are the TestStand Development System License, the TestStand Debug Deployment Environment License, and the TestStand Base Deployment Engine License.
TestStand Development System License
The TestStand Development System License is required for any test sequence development and/or editing of existing TestStand sequence files that you perform within the TestStand Sequence Editor or programmatically using the TestStand API.
TestStand Debug Deployment Environment License
The TestStand Debug Deployment Environment License gives you maximum flexibility for deploying TestStand and LabVIEW, LabWindows/CVI, and Measurement Studio-based systems. This license allows you to install the development versions of TestStand, LabVIEW, LabWindows/CVI, and Measurement Studio, along with any corresponding add-on toolkits, so that you can debug your test application on your deployed test station. This license does not include the ability to perform any development tasks within the TestStand Sequence Editor or programmatically using the TestStand API.
The TestStand Debug Deployment Environment License has debugging capabilities including settings breakpoints, monitoring variable values, and stepping into test code directly from the TestStand sequence.
(Note: This license does not provide the software but rather gives you the right to install a previously purchased piece of software on the target machine.)
TestStand Base Deployment Engine License
The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.
The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.
I hope this clears things up.
Best Regards,
Jonathan N.
National Instruments

Is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence?

I have created a custom TestStand operator interface and have modified the default sequential process model to display a UUT information dialog that prompts for more information than just the UUT serial number. This UUT information dialog is a LabVIEW VI. To distribute the operator interface, I build it into an executable. As part of the build process, I make a copy of the UUT information dialog VI (which is part of my operator interface project) and place it in the same folder as the executable. I have then configured the sequential process model to call the dialog VI from this location. It would be really nice if I could embed the UUT information dialog VI inside the operator interface executable so that I could distribute just an executable instead of an executable and separate VIs. Is this possible? In other words, is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence just like a standard LabVIEW VI call?

Ryan,
The dialog that you've created isn't being directly called by the OI at all and shouldn't need to be included in the same directory as the OI for distribution. Since you are modifying the PreUUT of the default process model, you will give the path to the VI in that step, create a deployment and then manually copy the VI to the directory referenced in the step. The VI is considered a support file for the process model and is not related to the OI at all.
Test Engineer - CTA

Is it possible to step into a CVI dll when called by TestStand?

As the question says: "Is it possible to step into a CVI dll when called by TestStand?"
I am sure Ray F. may have a few tricks up his sleeves... Hope you see this post, Ray!
I compiled a dll using CVI. The dll is called as a test by TestStand.
I do have an "exe" version of the code that I use for debug with a testbed, but the behaviour is not the same as testing the actual target while running TestStand. My goal is to get as close as possible to the real events.
Thanks,
JLV

Sorry about that,
There are two ways as I was saying:
1. You can configure the CVI adapter to Execute Steps in a External Instance of CVI (requires CVI 6.0 or greater).
Only go to Configure->Adapters and select the LabWindows CVI adapter and click on configure and select the corresponding option.
After that set a break point in the step that you want to debug.
An external instance of CVI will be launched where you can set break points and step into the code.
2. From CVI Specifying an external process:
In CVI go to Run Specify External Process and enter the seqEdit.exe as the program name (you have to browse to the location <TestStand>\Bin\SeqEdit.exe).
As the argument you enter the name of the sequence file you want to debug.
Now just select Run->Debug SeqEdit.Exe
The Sequence Edtior will be launched and you can set break point in your CVI code and step into it when the step is executed.
Check the Using LabWindows/CVI with TestStand reference manual for more information.
I hope it helps you to get started.
Regards.

Deciding whether TestStand is the right solution for my company

I'm working at a growing company and we recently started a push in our Test group to try and standardize our future development as much as possible to allow as much re-use of code as possible. I don't want to say exactly what it is we make for confidentiality reasons, but let's just say that 90% of what we make is the same basic type of product, but it comes in literally hundreds of models ranging in size from about the size of a dime to the size of a small washing machine. We're considering switching to TestStand on all new stations and on all updates of previous stations to assist in rapid development with increased efficiency.
Over the years we've made about 20 or so test stations as new versions of our product came out, each able to fit products of a different size and with different test requirements, but because our main products are all so similar to each other, there's only a pool of about 6 different types of tests we need to run, with some products needing only one of those tests and others needing all 6, and plenty in the 2-5 range. The size differences among different products also mean we have a large amount of different power supplies, and for various other reasons the measurement devices for the test stations aren't terribly standardized as well.
Step 1 was that we standardized the database we used to store all of the test data. We now have one database that can store data from all of our test stations in the same way. A few of the old stations had to have some creative workarounds done (i.e. instead of rewriting their current test program, write something that takes their old output format and converts it to the new database format, then upload it), but this step is 100% complete.
Step 2 was to abstract out the most common pieces of hardware, so we have started basically putting the IVI types in a LVOOP wrapper. Now instead of being limited to interchangability among IVI devices we can also swap in any of the other assorted devices we've accumulated over the years, many of which don't have IVI drivers and even a few that don't follow SCPI standards, as this is a great use of inheritance and overrides. We're also implementing a few device types that don't have IVI classes. This effort is already well underway and we're OK here.
Step 3 is where we're at now. As we standardized on hardware interfacing, we also figured it would be a good idea to attempt to effectively write each of the 6 or so tests one last time each with very flexible setup parameters as inputs, using the abstracted hardware classes so that it wouldn't matter which hardware we had, so that all the tests would run the same way. So we started looking at solutions to some form of sequence management, and we came up with a couple of possibilities for homegrown versions but after debating those for a while we started to ask ourselves, "Are we just re-inventing TestStand here?"
We use TestStand on a few stations here already so we had licences for development, but the stations we use it on at the moment fall into the 10% of outliers that we have and are somewhat non-standard. So none of the 6-ish usual tests were used on them and they're for a very different product type, so we never tried to use them with our standardized database. They also were all made before I came on board here, so I don't have much experience with TestStand myself, and I've run into some roadblocks when trying to come up with a framework for how to integrate our standard database and our standard instrument LVOOP classes into a TestStand environment that meets our current and future test requirements.
The first roadblock is that our database standardization and TestStand's built-in reporting don't mesh at all. Right now, all of our test stations use the same "mega-cluster" to store their data in, which is a type-def cluster of all the things our products could ever be tested for on any of our stations. We pass it to a common database write function that writes everything that has changed from the default values (NaN and blank strings\arrays) and ignores the rest, so we don't fill the database with zeroes for the tests we don't do. I do want to emphasize how big this cluster got in order to have all of the potential save values we might ever need in it. It is a cluster of 13 other clusters, the largest of which has 10 items in it, and one of those is a 1-D array of another cluster with 19 elements in it, and one of those elements is another 1-d array with a cluster of 24 units in it. If all of the controls in the mega-cluster are shown on the front panel at once, I can't fit them on 2 full-size 1080p screens at the same time. The context help for the main cluster is 5 screen heights tall just for the listing of all of the elements.
So I really can't see this being integrated with the built-in TestStand reporting system. Additionally, the "Type" system in TestStand appears to be unhelpful when attempting to pass this cluster between steps, and even worse when trying to pass it between sequences. When I add the mega-cluster to it, it also creates over 30 other types, one for each of the other clusters contained inside of it. Within LabVIEW alone this is pretty easy to manage, as we just have a centralized repository of typedefs in source control that gets checked out to a common directory on each computer, as we do minor changes to acommodate new products a few times a year. However, on TestStand, I can't find a method that's the equivalent for just storing a bunch of .ctl files in the same shared directory like we do with LabVIEW. I see that they can be stored in certain INI files or in sequence files. The INI files appear to all be station-specific, and since all of our 20ish test stations have different hardware and capabilities, we can't just synchronize those files. And if I want to pass the mega-cluster type between sequence files that call sub-sequence files, every one of those files will need to be manually updated to get their types to match... and we'lll be needing at least 200 sequence files when we're done, at a guess. Unless there's some method I'm missing here, I don't see how to use TestStand to move this data around. We could use something like just passing it by reference, but then if we do that I don't actually see much of a benefit here of using TestStand instead of just pure LabVIEW as two of the things that TestStand is supposed to handle (reporting steps as pass/fail against limits and reporting and logging the results afterwards). Plus then we have the additional burder of making sure the module holding the reference in LabVIEW doesn't unload before we're done using it.
Is there some better way of handling massively complex types in TestStand that I am not seeing?
There may be more that I'm not seeing yet, but if there isn't a way to handle these massively complex types in TestStand, all we'd be getting out of it is a slightly easier method of managing sequencing than we have now, which I don't see as being worth the investment in time and licenses it would take.
I'd be grateful for any feedback. Thanks!

Considering you already seem to be leveraging LabVIEW heavily and before jumping into TestStand I would look at the PTP Sequencer. This seems to be a cutdown version of TesStand but inside LabVIEW and is a simple install from the LabVIEW Tools network using VIPM.
If you are happy to look at alternative representations then maybe check out NI's StateChart Module or the Open StateChart by Vogel (available as an install from VIPM).
The advantages of any of the above is they will be alot cheaper than TestStand and the required run time licences if you don't require all the power of TestStand (extensible everything).

I need to pass data from an Access database to Teststand by using the built in Data step types(open data

base /open SQL Statement etc) the first time i defined the system everything was fine but when i changed the Database (using M.S.Access) the " open SQL Statement" it would show the tables but not thier columns ,I"m using win98 sec edition / Teststand 1.0.1i need to pass data from an Access database to Teststand by using the built in Data step types(open database /open SQL Statement etc) the first time i defined the system everything was fine but when i changed the Database (using M.S.Access) the " open SQL Statement" it would show the tables but not thier columns ,I"m using win98 sec edition / Teststand 1.0.1
When I tried the same thing on another cmputer the same thing
happend
appreiciate u"r help

base /open SQL Statement etc) the first time i defined the system everything was fine but when i changed the Database (using M.S.Access) the " open SQL Statement" it would show the tables but not thier columns ,I"m using win98 sec edition / Teststand 1.0.1Hello Kitty -
Certainly it is unusual that you can still see the tables available in your MS Access database but cannot see the columns? I am assuming you are configuring an Open Statement step and are trying to use the ring-control to select columns from your table?
Can you tell me more about the changes you made to your file when you 'changed' it with MS Access? What version of Access are you using? What happens if you try and manually type in an 'Open Statement Dialog's SQL string such as...
"SELECT UUT_RESULT.TEST_SOCKET_INDEX, UUT_RESULT.UUT_STATUS, UUT_RESULT.START_DATE_TIME FROM UUT_RESULT"
Is it able to find the columns even if it can't display them? I am worried that maybe you are using a version of MS Access that is too new for the version of TestSt
and you are running. Has anything else changed aside from the file you are editing?
Regards,
-Elaine R.
National Instruments
http://www.ni.com/ask

How can I set defaults in the TestStand's step settings Labview Advanced Settings tab to run a VI on a remote PC?

I am accessing a VI many times which is run on a remote PC.
When I click Step Settings, click on the Module tab, then click on the Labview Advanced Settings, there is are options for running a VI on a remote PC.
An annoyance is having to enter the remote host, remote VI path, port number and timeout settings every time I created a step to call the VI in the tests. These are a constant, or at least the rule by far rather than the exception. The TestStand step settings default is the VI does not run on a remote PC (unticked) and there are of course no IP addresses etc as defaults. So if I make a minor change to the tests such as the remote VI location, I have to manually change it is every occurrence of the VI being called. This is very time consuming and is prone to human error.
Is there a way I can preset these settings so that every time I call a Labview module, these defaults are invoked without me having to set them every time?
I guess a workaround is to have the VI run in a subsequence, so that the settings are made just once, but I would prefer not to have to do that.
regards to the NI community,
Dave
Solved!
Go to Solution.

Hi,
What you can do if you are using TS4.x is create your first step, then add it to the Template List. Then use the step from the template list when you require similar steps. See User Manual Chapter 3-6.
Regards
Ray Farmer
Regards
Ray Farmer

How to use return value from TestComplete ( using COM) as a variable in the conditional statement (e.g. while loop) in TestStand

Hi,
I have setup a COM interface for TestStand(TS) to run certain scripts in TestComplete (TC). Normally, when TestComplete finishes executing the script, it returns a 0 or 1 to denote pass/fail in the TestStand step (e.g String value test step). This worked fine.
However, now I need TestComplete to return a vaule( e.g 32) to TS, and TS need to evalue this value in a while statement. So if TC return value is 32, I'd have some statement in TS ike :
While (return value != 30)
Do something..
Thanks,
Solved!
Go to Solution.

There are a hundred ways to implement what you are asking. The hard part is deciding which one would be the best for you.
What adapter are you using to communicate with TestComplete? ActiveX? Is TestComplete running asynchronously (in parallel)? If so then how is the data getting back to TestStand?
So here are some options:
1. You can use the While Step type. It's in the Flow Control folder in your Step Types pallette. Look in your examples under UsingFlowControlSteps.seq in the SequenceFlow
2. You can loop on a step and have the termination for the loop be (return value == 30). Look in the Step Properties under Looping. Also in the TestStand help
3. You could do Post Actions based on a condition and have it jump to another step. Read about it in the TestStand Reference Manual.
4. You could use a GoTo step. I don't really recommend this one. It makes code hard to maintain. Also an example in SequenceFlow called gotobeep.seq.
Hopefully this gets you thinking. Let me know if you have specific questions about any of these methods.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

Error Manual intervention is required to stop the members...

I'm seeing a couple errors when disconnected members try to rejoin.
I've read what's here about "validate polls":
http://coherence.oracle.com/display/COH35UG/Partitioned+Cache+Service+Log+Messages
I think the relevant stuff is this:
2010-12-15 09:04:25.193/17363.862 Oracle Coherence GE 3.6.1.0 <Error> (thread=Cluster, member=n/a): validatePolls: This service timed-out due to unanswered handshake request. Manual intervention is required to stop the members that have not responded to this Poll
PollId=2, active
InitTimeMillis=1292425166002
Service=Cluster (0)
RespondedMemberSet=[1,2,3,4,5,6,7,8,9,10,11,12,17,19,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,40,41,42]
LeftMemberSet=[20,21,39]
RemainingMemberSet=[18]
2010-12-15 09:04:25.197/17363.866 Oracle Coherence GE 3.6.1.0 <Error> (thread=qReader, member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet...I have a number of these apps running simultaneously between two machines. At about the same time all the instances of the app running on one machine experienced the same issue. It looks like those members received cluster heartbeats which did not include the memeber so they left the cluster. They all then tried to rejoin but did not get a timely handshake back from a few members (20,21,39) so they just gave up. Is this correct behavior? Is there something I can do so it continues to reconnect? At a minimum can I somehow listen for this situation and do a System.exit(-1) so the apps' startup scripts know to restart them?
Thanks,
Andrew
The (almost) full log including the bit posted above is:
2010-12-15 04:15:18.478/17.147 Oracle Coherence 3.6.1.0 <Info> (thread=qReader, member=n/a): Loaded operational configuration from "jar:file:/Z:/coherence/lib/coherence.jar!/tangosol-coherence.xml"
2010-12-15 04:15:18.498/17.167 Oracle Coherence 3.6.1.0 <Info> (thread=qReader, member=n/a): Loaded operational overrides from "jar:file:/Z:/coherence/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
Oracle Coherence Version 3.6.1.0 Build 19636
Grid Edition: Development mode
Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
2010-12-15 04:15:19.122/17.791 Oracle Coherence GE 3.6.1.0 <Info> (thread=qReader, member=n/a): Loaded cache configuration from "file:/Z:/coherence/cache-config.xml"
2010-12-15 04:15:24.853/23.522 Oracle Coherence GE 3.6.1.0 <Info> (thread=Cluster, member=n/a): Failed to satisfy the variance: allowed=16, actual=52
2010-12-15 04:15:24.853/23.522 Oracle Coherence GE 3.6.1.0 <Info> (thread=Cluster, member=n/a): Increasing allowable variance to 20
2010-12-15 04:15:25.884/24.553 Oracle Coherence GE 3.6.1.0 <Info> (thread=Cluster, member=n/a): This Member(Id=16, Timestamp=2010-12-15 04:15:29.001, Address=192.168.3.6:8092, MachineId=27140, Location=machine:mothra,process:5888,member:six, Role=RediquoteclientRediQuoteClient, Edition=Grid Edition, Mode=Development, CpuCount=32, SocketCount=32) joined cluster "dev" with senior Member(Id=1, Timestamp=2010-12-14 20:01:47.154, Address=192.168.3.20:8088, MachineId=27412, Location=machine:amd4,process:4292,member:Administrator, Role=CoherenceServer, Edition=Grid Edition, Mode=Development, CpuCount=8, SocketCount=2)
2010-12-15 04:15:26.214/24.883 Oracle Coherence GE 3.6.1.0 <Info> (thread=qReader, member=n/a): Started cluster Name=dev
Group{Address=225.0.0.1, Port=54321, TTL=4}
MasterMemberSet
ThisMember=Member(Id=16, Timestamp=2010-12-15 04:15:29.001, Address=192.168.3.6:8092, MachineId=27140, Location=machine:mothra,process:5888,member:six, Role=RediquoteclientRediQuoteClient)
OldestMember=Member(Id=1, Timestamp=2010-12-14 20:01:47.154, Address=192.168.3.20:8088, MachineId=27412, Location=machine:amd4,process:4292,member:Administrator, Role=CoherenceServer)
ActualMemberSet=MemberSet(Size=15, BitSetCount=2
    Member(Id=1, Timestamp=2010-12-14 20:01:47.154, Address=192.168.3.20:8088, MachineId=27412, Location=machine:amd4,process:4292,member:Administrator, Role=CoherenceServer)
    Member(Id=2, Timestamp=2010-12-14 20:01:50.669, Address=192.168.3.20:8090, MachineId=27412, Location=machine:amd4,process:6048,member:Administrator, Role=CoherenceServer)
    Member(Id=3, Timestamp=2010-12-14 20:01:51.794, Address=192.168.3.20:8092, MachineId=27412, Location=machine:amd4,process:6980,member:Administrator, Role=CoherenceServer)
    Member(Id=4, Timestamp=2010-12-15 02:33:41.403, Address=192.168.3.5:8088, MachineId=27139, Location=machine:blackjack,process:12420,member:Administrator, Role=DJclientStartMe)
    Member(Id=5, Timestamp=2010-12-15 02:56:49.727, Address=192.168.3.5:8090, MachineId=27139, Location=machine:blackjack,process:7520,member:Administrator, Role=DJclientBboClient)
    Member(Id=7, Timestamp=2010-12-15 04:11:43.521, Address=192.168.3.5:8092, MachineId=27139, Location=machine:blackjack,process:7456,member:JD, Role=PE)
    Member(Id=8, Timestamp=2010-12-15 04:15:07.121, Address=192.168.3.7:8088, MachineId=27399, Location=machine:amd2,process:8036,member:ten, Role=RediquoteclientRediQuoteClient)
    Member(Id=9, Timestamp=2010-12-15 04:15:07.27, Address=192.168.3.7:8090, MachineId=27399, Location=machine:amd2,process:6328,member:twelve, Role=RediquoteclientRediQuoteClient)
    Member(Id=10, Timestamp=2010-12-15 04:15:07.295, Address=192.168.3.7:8092, MachineId=27399, Location=machine:amd2,process:2028,member:three, Role=RediquoteclientRediQuoteClient)
    Member(Id=11, Timestamp=2010-12-15 04:15:07.413, Address=192.168.3.7:8094, MachineId=27399, Location=machine:amd2,process:2744,member:two, Role=RediquoteclientRediQuoteClient)
    Member(Id=12, Timestamp=2010-12-15 04:15:11.511, Address=192.168.3.7:8096, MachineId=27399, Location=machine:amd2,process:2704,member:one, Role=RediquoteclientRediQuoteClient)
    Member(Id=13, Timestamp=2010-12-15 04:15:23.773, Address=192.168.3.6:8088, MachineId=27140, Location=machine:mothra,process:8424,member:five, Role=RediquoteclientRediQuoteClient)
    Member(Id=14, Timestamp=2010-12-15 04:15:24.957, Address=192.168.3.6:8090, MachineId=27140, Location=machine:mothra,process:8480,member:four, Role=RediquoteclientRediQuoteClient)
    Member(Id=15, Timestamp=2010-12-15 04:15:28.992, Address=192.168.3.6:8094, MachineId=27140, Location=machine:mothra,process:5152,member:seven, Role=RediquoteclientRediQuoteClient)
    Member(Id=16, Timestamp=2010-12-15 04:15:29.001, Address=192.168.3.6:8092, MachineId=27140, Location=machine:mothra,process:5888,member:six, Role=RediquoteclientRediQuoteClient)
RecycleMillis=1200000
RecycleSet=MemberSet(Size=0,BitSetCount=0
TcpRing{Connections=[15]}
IpMonitor{AddressListSize=3}
2010-12-15 07:12:32.467/10651.136 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 86107 ms communication delay (probable remote GC) with Member(Id=21, Timestamp=2010-12-15 05:56:59.648, Address=192.168.3.20:8096, MachineId=27412, Location=machine:amd4,process:3844,member:Administrator, Role=TvuMainTVU); 447 packets rescheduled, PauseRate=0.0189, Threshold=1878
2010-12-15 07:12:42.215/10660.884 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 49852 ms communication delay (probable remote GC) with Member(Id=20, Timestamp=2010-12-15 05:56:02.412, Address=192.168.3.20:8098, MachineId=27412, Location=machine:amd4,process:4704,member:Administrator, Role=StatsStatsLoader2); 266 packets rescheduled, PauseRate=0.0107, Threshold=1878
2010-12-15 07:16:32.750/10891.419 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 3372 ms communication delay (probable remote GC) with Member(Id=18, Timestamp=2010-12-15 05:40:07.904, Address=192.168.3.20:8094, MachineId=27412, Location=machine:amd4,process:5764,member:Administrator, Role=A1bookBinaryMainA1Multicast); 33 packets rescheduled, PauseRate=5.0E-4, Threshold=1612
2010-12-15 07:26:31.208/11489.878 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 4819 ms communication delay (probable remote GC) with Member(Id=18, Timestamp=2010-12-15 05:40:07.904, Address=192.168.3.20:8094, MachineId=27412, Location=machine:amd4,process:5764,member:Administrator, Role=A1bookBinaryMainA1Multicast); 41 packets rescheduled, PauseRate=0.0012, Threshold=1456
2010-12-15 07:47:21.567/12740.237 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 7115 ms communication delay (probable remote GC) with Member(Id=20, Timestamp=2010-12-15 05:56:02.412, Address=192.168.3.20:8098, MachineId=27412, Location=machine:amd4,process:4704,member:Administrator, Role=StatsStatsLoader2); 52 packets rescheduled, PauseRate=0.0085, Threshold=1612
2010-12-15 07:47:49.067/12767.736 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 8614 ms communication delay (probable remote GC) with Member(Id=21, Timestamp=2010-12-15 05:56:59.648, Address=192.168.3.20:8096, MachineId=27412, Location=machine:amd4,process:3844,member:Administrator, Role=TvuMainTVU); 60 packets rescheduled, PauseRate=0.0142, Threshold=1696
2010-12-15 07:56:32.988/13291.657 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 11513 ms communication delay (probable remote GC) with Member(Id=21, Timestamp=2010-12-15 05:56:59.648, Address=192.168.3.20:8096, MachineId=27412, Location=machine:amd4,process:3844,member:Administrator, Role=TvuMainTVU); 74 packets rescheduled, PauseRate=0.0147, Threshold=1612
2010-12-15 08:51:33.890/16592.559 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 33650 ms communication delay (probable remote GC) with Member(Id=20, Timestamp=2010-12-15 05:56:02.412, Address=192.168.3.20:8098, MachineId=27412, Location=machine:amd4,process:4704,member:Administrator, Role=StatsStatsLoader2); 184 packets rescheduled, PauseRate=0.0085, Threshold=1456
2010-12-15 08:52:22.802/16641.471 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 10437 ms communication delay (probable remote GC) with Member(Id=18, Timestamp=2010-12-15 05:40:07.904, Address=192.168.3.20:8094, MachineId=27412, Location=machine:amd4,process:5764,member:Administrator, Role=A1bookBinaryMainA1Multicast); 68 packets rescheduled, PauseRate=0.0016, Threshold=1129
2010-12-15 08:53:23.232/16701.901 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 5682 ms communication delay (probable remote GC) with Member(Id=18, Timestamp=2010-12-15 05:40:07.904, Address=192.168.3.20:8094, MachineId=27412, Location=machine:amd4,process:5764,member:Administrator, Role=A1bookBinaryMainA1Multicast); 45 packets rescheduled, PauseRate=0.0020, Threshold=1073
2010-12-15 08:53:50.802/16729.471 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 15112 ms communication delay (probable remote GC) with Member(Id=39, Timestamp=2010-12-15 07:57:53.415, Address=192.168.3.20:8102, MachineId=27412, Location=machine:amd4,process:4596,member:Administrator, Role=ex_viewer); 92 packets rescheduled, PauseRate=0.0044, Threshold=1785
2010-12-15 08:53:50.814/16729.483 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 1263 ms communication delay (probable remote GC) with Member(Id=21, Timestamp=2010-12-15 05:56:59.648, Address=192.168.3.20:8096, MachineId=27412, Location=machine:amd4,process:3844,member:Administrator, Role=TvuMainTVU); 23 packets rescheduled, PauseRate=0.0101, Threshold=1532
2010-12-15 08:54:36.660/16775.329 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 76110 ms communication delay (probable remote GC) with Member(Id=20, Timestamp=2010-12-15 05:56:02.412, Address=192.168.3.20:8098, MachineId=27412, Location=machine:amd4,process:4704,member:Administrator, Role=StatsStatsLoader2); 396 packets rescheduled, PauseRate=0.0155, Threshold=1384
2010-12-15 08:54:36.915/16775.584 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 5302 ms communication delay (probable remote GC) with Member(Id=21, Timestamp=2010-12-15 05:56:59.648, Address=192.168.3.20:8096, MachineId=27412, Location=machine:amd4,process:3844,member:Administrator, Role=TvuMainTVU); 43 packets rescheduled, PauseRate=0.0105, Threshold=1456
2010-12-15 08:55:28.984/16827.653 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 4293 ms communication delay (probable remote GC) with Member(Id=21, Timestamp=2010-12-15 05:56:59.648, Address=192.168.3.20:8096, MachineId=27412, Location=machine:amd4,process:3844,member:Administrator, Role=TvuMainTVU); 38 packets rescheduled, PauseRate=0.0109, Threshold=1384
2010-12-15 08:56:07.114/16865.783 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 3385 ms communication delay (probable remote GC) with Member(Id=18, Timestamp=2010-12-15 05:40:07.904, Address=192.168.3.20:8094, MachineId=27412, Location=machine:amd4,process:5764,member:Administrator, Role=A1bookBinaryMainA1Multicast); 33 packets rescheduled, PauseRate=0.0023, Threshold=1020
2010-12-15 08:56:55.091/16913.760 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 1398 ms communication delay (probable remote GC) with Member(Id=21, Timestamp=2010-12-15 05:56:59.648, Address=192.168.3.20:8096, MachineId=27412, Location=machine:amd4,process:3844,member:Administrator, Role=TvuMainTVU); 23 packets rescheduled, PauseRate=0.0109, Threshold=1315
2010-12-15 08:57:36.620/16955.289 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 9830 ms communication delay (probable remote GC) with Member(Id=18, Timestamp=2010-12-15 05:40:07.904, Address=192.168.3.20:8094, MachineId=27412, Location=machine:amd4,process:5764,member:Administrator, Role=A1bookBinaryMainA1Multicast); 66 packets rescheduled, PauseRate=0.0031, Threshold=969
2010-12-15 08:57:36.825/16955.494 Oracle Coherence GE 3.6.1.0 <Warning> (thread=PacketPublisher, member=16): Experienced a 127134 ms communication delay (probable remote GC) with Member(Id=39, Timestamp=2010-12-15 07:57:53.415, Address=192.168.3.20:8102, MachineId=27412, Location=machine:amd4,process:4596,member:Administrator, Role=ex_viewer); 650 packets rescheduled, PauseRate=0.0394, Threshold=1696
2010-12-15 08:59:22.500/17061.169 Oracle Coherence GE 3.6.1.0 <Error> (thread=Cluster, member=16): Received cluster heartbeat from the senior Member(Id=1, Timestamp=2010-12-14 20:01:47.154, Address=192.168.3.20:8088, MachineId=27412, Location=machine:amd4,process:4292,member:Administrator, Role=CoherenceServer) that does not contain this Member(Id=16, Timestamp=2010-12-15 04:15:29.001, Address=192.168.3.6:8092, MachineId=27140, Location=machine:mothra,process:5888,member:six, Role=RediquoteclientRediQuoteClient); stopping cluster service.
2010-12-15 08:59:22.504/17061.173 Oracle Coherence GE 3.6.1.0 <Error> (thread=Cluster, member=16): Full Thread Dump
Thread[Thread-3,5,main]
     java.lang.Object.wait(Native Method)
     rediquoteclient.QuoteServerLink.pause(QuoteServerLink.java:158)
     rediquoteclient.QuoteServerLink$1.run(QuoteServerLink.java:54)
     java.lang.Thread.run(Thread.java:619)
Thread[Cluster|Member(Id=16, Timestamp=2010-12-15 04:15:29.001, Address=192.168.3.6:8092, MachineId=27140, Location=machine:mothra,process:5888,member:six, Role=RediquoteclientRediQuoteClient),5,Cluster]
     java.lang.Thread.dumpThreads(Native Method)
     java.lang.Thread.getAllStackTraces(Thread.java:1487)
     com.tangosol.net.GuardSupport.logStackTraces(GuardSupport.java:810)
     com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService$SeniorMemberHeartbeat.onReceived(ClusterService.CDB:33)
     com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:11)
     com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:33)
     com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.onNotify(ClusterService.CDB:3)
     com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     java.lang.Thread.run(Thread.java:619)
Thread[Finalizer,8,system]
     java.lang.Object.wait(Native Method)
     java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
     java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
     java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
2010-12-15 08:59:23.722/17062.391 Oracle Coherence GE 3.6.1.0 <Info> (thread=qReader, member=16): Restarting NamedCache: quotes.REDI
2010-12-15 08:59:23.723/17062.392 Oracle Coherence GE 3.6.1.0 <Info> (thread=qReader, member=16): Restarting Service: DistributedQuotesCacheService
2010-12-15 08:59:23.723/17062.392 Oracle Coherence GE 3.6.1.0 <Info> (thread=qReader, member=n/a): Restarting cluster
2010-12-15 08:59:25.987/17064.656 Oracle Coherence GE 3.6.1.0 <Info> (thread=Cluster, member=n/a): This Member(Id=43, Timestamp=2010-12-15 08:59:44.971, Address=192.168.3.6:8092, MachineId=27140, Location=machine:mothra,process:5888,member:six, Role=RediquoteclientRediQuoteClient, Edition=Grid Edition, Mode=Development, CpuCount=32, SocketCount=32) joined cluster "dev" with senior Member(Id=1, Timestamp=2010-12-14 20:01:47.154, Address=192.168.3.20:8088, MachineId=27412, Location=machine:amd4,process:4292,member:Administrator, Role=CoherenceServer, Edition=Grid Edition, Mode=Development, CpuCount=8, SocketCount=2)
2010-12-15 09:03:59.364/17338.033 Oracle Coherence GE 3.6.1.0 <Error> (thread=Cluster, member=n/a): Detected soft timeout) of {WrapperGuardable Guard{Daemon=IpMonitor} Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_JOINED), Id=0, Version=3.6, OldestMemberId=1}}
2010-12-15 09:03:59.370/17338.039 Oracle Coherence GE 3.6.1.0 <Warning> (thread=Recovery Thread, member=n/a): Attempting recovery of Guard{Daemon=IpMonitor}
2010-12-15 09:04:25.193/17363.862 Oracle Coherence GE 3.6.1.0 <Error> (thread=Cluster, member=n/a): validatePolls: This service timed-out due to unanswered handshake request. Manual intervention is required to stop the members that have not responded to this Poll
PollId=2, active
InitTimeMillis=1292425166002
Service=Cluster (0)
RespondedMemberSet=[1,2,3,4,5,6,7,8,9,10,11,12,17,19,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,40,41,42]
LeftMemberSet=[20,21,39]
RemainingMemberSet=[18]
2010-12-15 09:04:25.197/17363.866 Oracle Coherence GE 3.6.1.0 <Error> (thread=qReader, member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
    OldestMember=n/a
    ActualMemberSet=MemberSet(Size=33, BitSetCount=2
      Member(Id=1, Timestamp=2010-12-14 20:01:47.154, Address=192.168.3.20:8088, MachineId=27412, Location=machine:amd4,process:4292,member:Administrator, Role=CoherenceServer)
      Member(Id=2, Timestamp=2010-12-14 20:01:50.669, Address=192.168.3.20:8090, MachineId=27412, Location=machine:amd4,process:6048,member:Administrator, Role=CoherenceServer)
      Member(Id=3, Timestamp=2010-12-14 20:01:51.794, Address=192.168.3.20:8092, MachineId=27412, Location=machine:amd4,process:6980,member:Administrator, Role=CoherenceServer)
      Member(Id=5, Timestamp=2010-12-15 02:56:49.727, Address=192.168.3.5:8090, MachineId=27139, Location=machine:blackjack,process:7520,member:Administrator, Role=DJclientBboClient)
      Member(Id=7, Timestamp=2010-12-15 04:11:43.521, Address=192.168.3.5:8092, MachineId=27139, Location=machine:blackjack,process:7456,member:JD, Role=PE)
      Member(Id=8, Timestamp=2010-12-15 04:15:07.121, Address=192.168.3.7:8088, MachineId=27399, Location=machine:amd2,process:8036,member:ten, Role=RediquoteclientRediQuoteClient)
      Member(Id=9, Timestamp=2010-12-15 04:15:07.27, Address=192.168.3.7:8090, MachineId=27399, Location=machine:amd2,process:6328,member:twelve, Role=RediquoteclientRediQuoteClient)
      Member(Id=10, Timestamp=2010-12-15 04:15:07.295, Address=192.168.3.7:8092, MachineId=27399, Location=machine:amd2,process:2028,member:three, Role=RediquoteclientRediQuoteClient)
      Member(Id=11, Timestamp=2010-12-15 04:15:07.413, Address=192.168.3.7:8094, MachineId=27399, Location=machine:amd2,process:2744,member:two, Role=RediquoteclientRediQuoteClient)
      Member(Id=12, Timestamp=2010-12-15 04:15:11.511, Address=192.168.3.7:8096, MachineId=27399, Location=machine:amd2,process:2704,member:one, Role=RediquoteclientRediQuoteClient)
      Member(Id=17, Timestamp=2010-12-15 05:24:58.776, Address=192.168.3.5:8096, MachineId=27139, Location=machine:blackjack,process:9836,member:Administrator, Role=DJclientRestarter)
      Member(Id=18, Timestamp=2010-12-15 05:40:07.904, Address=192.168.3.20:8094, MachineId=27412, Location=machine:amd4,process:5764,member:Administrator, Role=A1bookBinaryMainA1Multicast)
      Member(Id=22, Timestamp=2010-12-15 06:00:07.414, Address=192.168.3.25:8088, MachineId=27417, Location=machine:amd6,process:316,member:Administrator, Role=OmsOms)
      Member(Id=23, Timestamp=2010-12-15 06:00:09.872, Address=192.168.3.7:8098, MachineId=27399, Location=machine:amd2,process:2984,member:user, Role=PEQuoteProcessor)
      Member(Id=24, Timestamp=2010-12-15 06:00:51.201, Address=192.168.3.24:8088, MachineId=27416, Location=machine:Amd5,process:3096,member:St, Role=OmsOms)
      Member(Id=25, Timestamp=2010-12-15 06:52:44.897, Address=192.168.3.32:8088, MachineId=27424, Location=machine:themysticx,process:3804,member:Tony, Role=OmsOms)
      Member(Id=26, Timestamp=2010-12-15 07:13:05.082, Address=192.168.3.26:8088, MachineId=27418, Location=machine:dabulls,process:3256,member:St, Role=BboBBOClientMain)
      Member(Id=27, Timestamp=2010-12-15 07:27:00.105, Address=192.168.3.120:8090, MachineId=27512, Location=machine:TEST-1234,process:2936,member:TEST, Role=EXV)
      Member(Id=28, Timestamp=2010-12-15 07:27:00.183, Address=192.168.3.120:8088, MachineId=27512, Location=machine:TEST-1234,process:3116,member:TEST, Role=oew)
      Member(Id=29, Timestamp=2010-12-15 07:27:00.251, Address=192.168.3.120:8092, MachineId=27512, Location=machine:TEST-1234,process:272,member:TEST, Role=OV)
      Member(Id=30, Timestamp=2010-12-15 07:51:41.145, Address=192.168.3.116:8088, MachineId=27508, Location=machine:BE,process:2144,member:user, Role=EXV)
      Member(Id=32, Timestamp=2010-12-15 07:34:03.385, Address=192.168.3.5:8098, MachineId=27139, Location=machine:blackjack,process:5836,member:WayneN, Role=PE)
      Member(Id=35, Timestamp=2010-12-15 08:22:49.77, Address=192.168.3.121:8092, MachineId=27513, Location=machine:Hd,process:4052,member:Hd, Role=oew)
      Member(Id=36, Timestamp=2010-12-15 07:51:41.529, Address=192.168.3.116:8090, MachineId=27508, Location=machine:BE,process:2292,member:user, Role=OV)
      Member(Id=37, Timestamp=2010-12-15 07:51:41.556, Address=192.168.3.116:8091, MachineId=27508, Location=machine:BE,process:2064,member:user, Role=oew)
      Member(Id=38, Timestamp=2010-12-15 07:51:41.863, Address=192.168.3.116:8094, MachineId=27508, Location=machine:BE,process:2108,member:user, Role=PE)
      Member(Id=40, Timestamp=2010-12-15 08:06:00.705, Address=192.168.3.5:8100, MachineId=27139, Location=machine:blackjack,process:5484,member:ChrisL, Role=PE)
      Member(Id=41, Timestamp=2010-12-15 08:22:59.722, Address=192.168.3.121:8094, MachineId=27513, Location=machine:Hd,process:2972,member:Hd, Role=PE)
      Member(Id=43, Timestamp=2010-12-15 08:59:44.971, Address=192.168.3.6:8092, MachineId=27140, Location=machine:mothra,process:5888,member:six, Role=RediquoteclientRediQuoteClient)
      Member(Id=44, Timestamp=2010-12-15 09:01:17.056, Address=192.168.3.121:8090, MachineId=27513, Location=machine:Hd,process:860,member:Hd)
      Member(Id=45, Timestamp=2010-12-15 09:01:35.962, Address=192.168.3.5:8094, MachineId=27139, Location=machine:blackjack,process:4852,member:Administrator)
      Member(Id=46, Timestamp=2010-12-15 09:01:41.282, Address=192.168.3.5:8088, MachineId=27139, Location=machine:blackjack,process:12420,member:Administrator)
      Member(Id=47, Timestamp=2010-12-15 09:02:44.877, Address=192.168.3.121:8088, MachineId=27513, Location=machine:Hd,process:2804,member:Hd)
    MemberId/ServiceVersion/ServiceJoined/MemberState
      1/3.6/Tue Dec 14 20:01:47 CST 2010/JOINED,
      2/3.6/Tue Dec 14 20:01:50 CST 2010/JOINED,
      3/3.6/Tue Dec 14 20:01:51 CST 2010/JOINED,
      5/3.6/Wed Dec 15 02:56:49 CST 2010/JOINED,
      7/3.6/Wed Dec 15 04:11:43 CST 2010/JOINED,
      8/3.6/Wed Dec 15 04:15:07 CST 2010/JOINED,
      9/3.6/Wed Dec 15 04:15:07 CST 2010/JOINED,
      10/3.6/Wed Dec 15 04:15:07 CST 2010/JOINED,
      11/3.6/Wed Dec 15 04:15:07 CST 2010/JOINED,
      12/3.6/Wed Dec 15 04:15:11 CST 2010/JOINED,
      17/3.6/Wed Dec 15 05:24:58 CST 2010/JOINED,
      18/3.6/Wed Dec 15 05:40:07 CST 2010/JOINING,
      22/3.6/Wed Dec 15 06:00:07 CST 2010/JOINED,
      23/3.6/Wed Dec 15 06:00:09 CST 2010/JOINED,
      24/3.6/Wed Dec 15 06:00:51 CST 2010/JOINED,
      25/3.6/Wed Dec 15 06:52:44 CST 2010/JOINED,
      26/3.6/Wed Dec 15 07:13:05 CST 2010/JOINED,
      27/3.6/Wed Dec 15 07:27:00 CST 2010/JOINED,
      28/3.6/Wed Dec 15 07:27:00 CST 2010/JOINED,
      29/3.6/Wed Dec 15 07:27:00 CST 2010/JOINED,
      30/3.6/Wed Dec 15 07:51:41 CST 2010/JOINED,
      32/3.6/Wed Dec 15 07:34:03 CST 2010/JOINED,
      35/3.6/Wed Dec 15 08:22:49 CST 2010/JOINED,
      36/3.6/Wed Dec 15 07:51:41 CST 2010/JOINED,
      37/3.6/Wed Dec 15 07:51:41 CST 2010/JOINED,
      38/3.6/Wed Dec 15 07:51:41 CST 2010/JOINED,
      40/3.6/Wed Dec 15 08:06:00 CST 2010/JOINED,
      41/3.6/Wed Dec 15 08:22:59 CST 2010/JOINED,
      43/3.6/Wed Dec 15 08:59:44 CST 2010/JOINED,
      44/3.6/Wed Dec 15 09:01:17 CST 2010/JOINED,
      45/3.6/Wed Dec 15 09:01:35 CST 2010/JOINED,
      46/3.6/Wed Dec 15 09:01:41 CST 2010/JOINED,
      47/3.6/Wed Dec 15 09:02:44 CST 2010/JOINED
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
     at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:636)
     at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
     at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
     at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7)
     at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
     at com.tangosol.coherence.component.util.SafeService.restartService(SafeService.CDB:22)
     at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:39)
     at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureRunningCacheService(SafeCacheService.CDB:3)
     at com.tangosol.coherence.component.util.SafeNamedCache$CacheAction.run(SafeNamedCache.CDB:3)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:337)
     at com.tangosol.coherence.component.util.SafeNamedCache.restartNamedCache(SafeNamedCache.CDB:8)
     at com.tangosol.coherence.component.util.SafeNamedCache.ensureRunningNamedCache(SafeNamedCache.CDB:33)
     at com.tangosol.coherence.component.util.SafeNamedCache.getRunningNamedCache(SafeNamedCache.CDB:1)
     at com.tangosol.coherence.component.util.SafeNamedCache.putAll(SafeNamedCache.CDB:1)
     at rediquoteclient.CoherencePublisher$1.run(CoherencePublisher.java:105)
     at java.lang.Thread.run(Thread.java:619)

Ashbaernon said: Firstly, the complete error message is "This VI
is not executable. The full development version of Labview is required
to fix the errors"
"VI is not executable" can mean the VI is missing some component, but it can also mean the VI or one of its subVIs has not been compiled to the same version as your RTE (Run-Time Engine). I've specifically seen this using the TestStand full-featured LabVIEW user interface, which was last compiled with LabVIEW 7.x (5 years ago), yet shipped with TS 4. Anyhow, if this is the cause, the solution is to:
Open the top level VI and any dynamically called VIs (i.e. VIs called by VI Server).
Holding down Ctrl and Shift, press the Run arrow to recompile all VIs in memory.
File >> Save All (or Ctrl-Shift-S)
Rebuild your EXE.
-Jason
Message Edited by LabBEAN on 02-14-2009 10:28 PM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

TestStand 4.1 manual

Similar Messages

Maybe you are looking for