Error 7 looking for "CMP Compare Hierarchies.vi" when comparing VI hierarchies

[bmihura]

Awww, it's password-protected so I can't tell what's wrong; only a National Instruments employee can debug that.

But it sounds like you need to uninstall LabVIEW, completely wipe out the LabVIEW 7.1 directory, then reinstall it.

Things are very broken on your machine.

[BVSmith]

I am having the same problem, and it is happening on *two* different installations of LabVIew 7.1.1.
It sounds more like there is something wrong with LabView and not the installations.
We have procmphier.llb in the proper place and even if I start "CMP Compare Hierarchies.vi" from
there we get the same error message. 
On a third system, we get an error 1 (invalid input parameter).

As a side note, it would be very useful if the infamous error 7 (file not found) would report the name of the file.

[JLS]

Hello,

The following other forum has responses to the same problem from another applications engineer which you may find helpful and insightful:

http://forums.ni.com/ni/board/message?board.id=170&message.id=151737&requireLogin=False

It explains that:

"This has previously been reported to be caused by one of the hierarchies not being of the same version of LabVIEW as the other. The workaround is to mass compile the old VIs by going to "Tools » Advanced » Mass Compile..." and selecting the directory or library that holds the old VIs."

It also explains that:

"Remember  that you cannot mass compile a VI if it is saved without the block diagram because the compilation process works by converting the block diagram into compiled code."

I hope this provides insight and is relevant for your particular instances of the problem!

Best Regards,

JLS

[BVSmith]

Both hierarchies were at LabView 7.1.1, but I mass compiled both of them anyway (before posting my message), but I still get the error.

[JLS]

Hello,

I wonder if you're recompile process is falling into the case "Remember  that you cannot mass compile a VI if it is saved without the block diagram because the compilation process works by converting the block diagram into compiled code."  Were the two VIs you are comparing originally built in the same version of LabVIEW? Are you comparing the hierarchies of the same 2 VIs in the cases you see this error, even across systems?  I can reproduce the error under the conditions that the other engineer noted (different versions of LabVIEW for the hierarchies being compared), but don't have problems when I have two VIs that were built in the same version.

I would like to determine if we have a new case where this error occurs, or if we are falling into the other known case in a somewhat disguised form.  If you can post your VIs here, I can also try on my machine, and include them in a corrective action request if it is determined that R&D should look into fixing a potential problem.

I look forward to hearing back from you!

Thank you,

Best Regards,

JLS

[BVSmith]

I was able to compare the VI hierarchies after some effort, and it may have been because one or more sub-VIs were from a different version of LabView, although I thought I had mass compiled the whole tree before comparing them.
Anyway, I requested to a National engineer that the whole process (compare vi hierarchies) be a little more explicit in the error reporting since it appears that any of the following can occur:

1. VIs are from different LabView versions
2. VI is password protected
3. VI not executable(syntax error)
4. VI saved without block diagram

These all produce the vague "Error 7".
At the very least, "Error 7" could include in its message the filename that can't be opened.

Thanks for your interest, JLS.

-BVSmith

[JLS]

Hello,

I am glad you were able to compare, and your concerns about the error message are great to report.  Go to ni.com and click Contact Us; you should then see a feedback section in the bottom left corner of the page - click the word feedback and you can submit a product suggestion to have that changed!

Thank you,

Best Regards,

JLS