{871E20E9-938D-4AAE-9CB3-A1C579E94F77} not found by installer after build.

[FTI_Newton]

Any reply or confirmation from National Instruments?

One of the previous Application Engineers posting should verify the behaviour. C'mon guys, someone has to need the points for submitting the CAR.

[Jennifer_R]

I have tested installers under a variety of conditions and haven't been able to reproduce the error.  The files created on my computer are not set to read-only, and even if I change them to read-only I do not receive an installer error.  I tried changing the product version, as well as leaving it the same.  In each case the installer built and ran successfully. 

If you have the option to investigate the error, that would provide additional information.  If there is a log file you can post or email, that would be helpful. 

[vituning]

Here's a solution:

My build directory is controlled as a Microsoft SourceSafe project, and is therefore subject to the usual write/read file restrictions that have been mentioned in this thread.

When I build my application and installer into this Build directory when it is NOT checked out, running the installer would result in this error:

.\Distribution.cpp(237): IInstallerError 10002
Fatal Error. Object not found.

From within SourceSafe, I checked out the Build directory, and overwrote all the files that had been edited by building the exe and installer while the project was not checked out.

I re-built the exe and installer into the original Build directory (now checked out) and ran the installer. Now I don't get the error.

Hope this helps. I can't say whether this is limited to MSVSS or may show up with other source code control providers. I don't remember there being any mention of SCC in this thread, but that was definitely the problem in my case: I didn't check out the project.

[GGivan]

I've got the same issue with LV 8.6.1.  

.\Distribution.cpp(283): IInstallerError 10002

Fatal Error. Object not found.

class CPart object lookup by ProductCode failed to find object {644DAD90-2083-4871-BD49-721BF8FAE295}

The .exe and the installer were created new into new folders and were not read only.  I compiled a different program the same way last week with no problems.  The one I am having problems with won't even install on the machine it was developed on!!! 

[Will_S.]

This is potentially caused by an error in the run-time installer. Could you please try a build that does not include the LabVIEW Run-Time engine? Then install the run-time engine separately by downloading from ni.com/support, followed by the new installer.

[GGivan]

This problem is with the runtime installer files and not with the installer itself.  For some reason my Labview 8.6.1 install and compiler will only work with the files listed below.  I found them in a previous build and copied them to the location listed above the file listing.  They are the exact same file names but have differing times/dates than the files that were in there.  The files that were in there came from an install of the runtime only as at one point in this effort I installed it separately from the Labview install.  My guess is that there is a problem with the compiler in that it will only work with the files that were installed by the full Labview install and not with just any lvrt install of that version or the stand alone lvrt install is different from the one packaged with Labview when both are of the same version. 

[Will_S.]

If that is the case, does repairing LabVIEW in Add/Remove programs correct the issue?

[GGivan]

I don't know, never tried it.  I copied the files from a previous install and replaced the ones that were being used.

[Bebeto]

Hello All,

I have exactly the same problem,

.\Distribution.cpp(336): IInstallerError 10002
Fatal Error. Object not found.
class CPart object lookup by ProductCode failed to find object {644DAD90-2083-4871-BD49-721BF8FAE295}

can somebody please help me out! thanks

[Will_S.]

Hi Bebeto,

Since this is such an old forum, please create a new thread that details your error as well as your completed troubleshooting steps. Have you tried repairing LabVIEW?