Michael,
I wasn't able to find any references to error code 2046300, but here are some things you can try:
- first recompile your VIs into LabVIEW 7.1 ( by opening and save them) before building them with App Builder 7.1
- save all of your VIs in a library and then select your top level VI from library when building the executable. Add any dynamic VIs and support files e.g. DLLs etc. Here is what I found another NI engineer posted on google about this to another customer for whom the above solution worked:
"The documentation doesn't explain this because it is not really necessary. What is necessary is that all of the linkages in your hierarchy of VIs are correct *before* building the application. I suspect that if you were to open your VIs in the LabVIEW deve
lopment environment and then close them, LabVIEW would start prompting you to save changes in your VIs. This indicates that the linkage information stored in the VIs does not reflect the actual state of the VIs on your computer (i.e. LabVIEW had to search to find a subVI rather than linking to the VI identified by the relative path stored in the calling VI). If you save these changes and then build the application, I bet it would work correctly.
Saving things to a new library via the Save With Options dialog is way of forcing the linkages to be correct, which is why it solved the problem for you.
- reinstall the application builder 7.1
- make sure you have run-time engine 7.1 installed before you run the executable
Zvezdana S.
National Instruments
