Error 10 occurred at New VI Library.vi when building .exe

[nate]

This is driving me crazy!  What is causing this.  The program worked fine in 8.5.1 and before.  The only thing that has changed is that I had to create directories for each class in the Microsoft Report Generation Toolkit which was a huge pain itself.  See Building an EXE in LabVIEW 8.6 using the Report Generation Toolkit application note for more information.  Anyway, any suggestions would be much appreciated.

[CWolf]

Nate,

Did you see this KnowledgeBase Article that talks about Error 10 with the Application Builder?  If you already tried all these things, then it's hard to tell what would be causing this without some more information.  One thing to check, though, is that none of yur directory names have periods in the folder name.  I have seen at least one case where this caused error 10.  Also, make sure that you have Enable Debugging selected in the Application Builder. 

I hope this helps.

Christina

[nate]

I have tried everything metioned in the knowledgebase.  I can't find New VI Library.vi in my code anywhere.  It may be in one of the password protected VIs from NI which I can't see anyway.  The funny thing is that it only happens when I build my UI application.  When I build my RT application, there are no issues.

[CWolf]

Nate,

Have you tried creating an executable from other code (like an example program)?  Does this work fine? 

Also, if your code isn't too big, could you post it here so I could try it on my computer?  (Have you tried it on amy other computers?)

-Christina

[nate · Accepted solution]

After a lot more testing I think I have identified the problem.  Our executable uses the Microsoft Report Generation toolkit.  Due to how LabVIEW 8.6 has implemented the toolkit, it creates directories for each class of the toolkit to prevent name collisions.  Maybe LabVIEW should start using namespaces.  Anyway, we did not want the code to be visible to out customers.  We wanted it to be in a single executable.  So I found a knowledge base article that addresses the issue.  It's called "Managing the Resulting Files from a Build Containing LabVIEW Classes" and it's document id is 4OKDCDES.  Anyway this article says to add .llb destinations into the build so that instead of 5 directories with exposed VIs, you get 5 .llb.  This worked ok with no build issues, but then the article said to rename the .llb to .dll so the extra directories would appear to look like dlls.  The first time you build this it works, but if you build it again, it fails and you get error code 10.  You can then build it again and it will work.  So the problem has to do with renaming the extra .llb to .dll.