Build Error: Can't find distribution being built

Question

Greetings,
      I'm encountering an error similar to that described in another thread.    Here, though, the missing installer is the one being built.
If no additional installers are selected, the build succeeds.  If any installers located in the "local cache" are selected (I've tried three), then the App builder wants the location of the installer for the app. I'm trying to build.  The app being built has been installed on the development station, for some reason the App. builder now thinks it needs it.
Maybe some NI "working-file" or registry-entry needs to be flushed(?)
Any ideas are appreciated!
Cheers!  
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

Answer 1

Deborah Y wrote:
Hello Bill,
As Michael asked earlier, have you tried starting from scratch deleting and/or rebuilding the build configuration or project file? Going by the screenshot above having no specific error code, this would point towards looking at the Build Specifications->My Installer Properties box at the categories Source File and Source File Settings on the station this installer DOES work on and see where the discrepancies or missing files lie. Also looking at the Installer Destination under Product Info and then double checking Destinations and Registry would assure the issue doesn't lie there when you accidentally deleted some of those files.
Hello Deborah,
      As I mentioned earlier, the exact-same build works fine on another PC.  We use source-code control - it's EXACTLY the same .lvproj and file hierarchy.  The build properties you mentioned - Source File/Settings - are correct and identical on both stations.  But this is getting a bit off-track
Keep in mind that the installer error does not occur if no additional installers are selected.  If, say, LabVIEW 2009 Run-time is selected, then the error occurs.  Destinations for compiler or installer products are created/replaced every build, and anyway, unrelated to "C:\temp\temp".  C:\temp\temp" is where the installer-products were manually copied and where setup.exe was run.
If you want to help, please find-out how running a LabVIEW installer might change the Windows Registry, such that: dependencies which were associated with other NI installers have become associated with my, arbitrary, installed application.
In other words, registry damage appears to have been on by RUNning an installer - the damage then appears when reBUILDing the installer.  Hmmm, that's an experiment to do - build an empty/untitled VI - with LV 2009 RunTime and see what happens...
Thanks/Cheers!   
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)