Exception Error 0x5F4 deletechildobject.vi

[JLS]

Hello,

As is usually the case with test machines, since the time I last tried this, someone has installed NI software.  I'll remove it, try the new attached code, and post results!

Best Regards,

JLS

[JLS]

Hello,

The first time I run your exe it runs without a problem.  The second time it runs and I receive the same error.  Perhaps something is still funny with the paths (the path indicator is NOT correct the second time I run it - it's empty).

I'd really like to reproduce this, or perhaps confirm that it doesn't break on a machine here, so that we can deduce the cause of the problem!

Best Regards,

JLS

[ASTDan]

Hello

It is running as expected.

You need to replace the .tdm file with the orginal.  What is happening is the first time you run the program it deletes the  run group.  If you run the program again the run group is deleted and that error is generated because there is nothing to delete.

When you open the zip file save a copy of the tdm in a different location.  Everytime you run the program replace the .tdm file with the copy.

Dan

[JLS]

Hello again,

I understand, sorry for the confusion on that!  I run it on a machine with only the runtime engine and it works as expected every time (when I replace the file as I now understand).  Is there anything else about the customer's machine that could be causing a problem in general?  We may want to wipe it clean of NI software, and start again, even if it's just the runtime engine.

I'm afraid this is going to be rather difficult to troubleshoot from a purely theoretical basis - being able to reproduce it will go a long way to figuring out the problem, and then the solution!

I look forward to hearing back from you!

Best Regards,

JLS

[ASTDan]

You are seeing what I am seeing.  I can't reproduce the error on any of my machines.  However all my customers machines crash.  I have tried running the .exe on a machine that never had NI software installed, and it crashed.  I tried both 7.1 and 7.1.1 runtime engines.

My customer is also reporting a new error.  I have attached it below. I can't reproduce it on my machines.  Maybe this will give some more insight as to what is going on.  Thank you for your help in trying to resolve this issue.

[JLS]

Hello,

That error is often indicative of an unhandled exception having been thrown in a dll - since the dll didn't handle it, it's passed up to LabVIEW that way.  The note that it may have corrupted LabVIEW's memory indicates that the result of the exception may have been to write on LabVIEW's memory space, which can cause any number of errors. 

You noted that you can reproduce this on computers that never had NI software installed, so in order to reproduce this I am having a machine ghosted with an image containing only XP - I will put just the LabVIEW 7.1 runtime engine on it and try again.  One other interesting note is that I found some documentation regarding a problem with building and using dlls from VIs which use the storage VIs.  I think it has already been addressed, but perhaps there is a connection here, because that error would not always occur, and depended on when memory was freed by the OS.  Perhaps there is something similar going on here with the exe, but the fact that the only correlation we can find is ever having NI software installed is a mystery... I don't think the exe's behavior (even if related to that issue) should be dependent on ever having NI software installed.  This may sound crazy, but can you try putting some NI software on it, just to see if that actually solves the problem?  Perhaps you can install the NI-VISA runtime engine or something like that... just as a sanity check.  You can do so from our drivers and updates page:

http://digital.ni.com/softlib.nsf/MainPage?ReadForm&node=132010_US

The best case scenario is that I CAN reproduce the problem, because then I can officially CAR this to be formally addressed by R&D!

I'll repost with results, and it would be great if you can try the sanity-check experiment noted above, and post results here.

Best Regards,

JLS

[JLS]

Hello,

I successfully reproduced the error on a freshly imaged machine, after installing only the 7.1 runtime engine.  I uninstalled it and tried version 7.1.1 and it failed as well, in line with your findings.  I have filed a corrective action request to R&D on this matter and will update you with whatever information I can.  I hope there is a solution which will not have to wait until a future release!

Thank you for your persistence on this issue!

Best Regards,

JLS