Getting "Error 10 occurred at Copy in Win Install..." when building application

[lgk]

I'm using a build script that worked last time I needed to build my application, however it is now giving me an Error 10 with a possible reason of Duplicate path.

I am attaching the image of the error message. Where do I look for the possible duplicate path?

Your message posting is not giving me warm fuzzy feedback; I'm pressing the submit button and nothing is happening...
If you are getting multiples of this message, that is why.

[WireWorker]

Well, this is a tough one! I've gotten this error before with a different file. In my case, the error occured when the Application Builder was supplied with two paths to the same external library, as opposed to a VI in your case. I had inadvertantly included a DLL as a support file in the Application Builder, but it was also loaded by one of the VIs in their application. For instance, if you build a Data Acquisition VI and you also include lvdaq.dll as a support file, you have actually provided the path to this DLL twice, once through the support files and once through the DAQ VIs. To resolve this, I removed the DLL or from the support files and it worked. Your case may be similar. See if there are multiple places you're including any external library or other dependency file.

Also, if you're using LabVIEW 6.0, here's a possibility. This Knowledgebase was written for TestStand but mentions a bug in the App Builder for LabVIEW 6.0 that caused an error message much like the one you're receiving. Let me know if any of this helps or if you're still getting the error.

[lgk]

Thanks for the response to my inquiry. After scratching my head over the error message and submitting my inquiry to the forum, I went back and began observing what was going on in the directories where the target executable and installer files were to be deposited, while the App Builder was executing. In this manner, I was able to determine that the problem was due to the previous versions of the installer files being marked read-only. I believe that that happened when I pulled an earlier version of the installer files out of the SourceSafe. Once I changed the file attributes to read-write, the process completed successfully.

Naturally, I forgot to go back and yank my inquiry (is that possible?)... my apologies.

[WireWorker]

Great job on the troubleshooting! That sounds like it was a tough one to track down. No worries on not pulling your question. I don't even think you can do that, anyway. At least someone else may see this thread and not have to search it down like you did!