Summary

Information on build errors.

Symptoms

Error 1024 is encountered only at build time. The InstallShield build process displays either of the following message:

• **Error: -1024: File <FILENAME> not found. Cannot stream the file into the Binary table.
• **Error: -1024: The source file <FILENAME> for Icon <ICONNAME> does not exist.
• <FILENAME> is the name of the file not found.
• <ICONNAME> is the name of the icon file from the Icon table.

Cause

This error occurs when there is an invalid IsBuildSourcePath listing in the Binary table or Icon table.

Possible Causes:

1. A custom action of type StoredInBinary table is included in the project and the source field contains an invalid path.
2. A dialog included in the project has a bitmap control, and the File Name property contains an invalid path.
3. The icon field of a shortcut in the project contains an invalid path.
4. An entry has been abandoned in the binary table that is no longer being used.
5. A release location other than <ISPROJECTDATAFOLDER> is specified, and a function in a standard DLL is being called.
6. The Display Icon field for Add or Remove Programs entry in the project contains an invalid path

Resolution

Solution for Cause 1:

1. Select the Custom Actions view.
2. If you recognize the name of the file referenced in the build error, find the custom action that references that file. Otherwise, you need to check each custom action. Click the appropriate custom action to display the custom action's property grid. One of the fields will be the file name field. Depending on the type of custom action this field may say Executable FileKey, DLL FileName, VBScript FileName, or another file name.
3. Verify that each path in the File Name field is valid. If the path is not valid, modify the path appropriately.

NOTE: As an alternative, right-click the custom action and select Custom Action Wizard. As you step through the wizard, check the Source field on the Action Parameters panel and verify that file path is valid.

Solution to Cause 2:

1. Open the Direct Editor view.
2. Select the Binary table in the Direct Editor view.
3. Search for the FILENAME in the Binary table.
4. Take note of the Binary 'Name' column field for the row that contains the missing file.
5. Search for the Binary name from the above step in the Control table.
6. Take note of the 'Dialog' column for the rows that contain the binary name.
7. Using the dialogs view, select the bitmap controls for the dialogs specified in step 6.
8. For each bitmap control, verify that the path displayed in the File Name field is a valid path. If the path is not valid, modify the path appropriately

Solution for Cause 3:

1. Open the Shortcuts view.
2. Set the View Filter at the top of the Shortcuts view to All Application Data.
3. Click each shortcut listed in the Shortcuts view and find the Icon File field on the right side.
4. Verify that the path displayed in the Icon File field is a valid path. If the path is not valid, modify the path appropriately.

Solution for Cause 4:

1. Open the Direct Editor view.
2. Select the Binary table in the Direct Editor view.
3. Review the Binary table for any entries that are no longer needed.
4. Delete entries by right-clicking them and selecting Delete from the context menu.

Solution for Cause 5:

1. Verify that <ISPROJECTDATAFOLDER> exists. If not, use Windows Explorer to create this folder. This should be a folder with the same name as that of the project's .ism file and be located in the same folder that the .ism file is in.
2. In the Path Variables section under Advanced Views, the Current Value of the ISProjectDataFolder name should be set to this value.
3. Rebuild the project.

Solution to Cause 6:

1. Select the General Information view.
2. Select Add or Remove Programs.
3. In the Display Icon property, verify that the path in the Display Icon field is valid. If the path is not valid, modify the path appropriately.

Additional Information

Path variables may be referenced in the file paths. If this is the case, check the Path Variables view and verify that the appropriate Path Variable has been assigned a valid path.

As an additional solution to the above causes, the IsBuildSourcePath can be directly modified via the Direct Editor in the Binary or Icon table.

The Binary table is documented in the Windows Installer Help Library topic Binary Table.