Error -6109

[#1]

Summary

Error -6109: Internal build error or ISDEV : fatal error -6109: Internal build error

Symptoms

When building a Basic MSI project, one the following errors occur:

• Error -6109: Internal build error
• ISDEV : fatal error -6109: Internal build error

Cause

This is a generic internal build error. Below are some known causes and potential solutions.

Resolution

Files Specified as Project Outputs are Not in the Correct Location

When you add files to a Visual Studio .NET project, you add pointers called project outputs. The outputs of the project are the files required at run time to run the project. You must build these files in Visual Studio .NET before building the installation project.

If the files specified as the project outputs are not where you specified they should be or if at one point the project outputs pointed to files but now they no longer do, then this error can occur. Make sure that the project outputs of your Visual Studio .NET project point to the files needed to run your project.

Project Files Are Not On The System

Verify that all files listed in the project are present in the file system. These files may appear with little yellow warning icons in ASP.NET projects.

Files Checked Into Source Control Reference Files That Don't Exist

If the .NET project is under source control, a .NET project file could be checked in that references a number of files that don't actually exist in source safe. In this case simply delete the bogus file references from the project.

Product Being Built Is Also Installed On The Same Machine

There have been reports that this error has occurred if the product being built has also been installed on the same machine. If this is the case, uninstall the product or rebuild the release on a clean machine.

Corrupted .NET

There have been reports that this problem has been resolved by reinstalling .NET from scratch and also possibly a reinstall of Installshield.

Comma In File Name

If one of the files has a comma in the file name, this error can occur. In this case, either remove the comma from the file name or exclude the file from the build.

Shared Dependency

There have been reports that in some cases this error can occur if two files (ie. DLLs) have the same dependency. Remove the dependency from one of the files in the InstallShield project.

Workaround

Changing project settings such as setting .NET Scan at Build to none or specifying that files in the project should not be built, can help you work around the issue without having to make huge changes in your InstallShield project.

Additional Information

Build Error 7354
Build Errors and Warnings