Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Troubleshooting Problems with Your Custom Package

If your custom package does not work as expected on your user's machine, check the following scenarios:

Windows Update Setup fails on a user's machine

If Windows Update Setup fails, you can troubleshoot errors using the Active Setup Log.txt file. The Active Setup Log.txt file is a log of the entire setup process from the moment IE6Setup.exe is executed until the download of the last .cab file is complete.

When IE6Setup.exe is executed, Active Setup Log.txt is created in the folder where Windows is installed (typically, the C:\Windows folder). If an Active Setup Log.txt from a previous Internet Explorer Setup session exists, it is renamed to Active Setup Log.bak.

The log begins with the date and time Setup was launched and ends with the date and time it successfully downloads the last .cab file. As you go through the Setup wizard, logging entries are continually written to this file. It is the most informative log file for determining what caused a download failure and when the failure occurred. Most entries logged in this file are also written to the registry; this data is recorded to assist with safe recovery.

The error codes can help you determine what Setup was doing when it failed and also help you determine the cause of the failure. For information about the error codes, see Error Log Information for Active Setup Log.txt.

Files do not download during Windows Update Setup

Windows Update Setup has the ability to switch servers during an installation to maintain maximum throughput or recover from a distribution site that is not responding. Switching servers occurs when Windows Update Setup detects no throughput or less than one byte in two minutes.

If a connection times out, Setup will try to connect to the next download site in the list and continue the setup process at the beginning of the partially downloaded .cab file. If a connection times out and Setup does not switch servers, it will attempt to reconnect to the download site and continue the setup process at the point where it left off. If a connection to the download site cannot be established, Setup asks if you want to abort the installation or try again.

If the first site is down (for example, as a result of server problems), Windows Update Setup is unable to locate the remaining sites by default. A workaround involves overwriting the first site with the following command:

<path>\ie6setup.exe /C:"ie6wzd.exe /S:""<path>\ie6setup.exe"" /L:""http://my Web server/my Web site/ie6sites.dat"""

<path> is the folder where IE6setup.exe is located.

Example

The following is an example of the syntax to give to users when the first site is down. The example is a single command-line, displayed using three lines of text to improve readability.

C:\ie6setup.exe /C:"ie6wzd.exe
    /S:""D:\Build\1700\package\download\win95_nt\en\ie6setup.exe""
    /L:""http://<NewServerAddress>/<YourDownloadDir>/ie6sites.dat """

Installation modes not available to Windows 2000 or Windows XP users

Regardless of the installation options you configure for your package, Windows Update Setup presents only one installation option to users running the Windows 2000 or Windows XP operating systems. This installation option includes the full set of Microsoft Internet components, along with all custom components included in your package.

Branding changes made through auto-configuration are not applied on a machine running Windows 2000 or Windows XP

Branding changes distributed to people using auto-configuration are not applied if the No External Branding policy is set in Windows 2000 or Windows XP Group Policy. This policy prevents branding of Internet programs, such as customization of Internet Explorer and Outlook Express logos and title bars, by a third party such as an Internet service provider or Internet content provider. For more information, see Administering Microsoft Internet Explorer on Windows 2000 and Windows XP.

Cannot uninstall components

When the uninstall process fails, the most important tool for troubleshooting an uninstallation is the uninstall log, IE6 Uninstall Log.txt, which is located in the \Windows folder. This log covers the entire uninstallation process sequentially, including every file addition or removal; every registry addition, change, or removal; and any dialog boxes shown to the user.

The log is divided into Passes, which denote the different phases of an uninstall. Entries in the log also have an Object number that corresponds to the line entry in Setup.stf. Lines without an Object number result from custom actions specific to Internet Explorer and are contained in the IE6.inf file or in an .inf file from an external component uninstallation.

If you cannot use Add or Remove Programs in Control Panel to uninstall Internet Explorer, uninstall information might not be on the computer. The following are the key uninstall files:

  • IE6bak.dat

  • IE6bak.ini

  • Integrated Browser.dat

  • Integrated Browser.ini

The Internet Explorer Advanced Uninstall dialog box offers the option of uninstalling this backup information, but doing so prevents you from uninstalling Internet Explorer in the future.

For information about uninstalling custom components, see Providing Uninstall Functionality in an .inf Script and Uninstalling a Custom Component.

ICW Internet Sign-up does not work with single-disk branding

If you are using single-disk branding, do not use Internet Connection Wizard mode sign-up if you anticipate that some of your users are using Internet Explorer 4.01 Service Pack 1 (or earlier versions); instead, create a separate package using Kiosk-mode sign-up for these customers.


Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.