After that it will not be advisable for the “average” user to run Office 2010 on a computerĬhange in computer programs tends to be “evolutionary” rather than “revolutionary”. OctoMS will stop providing security updates for it. Sorry to say, but Office 2010 is reaching it’s “end of life”. MSI, “Normal”, installations the log files will look like MSI****.LOG Provide the complete error log present in the ‘Temp’ folder to help you better.įollow the steps below to access the ‘Temp’ folder.įollowing are the log files that may be present in the %windir%\temp folder (c2r is for Click to Run):Bootstrapper*.log
MICROSOFT OFFICE AND STUDENT 2010 INSTALL
Now try to install Microsoft Office 2013 to get the error message so that the log files get created. Type reg add HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide /v LogLevel /t REG_DWORD /d 3 Note: make sure to turn off verbose logging after you are done.Įnable verbose logging before collecting the log files.ģ.
MICROSOFT OFFICE AND STUDENT 2010 WINDOWS
Windows installer returns codes during the install which will indicate if a particular function was successful or not. When looking through the MSI logs we will typically want to look for a value 3 entry in the logs. Every time anything is installed, ie Windows Updates, logs are created. Each time you use the Add/Remove Programs tool in Control Panel, a new Msi*.log file is created. In Control Panel, a new Msi*.log file is created. Each time you use the Add/Remove Programs tool Note This should be used only for trouble shooting purposes and should not be left on because it will have adverse effects on system performance and disk space. To include the v and the x option, specify “/l*vx”. ”*” - Wildcard, log all information except for the v and the x option. The “x” flag is available only on Windows Server 2003 and later operating systems, and on the MSI redistributable version 3.0, and on later versions of the MSI redistributable. M - Out-of-memory or fatal exit information Each letter’s actual function is as follows for MSI version 1.1: Each letter turns on a different logging mode. The letters in the value field can be in any order. HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer In the Open box, type the following command-line, and then click OK:
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). It will continue to generate “excess” logging files during all installations, including Windows updates.Īt times, Office Setup stops responding (hangs), and you do not receive any error message. PS: remember to turn Verbose Logging OFF after you fix the problem. So posting extract may catch the problem, but often miss the important info, so it is best to give us The thing is, the “useful” part will be very small and very specific and you probably won’t recognize it. If you don’t recognize an error, upload the entire log file set to Onedrive. Installationĭo a google search for “error status: 1603” Product Name: Microsoft Office Single Image 2010. MSI (s) (48:2C) : Windows Installer installed the product. MSI (s) (48:2C) : Product: Microsoft Office Single Image 2010 - Installation operation failed. All of the log files after that point willīe reporting the uninstall of previously installed components in reverse order. It is most likely to be the one reporting the error that caused the install to end and back out. Starting from top of list are logs for successful install of components.įind the log file in the very middle of the list of log files. There should be an odd number of log files. The pattern is that there is a separate log file for each component. I found a pattern in one verbose log file set that I have not yet had a chance to confirm in others, but you can give it a try. You can post the generated Logs in Onedrive and give a link to them to your technician if you need technical help. It will capture “success”, “informational”, “warning” as well as “error” messages that provide us with clues to your problem. “Verbose logging” is a setting that exposes more information during the installation process. Shooting-office-365-proplus-installations.aspx shooting-office-installation-failures/ - help interpretting logs – Trouble shooting Office install failures shooting-office-installation-failures.aspx Office 2003-2010, analyse log fix Its to turn verbose logging on and off Fix it for Win XP-Win 8
reg hack to enable/disable Verbose Logging It can generate a LOT of log files that will clog Verbose Logging applies to Windows updates and all other install processes. NOTE: Remember to turn it off after you fix the problem. It is a Windows install mode that captures normally hidden outputs to help with install/update trouble shooting. Verbose Logging – install trouble shooting
0 kommentar(er)
