Verify upgrade (Windows SharePoint Services)
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2010-03-26
In this article:
After you have upgraded to Windows SharePoint Services 3.0 and installed the available software update, you should verify that the installation was successful by reviewing the upgrade log file (Upgrade.log), as described in the following procedure.To view the upgrade log file
In Windows Explorer, change to the following directory:
%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS
Use a text editor to open the Upgrade.log file.
Scroll to the date on which you installed the software update.
Search, or visually scan, for the following entries:
Finished upgrading SPFarm Name=<Name of Configuration Database>
In-place upgrade session finishes. Root object = SPFarm=<Name of Configuration Database>, recursive = True. 0 errors and 0 warnings encountered.
If you find these entries, the installation was successful.
If you do not find the entries from the previous step, you can identify specific issues that may have contributed to the failure by searching, or visually scanning, through the Upgrade.log file for the following terms:
After you identify and resolve the blocking issues, you can force a software upgrade to complete the configuration from the command line.
After you have verified that the upgrade was successful by reviewing the upgrade log file, review the upgraded sites and notify site owners that their sites are ready for review. For more information about reviewing upgraded sites, see Review upgraded sites (Windows SharePoint Services).
|In some configurations, the SharePoint Timer Service (OWStimer) account—which, by default, is the same account used by the SharePoint Central Administration v3 application pool account—is configured with credentials that do not have permission to access the LOGS folder in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case, part of the Upgrade.log is stored in the temporary storage folder of the account that is running the SharePoint Timer service. To avoid the possibility of deleting the upgrade log file when you restart the server computer, copy Upgrade.log to another location.|
To write all available logging information, including verbose output and detailed debugging information, to the log files for the software update installation, run the following command:
msiexec /p <PatchPackage> /l*vx %temp%\patch.log
Where PatchPackage is the path to the software update log file.
You can find the log file in the temporary file location with the file name msi*.log.
|By default, every time you run an upgrade, the information about that upgrade is added to the same upgrade log file. If you are running upgrade multiple times, rename the log file after each upgrade, so that you can review only the information about the current upgrade.|
If the installation was unsuccessful, you can run the SharePoint Products and Technologies Configuration Wizard again, or you can use the following procedure to complete the configuration from the command line.
|You can enable Windows Installer logging before you start the software upgrade installation again. To enable logging for Windows Installer, see Microsoft Knowledge Base article 99206: How to enable Windows Installer logging (http://go.microsoft.com/fwlink/?LinkID=99206).|
Open a Command Prompt window and change to the following directory:
%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin\
Type the following command:
psconfig –cmd upgrade –inplace v2v –wait –force
In addition to viewing the upgrade log, you can verify that the update was successful by using the SharePoint Central Administration Web site to view the version number on the Servers in Farm page. For more information about verifying that each server in the farm has been updated to the new binary version, see Deploy software updates for Windows SharePoint Services 3.0.