error in error code database

[edwin]

Hi,

I have this error (screenshot provided), which problem is its asking for a password. I think this vi is ni developed. So, I have tried to reinstall labview but still this cannot work. Thanks, for any help.

Best regards,

Edwin

[tst]

The error means that the VI tries to call a DLL function and does not find it (the function or the DLL file). You're right that the VI was developed by NI.

How did this start? If it started right after you installed LV, maybe your CD is corrupted and didn't install LV properly.
If that is the case, you should probably call your local NI office and get a replacement CD. Also, Uninstalling would probably not be a bad idea before attempting a reinstallation.

Oh, and I'm sure you noticed that zipping your image has caused to shrink to about 2% of its original size. The same could have been accomplished if you had saved it as a .JPG, .GIF or .PNG, instead of .BMP.

[Philip_Courtois]

Hi Edwin,

The error is most likely caused by opening an LLB in a newer version of LabVIEW than the version it was developed on. It is commonly seen with the "Error Code Database.vi" when upgrading from LabVIEW 6.x to 7.x, if the original main VI using the "Simple Error Handler.vi" and it was saved in an LLB including the VI.LIB files ("File » Save with Options... » Include vi.lib files"). To fix the issue, make sure to use the VI.LIB files (VIs) from the current development system on the machine. You can replace for example the "Simple Error Handler.vi" by right-clicking it on the block diagram, choose "Replace" and then browse to the "Simple Error Handler.vi" in the palette.

Please refer to the following KnowledgeBase about this error:

My Copy of the Error Code Database VI from LabVIEW 6.1 Does Not Work in LabVIEW 7.0

To not run into this error again in the future, do not save the VI.LIB with the VI, unless you are distributing to a system without the same VI.LIB files available (e.g. from Full Development system to Base Package).

Let me know if you get it to work, thanks.

Have fun!

[edwin]

Thank you very much for all of your helps

well I manage to run this on seems a weird way. I open a vi that runs well, then i open that 'problematic' vi. Suddenly all error dissapear... If i open it without open other vi first, the problem still persist. Then i do what philip says, save with option, etc. ok then it runs well, without opening other vi it can run too. but it can only run when main vi is on .dll file. If i separate the main vi (copy paste and put to other places) the error still there. But its ok, it can work that ways.

Best regards,

Edwin

[tst]

This isn't weird at all - LV can only hold one VI of a certain name at a time in memory. If another VI with the same name is opened, LV will tell you that it loaded the VI which is already in its memory instead of your VI. When you open a VI that runs well, Error Code DB is loaded from your VI.lib directory, and you should get a message telling you (among other things) that the VI was loaded from your VI.lib directory. When you save it, it remembers it loaded the VI from the VI.lib directory, so it works fine.

When you copy the LLB, the relative path probably gets lost and LV starts looking for the VI. The first place it finds it is in the LLB, but because that's an old version, you get errors again.

Here is what you should do - After you open it and it works well, do a regular save (File>>Save). Then, close it, open it again and choose Save with Option>>Development Distribution. Here you can choose to include or not to include VI.lib VIs, but either way, the old Error Code DB VI will not be saved with your new file.