Users can install features on demand or run Setup in maintenance mode to add new features. Windows Installer uses this local installation source to install Office, and the local source remains available for repairing, reinstalling, or updating Office later. If sufficient hard disk space exists on the local computer, Setup caches the whole installation source by default. Start the Instmsi(w).exe file to install the Windows Installer.Ĭheck for installed beta versions of Office.Ĭheck the version of the Tahoma and TahomaBD fonts.īy default, Setup creates a local installation source in Office, but only when you install Office from the CD or a compressed CD image. Verify that the correct operating system and service pack are being used. The Setup.exe log file contains the command line that you specified for the installation, so you must check the log file for typographical errors, such as the one shown in the previous example (the letter s is missing from the end of Transform in the first command line). The correct command line is Transforms=\.mst. Using this on the command line doesn't produce an error message during the installation, but the transform won't be applied to the installation. A common mistake is to include Transform=\.mst on a command line. Parse the command line for properties and switches that have to be passed to the Windows Installer. The log file for the Setup.exe file is very short because the number of tasks that Setup.exe performs is limited to tasks like the following: How to interpret log filesĭepending on the problem that you are experiencing, you may have to view the Setup log file or the Windows Installer log file for the Office installation. In this situation, the Windows Installer log file for the Office installation has Task(0001) appended to the log file instead of Task(0002). You may have only a Microsoft Windows Installer log file for the Office installation. Therefore, the log file that has the highest number is the log file for the most recent time that you ran Setup. They increment by one each time that you run Setup. The # characters in the log file names are numbers that start with 0001. For more information, see How to enable Microsoft 365 Apps for enterprise ULS logging. For installation or patching issues, they use the system account, so you will also want to collect the logs from %windir%\temp. The logs will be stored under %temp% for Sign-in or Activation issues. Office Setup automatically creates log files in your \Temp folder. Many articles in the Microsoft Knowledge Base that relate to installation errors also include sections of log files that help you confirm that the article describes the same issue that you are experiencing. This article does not cover every situation that you may experience, but it discusses several examples where the Setup issue is resolved by interpreting a Setup log file. The topics are listed in the order that you want to use each technique. This article discusses several techniques to interpret the information in Office installation log files. Even if you receive an error message, you may have to use an installation log file as one of your tools to determine the issue. Occasionally a problem occurs with Office Setup and you may not receive an error message. This step-by-step article describes how to use the Microsoft Office installation log files to troubleshoot Office Setup issues.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |