Server 2003 program install log

United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. However, the logging options that are used for these verbose log files aren't all the options that are available to the Windows Installer. You can create a verbose log file when you perform an administrative installation of Office by using a command line that's similar to the following:. At times, Office Setup stops responding hangs , and you don't receive any error message.

The best thing to do in this situation is to restart your computer, and run Office Setup again with complete verbose logging turned on with one additional option. To do so, follow these steps:. In the Open box, type the following command line, and then click OK :. Typically, 19 lines of logging information are cached in memory before being written to the verbose log file.

If you don't use the! If you use the! After you create the verbose log file, scroll to the end and look at the last one or two lines. These lines tell you what Setup was trying to do when it stopped. For example, you may see text that's similar to the following example:.

The resolution for this particular issue is to repair the Windows registry before you run Office Setup again. This indicates a problem with an Office Removal Wizard operation. This problem may occur when Office Setup is having a problem removing your earlier version of Microsoft Office. Try to remove the earlier version of Office, and then run Office Setup again.

Office Setup uses the following prefixes for custom actions. If the log file indicates a problem with a custom action, these prefixes indicate where to start your troubleshooting. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? The MSI log files provide details of the installation package process. At the end of the file is a summary of the execution, which includes the success or failure status and properties. To find the error in the MSI file, search for "value 3" and review the text before and after. The configuration file contains the input settings that are provided during installation.

It can be used to restart the installation without having to enter the settings manually. However, passwords for the accounts, PID, and some parameters are not saved in the configuration file. The settings can be either added to the file or provided by using the command line or the Setup user interface. The ConfigurationFile. The system configuration check report contains a short description for each executed rule, and the execution status.

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This article describes where to locate these log files and which log files are most useful for troubleshooting each setup phase of Windows 7, of Windows Server R2, and of Windows Vista.

Windows setup log files are in different locations on the hard disk. These locations depend on the setup phase. Support for Windows Vista without any service packs installed ended on April 13, For more information, see Windows XP support has ended.

The downlevel phase is the Windows setup phase that is running within the previous operating system.