09.12.2012 Views

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 25-2: Build Errors and Warnings (cont.)<br />

Error Description Troubleshooting Tips<br />

-7027 The build engine is unable to load<br />

the settings for the ‘Internet’ release<br />

type.<br />

Chapter 25: Errors and Warnings<br />

Build Errors and Warnings<br />

Check the <strong>Knowledge</strong> <strong>Base</strong> for information about this error, or<br />

request technical support.<br />

-7026 Internal build error. Check the <strong>Knowledge</strong> <strong>Base</strong> for information about this error, or<br />

request technical support.<br />

-7025 The COM+ component server file<br />

'%1' cannot be found on your<br />

system. The component '%2' will<br />

not be installed on the target<br />

system. You will need to install the<br />

component manually after your<br />

COM+ application is installed.<br />

-7024 To include J# in the build you must<br />

also include .NET 1.1.<br />

%1 refers to the COM+ DLL that is missing, and %2 refers to the<br />

ProgID. To resolve this warning, add the DLL to your system in the<br />

appropriate location, or remove the COM+ component from your<br />

project.<br />

J# requires the .NET Framework Redistributable Package version<br />

1.1, but it is not included in the installation. If you are sure that your<br />

end users already have the .NET Framework 1.1 on their systems,<br />

you can ignore this warning message. However, if there is a chance<br />

that they will not have the .NET Framework 1.1, add it to your<br />

installation. If the .NET Framework is not on their systems, they<br />

might have trouble installing J# as part of your installation.<br />

-7023 Internal build error. This error occurs if a merge module such as MFC 7.1 is not<br />

configured correctly or it is corrupted. If you have more than one<br />

merge module in your project but you do not know which one is<br />

causing the error, you need to first identify the problematic merge<br />

module. You can do this by removing a merge module from your<br />

project and then building your release. If the error recurs, you have<br />

identified the problematic merge module. If not, remove a different<br />

merge module and then build. Once you have identified the merge<br />

module causing the error, try reinstalling it. If that does not resolve<br />

the error, contact the author to obtain the latest version.<br />

-7016 The CabFiles key in the ini file that<br />

supports the "%1" Windows Mobile<br />

installation is too long. Shorten the<br />

Application Name, Company Name,<br />

or reduce the number of platforms/<br />

processors targeted.<br />

To resolve this error, open the Mobile Devices view and select the<br />

installation mentioned in the error message. If possible, shorten the<br />

company name or the application name, or reduce the number of<br />

platforms and/or processors that your installation supports. As an<br />

alternative, set up your installation so that it supports all platforms<br />

and/or processors.<br />

-7012 Internal build error. Check the <strong>Knowledge</strong> <strong>Base</strong> for information about this error, or<br />

request technical support.<br />

<strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1800-UG01 617

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!