LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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

I found out the issue and how to avoid it (to actually fix it - or even report it during build is something you guys have to do.). I'm surprised it hasnt' come up more than once actually.
When the installer build writes the files in the folder you've designated, it doesn't check th
0 Kudos
Message 11 of 35
(2,416 Views)
ADAC,

I'm glad you were able to get things working!  Unfortunately, it looks like your posts were cut off.  Any further information you have would be very much appreciated!
0 Kudos
Message 12 of 35
(2,410 Views)
Has there been any other progress on this issue?  I am seeing the same issue.

.\Distribution.cpp(242): IInstallerError 10002
Fatal Error. Object not found.
class CPart object lookup by ProductCode failed to find object {D508C13F-FD07-4F97-AA43-DBAA93698C7F}


I just upgraded to LV 8.5.1.  I haven't seen this problem with any other apps that I have build.  This app is included the VISA Support and 8.5.1 Run Time. 

The installer and build create fine.  I am also able to run the exe file as a standalone and it is fine.


BJD1613

Lead Test Tools Development Engineer

Philips Respironics

Certified LV Architect / Instructor
0 Kudos
Message 13 of 35
(2,332 Views)
Maybe this will help.

I originally build this app in LV 8.5.  Installed this on a machine and named it version 1.0.0 in the installer window.

I then installed LV 8.5.1 and rebuild the app and named it 1.1.0 in the installer. 

This is where I had problems.  I tried to uninstall the old app.  Nothing worked.

I changed the version number of the installed back to 1.0.0. Now is works... I am not sure why though.

Any thoughts?
BJD1613

Lead Test Tools Development Engineer

Philips Respironics

Certified LV Architect / Instructor
0 Kudos
Message 14 of 35
(2,329 Views)

Newton, Can you explan your remedy again.It has cut off in the middle.

0 Kudos
Message 15 of 35
(2,285 Views)
Hi Arvindti.
 
Are you receiving the same error when running your installer?  What are the properties of your installer, particularly any additional installers that are included?  If you delete the installer build specification and create a new installer, with a different location selected, does that result in the same error? 


Message Edited by Jennifer_R on 05-21-2008 09:34 AM
Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 16 of 35
(2,262 Views)
Thanks Jennifer,
 I could install it now after creating a new installer at a different destination. Is that the solution for this isuue?
Actually my installer had LabVIEW Runtime engine included with that.
0 Kudos
Message 17 of 35
(2,250 Views)
Hi Arvindti,
 
That's great!  With similar errors I have seen, the solution has been to select a different destination or else delete and recreate the existing installer directory. 
Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 18 of 35
(2,239 Views)
The destination changes didn't solve my problem.  Has there been any other testing done on this problem?  I understand that it is random and hard to create.   I changed the version number.  I would look into the Product Information screen in the installer.  This seems to be where the problem/fix could occur.  We both said that removing or adding additional installer didn't change the result.

hope this helps
BJD1613

Lead Test Tools Development Engineer

Philips Respironics

Certified LV Architect / Instructor
0 Kudos
Message 19 of 35
(2,236 Views)

Been awhile since I've dealt with this, so I'm going by memory - I deny responsibility for any inaccuracies in the following post. Smiley Tongue

 

The installer files are read only after creation maybe?. In any case, the installer creator doesn't check to see if the old files are read only. It cannot overwrite them, and keeps on proceeding with the operation without a warning or error. The answer is to delete the old installer or change it from Read Only. If you install to a different location, it works because the old files aren't there!

NI needs to have the installer detect if it cannot overwrite the file, then either bomb out or prompt the user for permission to overwrite the file.

I'm amazed NI hasn't encountered this in testing.

Actually, I'm not. Smiley Mad

 

 



Message Edited by FTI Newton on 05-22-2008 12:10 PM
Message 20 of 35
(2,229 Views)