Vi not running when using NI´s SiimpleErrorHandler.vi (TS2010/LV2011) in runtime - Windows 7

[OnlyOne]

Hello,

i have a simple VI in LV2011 that i call as action in Teststand 2010.

In teststand the LAbview-Adapter is set to 2011-runtime.

The Vi cannot be executet if i use inside the SimpleErrorHandler.vi which creates this error-cluster for teststand.

When i delete this subvi then it can be executed.

Also if i run labvie win development-mode it works.

I already recompiled multiple time all labview-things and also complete drive C:

When i manually open the SimpleErrorHandler.vi then there is no * in the title which means it should be already compiled as version 2011.

Or are there any write-protected parts somewhere in the NI-directories?

Operating System is "Windows 7"

Thanks for all ideas.

[RayFarmer]

you might need this patch

http://joule.ni.com/nidu/cds/view/p/id/2102

[RayFarmer]

Hi,

.

I am running a small example which has a VI with the Simple Error Handler.vi . I am running Teststand 2010 SP1 with LabVIEW 2011 in Window 7 and I am not seeing your error condition.

I have switched to using the LabVIEW RTE 2011 and it runs fine.

I have attached my example

[Al.B]

Hi,

This sounds like an issue with the object cache in LabVIEW - see this article for details:

Why Can I Not Call a LabVIEW 2010 (SP1) VI from TestStand Using the LabVIEW 2010 (SP1) Run-Time Engi...

Let me know if the steps in this article fix the issue!

[OnlyOne]

@Ray Farmer: The example is mpt running. Exactly the same problem that i have.

"Picture not available"-text and blinking red icon.

Attachached a screenshot.

What search-pathes do you have set in teststand?

@Ballington: I cleared the cache, the directory is also not write protected.

[OnlyOne]

I tested on another PC with TS 4.2.1.83 / Labview 8.6. There i have also this problem when using runtime.

[RayFarmer]

That error is because it's looking for the VI in the Examples folder so if you have placed it somewhere else then it will not find it. Just use the browser and relink the VI.

[OnlyOne]

Strange things happen.

If i copy the vi to a new directory like c:\Example and set the path with browse-button then it works.

But when i move the file to my project-directory and change the path then its not working.
Also if i set it to "absolute-path" i get the red icon.

I have no idea why this happens. It is exactly the same vi which is working in another path.

[RayFarmer]

Hi,

do you have another copy of the SiimpleErrorHandler.vi  somewhere in your project directory?

[OnlyOne]

No, there no duplicate file.