LabVIEW was unable to modify the password for the following VI: C:\Program Files\National Instruments\LabVIEW 2013\vi.lib\Utility\error.l\Error Code Database.vi. Open the block diagram of the VI to enter the current password before you build.

[sallesa]

Hello,

I am currently trying to build in 2013 a project created in 8.2, and now updated (and working) to 2013.

While building, labview gives me back the message I paste in the Subject this message.

I join snapshot of windows appearing during building process.

I tried solution already available on this forum like remove password in build properties.

So far i am stuck.

Any idea ?

thanks

[Bob_Schor]

It looks like the routine Manip_YR623 is attempting to do something with LabVIEW's database of error codes (which is password-protected to prevent users from "messing it up", not to mention that it is part of NI's Intellectual Property).  It is not clear why it should be doing this, nor why LabVIEW 8.2 would have allowed it.

Can you post this VI to let us see what might be causing this?  If not, I'd suggest trying to make a "smaller leap" than 8 years of LabVIEW development and try porting to, say, LabVIEW 8.6, then LabVIEW 2010 -- if you can pin down the LabVIEW version when the problem appears, then looking at the "What's New" section of that LabVIEW version may give you (and us) a clue.

Bob Schor

[sallesa · Accepted solution]

Hello,

Thanks for your answer.

Definetly the transition from 8.2 to 2013 was too aggressive.

The solution came from re-creating a build process from scratch under the same project.

No more error after that.

Lessosn learned: do not try to build a dll directly after updating your project from an older version of Labview.

This subject is then closed

[GerdW]

Lesson learned: give a SHORT, but descriptive subject line and put more text in the message body…

[nyc_(is_out_of_here)]

---

@sallesa wrote:

Hello,

Thanks for your answer.

Definetly the transition from 8.2 to 2013 was too aggressive.

The solution came from re-creating a build process from scratch under the same project.

No more error after that.

Lessosn learned: do not try to build a dll directly after updating your project from an older version of Labview.

This subject is then closed

---

Lesson learned should be don't mark your own post as the answer since you needed someone else's help to get your problem solved.

Very tacky.

[Hooovahh]

Lets just all agree that a good lesson to learn, would come from reading the unofficial guidelines

• Have a useful title.  The title of your question should never be "labview" for "fpga".  Your title should also not be a paragraph.  It should be a quick summary of the topics your post is going to discuss.
• You can thanks a person on the forum by giving them a Kudo.  A user on the forums can Kudo a post by another user once, but multiple users can Kudo the same post which can highlight posts that a collection of users find useful.

There are several useful things mentioned on having solutions marked too.