- Microsoft office 2000 error how to#
- Microsoft office 2000 error update#
- Microsoft office 2000 error Patch#
- Microsoft office 2000 error professional#
Microsoft office 2000 error Patch#
Office\Office10\OUTLLIB.DLL' is redirected to patch 'C:\Config.Msi\PT16A.tmp' instead. MSI (s) (B3:D6): Patch for file 'C:\Program Files\Microsoft (The following text is taken from a verbose log file that was created when installing a Microsoft Outlook 2000 Update.) For example, if you receive an error 1328, you may see the following text in a verbose log file.
Microsoft office 2000 error update#
If you receive a Windows Installer error message during the update process, the error message probably includes an error number. The error number - for example Error 1328.These techniques include searching for the following:
Microsoft office 2000 error how to#
The following line is one of the most important parts of the Ohotfixe.exe log file:Ģ96603 How to use an Office XP setup log file to troubleshoot setup problems in Office XP Logging Success in the Ohotfix.exe Log File
Microsoft office 2000 error professional#
Professional with FrontPage Version 4.: Needs patch. Seeing if patch C:\Program Files\OfficeUpdate\MSPs\winword.msp is needed. The following text from an Ohotfix.exe log file reveals that the single update package must be installed for the Microsoft Word 2000 update: When you apply an Office 2000 update, Ohotfix.exe inspects your installed products and decides which of the update packages must be installed (when the update contains multiple update packages). The Ohotfix.exe log file can also indicate the Windows Installer update packages (.msp) contained in the update that must be applied. MessageTitle="Microsoft Office Hotfix Installer"Ģ55275 How to determine the version of your Office 2000 program By default, the log file contains a MessageTitle line similar to one of the following near the top of the log: To definitively identify the Office 2000 log files, open the Ohotfix.exe log file, OHotfix( #).log, and then view the ninth line in the log file. The highest numbered pair belongs to the latest update installation. Because the update log file names are similar, the best way to identify the most recent update log files is by the number ( #) in the log file names. If you installed more than one update, it is not obvious which log files belong to the most recent installation. Therefore, you can easily match them as part of the same installation. The pair of Setup and Windows Installer log files have the same number ( #) in their respective log file's name. The first log file is created by the Ohotfix.exe bootstrap Setup file, and the second log file is created by the Windows Installer (Msiexec.exe). Therefore, if you run the same update again or you run a new update, the next pair of log files will be numbered 00002.įor each update installed, two log files are created. Note: These numbers start at 00001 and are incremented for each additional update. The log files have names similar to the following: This article does not cover every situation that you may experience, but it discusses several examples in which the update issue is resolved by interpreting a log file.Īll client updates for Office 2000 create log files in the Temp\OHotfix folder. The methods are listed in the recommended order of use. This article discusses methods for interpreting the information in the Office 2000 update files. In either case, the use of a log file can help you determine the exact error and the best method to troubleshoot the issue. If a problem occurs with the installation of an update for Office 2000, you may or may not receive a descriptive error message. This step-by-step article describes how to use the log files that are created when you try to update Office 2000 to determine the cause of an failed Office update.
0 kommentar(er)
