Built application doesn't 'see' user.lib?

Question

New AppBuilder user here.
I seem to be having a problem building a standalone application that has a few custom VIs in it.  Debugging showed that it apparently refuses to recognize the custom VIs in my user.lib folder.  I tried disabling them in my source and recompiling, and the rest of it works fine.  Two are VIs in their own right, the third is a VI called from within an .LLB file, again in the user.lib folder.  None of the custom VIs contain any 'custom pieces' from elsewhere.
I'd built an installer to get the runtime engine, support files, &etc. on the target laptop and it apparently properly installed all these components.  Then I built the *.EXE separately.  No errors.
As a sanity-check, I built an EXE from another VI that uses only Labview-native VIs &etc. (i.e. nothing from the user.lib folder), 'ported it over to the target laptop, and it works perfectly.  I can only surmise that the EXE isn't properly 'seeing' stuff in the user.lib folder on the target machine.  The crashing EXE _does_ work properly on the source machine.
I'd even tried (seen in another forum posting) saving the source with the 'duplicate hierarchy' option set and building from _that_ copy.  No good.
The crashing EXE gives me the error: "Error -2147221164 occurred in class not registered in app.vi" on the laptop.  Googling this error number seems to show that it is an OS error number, with several ni.com-related postings which do not seem to apply to my situation.
Sound familiar to anybody?  I'm stumped.  Thanks for any help.

Answer 1

Hi GerdW,
Yes, I would have thought everything was included in the build too.
To me, it seems like the three VIs I'd written that I'm using are crashing the EXE on the laptop.  I can pull 'disable' structures around them, build the EXE again and put it on the laptop and everything else in the VI works fine (the three VIs are math-related and, now just output zero values to the data file, but let everything else in the VI function).
As I said: two of them are *.VI files and the third is a .VI inside a *.LLB file.  They are all IN the C:\Program Files\National Instruments\Lab VIEW 8.5\user.lib\ folders on both machines but it seems the build recognizes them on the source machine but NOT the laptop.
Nope - not doing any vi server stuff: everything is called directly and these are all standalone machines.  I've even copied the VI out of the LLB right into the user.lib folder (and properly updated the source) and get the same results.  Everything called from vi.lib works fine on both machines but stuff called from user.lib only works on the source machine.
I could understand it if the stuff wasn't IN the folder but they're identical.  After seeing the first time that things weren't recognized (running the installer I'd created, then the EXE) I physically brought over the entire user.lib folder from the source machine to the laptop, so I _know_ they're the same.
Thanks for your response - I appreciate any and all help.  This is the first time I've had problems building an EXE and, coincidentally, the first time I've done a build incorporating stuff from user.lib.  My next troubleshooting move will be to hardwire the contents of the offending sub-VIs directly into the main VI and see if it helps (as messy as it will look...).
 6.1, 7.1, 8.5 on Windows, 7.1, 8.6 on OSX