09.12.2012 Views

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

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 />

-7234 <strong>InstallShield</strong> could not create the<br />

software identification tag because<br />

the template file Swidtag.xml<br />

could not be opened.<br />

-7222 No supported languages included in<br />

the media. You must select at least<br />

one supported language for the<br />

media.<br />

-7211 Building a compressed Network<br />

Image Setup.exe. All other build<br />

types are not allowed in the<br />

evaluation mode of <strong>InstallShield</strong>.<br />

-7209 The current Windows Installer<br />

package name includes Unicode<br />

characters that may cause a runtime<br />

error if a compressed Network<br />

Image Setup.exe is built.<br />

Chapter 25: Errors and Warnings<br />

Build Errors and Warnings<br />

<strong>InstallShield</strong> uses the Swidtag.xml file, which is installed to one of<br />

the following locations, to build tag files:<br />

<strong>InstallShield</strong> Program Files folder\Support\0409<br />

<strong>InstallShield</strong> Program Files folder\Support\0411<br />

To resolve this issue, ensure that the Swidtag.xml file is present<br />

and not locked.<br />

For more information, see Including a Software Identification Tag<br />

for Your Product.<br />

This error occurs only when no supported language exists in the<br />

media.<br />

If you are using <strong>InstallShield</strong> in evaluation mode (that is, you have<br />

not activated it), you can build compressed Setup.exe files, but no<br />

other release types. If you are creating a Windows Installer–based<br />

release, the .msi database is always embedded in the Setup.exe<br />

file.<br />

If you try to build an uncompressed release in evaluation mode, the<br />

uncompressed option is ignored, and <strong>InstallShield</strong> displays this<br />

build warning.<br />

Once you have activated <strong>InstallShield</strong>, the evaluation-mode<br />

limitations are removed.<br />

This build warning occurs if the following conditions are true:<br />

• For the name of the .msi package, you include Unicode<br />

characters that are not supported by your build machine’s<br />

ANSI code page.<br />

• You include a setup launcher (Setup.exe file) with your<br />

release.<br />

This warning occurs to inform you that when the Windows Installer<br />

package is extracted from Setup.exe to a temporary location on<br />

the target system, run-time error 1152 may occur.<br />

To resolve this warning, change the name of the .msi package so<br />

that it does not contain Unicode characters that are not supported<br />

by your machine’s ANSI code page. To do so, you can use the MSI<br />

Package File Name setting, which is available when you click the<br />

<strong>Express</strong> node in the Releases view.<br />

<strong>InstallShield</strong> <strong>2012</strong> <strong>Spring</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1900-UG00 611

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

Saved successfully!

Ooh no, something went wrong!