Software Deployment Question

Help with MSI 2715

04/11/2004 32746 views
Help with MSI (Microsoft Installer) error 2715: The specified File key ('[2]') not found in the File Table.
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

This error has been reported when the MSI has a custom action in the incorrect place in the
sequences section. If you are authoring an MSI and working with custom actions, try inserting it between the "Install Initialize" and "Install Finalize" entries in the "Execute Sequence".
This was also a problem reported that was fixed in PhotoDraw 2000, Version 2 SR-1 ( where it was encountered during install-on-demand operations.
Answered 04/11/2004 by: AppDeploy.com
Red Belt

This error was caused by having an empty component. The file key *never* existed in the file table. The component was ODBC entries that I removed to replace with registry entries. I forgot to make sure that WPS4.62 didn't leave empty components after I delete the ODBC stuff in Installation Expert. (Misterd, 4 may 2006)
Answered 05/04/2006 by: misterd
Second Degree Blue Belt

I got this error due to custom action "Call Dll from Installation function UpgradeCheckEx" which is in UserInterface i deleted that that's why i was getting error it. it used For an upgrade, detect installed products affected by the pending upgrade.
Answered 06/16/2006 by: organicjoy
Yellow Belt

Sometimes the simplest things can be the solution:I had a Microsoft MSI which I had to add a file to which I did through ORCA - WPS took ages and frequently crashed whilst saving.I got a 2515 error because of a "typo" in the Component table/Ketpath column. All I had to do was cross-check the relevant entry and change the Keypath to have the correct spelling.
Answered 10/02/2007 by: fritoz
Orange Belt

I received this error because the keypath was not uppercased whereas I had uppercased the filename in all other locations.MSI is case sensitive!!!
Answered 09/26/2011 by: whenriksen
Yellow Belt

I got this error because somehow the attribute in the component table was set to registry keypath (4) while the keypath pointed to a file table entry. Because I needed it to be a file keypath, I changed the attribute to file keypath (0) and it worked.
Answered 01/13/2012 by: koswo
Orange Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ