Guidelines on troubleshooting installation /patch installation and repair issues on SharePoint 2007 /WSS 3.0
SharePoint update or Service Pack has 2 step of installation
- Binary installation
- Running PSCONFIG
Some of the common issues while installing running an Repair or an updates
Ø Error 1706.An installation package for the product Microsoft Windows SharePoint Services 3.0 cannot be found. Try the installation again using a valid copy of the installation package 'sts.msi'.
Ø Microsoft Office SharePoint Server 2007 configuration did not complete successfully. An installation package for the product Microsoft Office Shared Coms English Language Pack cannot be found. Try the installation again using a valid copy of theinstallation package 'osrvmui.msi'.
Ø "The detection failed, this can be due to a corrupted installation database."
Ø An installation package for the product for MS Office SharePoint Server 2007 English language pack cannot be found,... retry the installation with a valid copy..
Ø Running the WSS /MOSS repair from the control panel nothing happens no error nor it would start repair
Ø "The update cannot be applied."
Ø Binary installation of MOSS SP2 on Server failed with error code 1603.
Troubleshooting some of the above issue
With the advent of the 2007 Office system multi-MSI installation model, the inefficient Windows Installer logging is secondary to the 2007 Office system Setup logging.
However, there are still occasions for which only Windows Installer logging provides the additional level of detail needed.
Because the size of the logs can be significant, you should only enable verbose Windows Installer logging when needed and immediately disable logging once the problem is resolved.
Although use of Windows Installer functions is limited in the 2007 Office system, Setup.exe ultimately relies on the Windows Installer to perform many processes. Because of this, some of the common things that go wrong with the Windows Installer itself might need to be rectified before determining if an actual 2007 Office system problem exists.
Before you enable Windows Installer logging, you should check the following:
o Verify the Windows Installer service is not disabled.
o Check for system policy restrictions.
o Clean up the temporary files.
o Verify DCOM permissions.
If we find any issues related to Binary installation we can enable the Verbose logging for the MSI installer by merging the below registry
How to enable Windows Installer logging
To enable Windows Installer logging, open the registry by using Regedit.exe and create the following path and keys:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmupx
Windows Installer logging should be used only for troubleshooting purposes and should not be left on because it will have adverse effects on system performance and disk space. Each time you use Add/Remove Programs in Control Panel, a new Msi*.log file is created.
For more information about how to enable Windows Installer logging, see Microsoft Knowledge Base article 223300: How to enable Windows Installer logging (https://go.microsoft.com/fwlink/?LinkId=128265).
What to be looked when reviewing MSI verbose log file?
After merging the verbose registry key to the machine.
Then run the installation again so that the error is logged in the log file ,which is stored at the below location %temp%
Open the latest log file by sorting by date modified
· Search the log file for the error number. If you received a 1603 error message,
· Search for the key “Value 3” which is an error code in MSI installations which will help determine why the failure occurred.
· Read each line up from the line that has the error number. Typically you see a line that failed, with the ultimate result being a Setup error.
· If you do not receive an error number, you can also search on the word “Error.”
· When no obvious error is generated or logged, search for the string “Note.” A “Note” is an error that is frequently expected (for example, when checking for the existence of a file that was deleted, it would be expected to receive a “File not found” error). Sometimes, however, it is an indication of a true error.
Although a Return Code of 0 normally indicates no problems, occasionally there is no error generated, and yet the installation process does not complete as expected.
For more information about the error codes used by 2007 Office system installations when you enable verbose logging, see Error codes for 2007 Office system installations.
Note: We can use a tool called The Windows Installer Verbose Log Analyzer which assists the analysis of log files from a Windows Installer installation, and it displays suggested solutions to errors that are found in a log file. (See the tools section for more details)
For more information, see Logging
For more information about the Windows Installer Verbose Log Analyzer (Wilogutl.exe), see Wilogutl.exe ,
Microsoft Windows SDK Blog - Windows SDK Hidden Gems: Part 1
To download the Windows Installer Verbose Log Analyzer (Wilogutl.exe),
see Microsoft Windows Software Development Kit Update for Windows Vista