How to troubleshoot Microsoft Update issues when you use the Product Update feature in SQL Server "Denali"

Article translations Article translations
Article ID: 2528485
Expand all | Collapse all

On This Page


This article applies to the following product:
  • Microsoft SQL Server "Denali"

Introduction

Although Microsoft does extensive testing, issues can sometimes occur that may prevent the SQL Server Product Update feature in Microsoft SQL Server "Denali" from functioning as expected or without error. This article presents some common troubleshooting steps to help you resolve issues that may occur in SQL Server Product Update. These steps can help you identify the exact error message or the exact step within the setup process at which the error occurred so that you can search for detailed information.

Note This article is not a complete troubleshooting document. Instead, it is intended as a starter guide for the average user.

MORE INFORMATION

The new Product Update feature in SQL Server "Denali"

SQL Server Product Update is a new feature that was created to help you make sure that you have the latest updates at the time of installation. For more information about an update that is available to add support for testing the Product Update feature, click the following article number to view the article in the Microsoft Knowledge Base:
2580208 An update is available to add support for testing the Product Update feature in SQL Server "Denali" CTP3
By the time that you installed an earlier version of SQL Server, updates may have been released that helped to resolve setup or product issues. These updates may have included security updates to help increase the stability and reliability of the SQL Server suite of products.

With the introduction of SQL Server 2008 Service Pack 1 (SP1), Microsoft implemented the slipstreaming capability. Slipstreaming lets you have the latest updates at the time of installation. However, slipstreaming required some significant manual intervention that most users could not easily perform.

The Product Update feature in SQL Server "Denali" provides an easy solution to these issues. Now you can integrate the latest product updates with the main product installation by starting the usual Setup application. Product Update automatically searches Microsoft Update, Windows Server Update Services (WSUS), or a local or remote network folder. When Product Update finds the latest versions of the applicable updates, it downloads them to the local system and integrates them with the current SQL Server setup. These updates can be a download, a cumulative update (CU), a service pack, or any combination of these updates.

Microsoft Update

The SQL Server Product Update feature can use Microsoft Update as one of the ways to download and to incorporate the latest SQL Server updates.

Microsoft Update is a service that provides all the features of Windows Update plus updates for other Microsoft applications such as SQL Server. The update service is the online extension of the Windows operating system. It is basically a catalog of updates and improvements to Windows and to many other applications such as SQL Server.

Initial troubleshooting

There are some actions that you can try that may resolve issues with Microsoft Update. This section lists some articles that can help you resolve issues with Microsoft Update and with Windows Update.
  • Try to reset the Windows Update client files and configuration. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
    971058 How do I reset Windows Update components?
  • If you have identified the error message, click the following article number to view the article in the Microsoft Knowledge Base for more information about some of the most common issues:
    906602 How to troubleshoot common Windows Update, Microsoft Update, and Windows Server Update Services installation issues
  • To troubleshoot an error message that you received, try the Windows Update Troubleshooter. To do this, visit the following Windows Update website:
    Windows Update Troubleshooter
  • To find descriptions of Microsoft Update error codes that may help you in your online search, visit the following Microsoft TechNet website:
    Windows Update Agent Result Codes
If you reset the Windows Update client files, and if the other resources that are listed here did not resolve the issue, you should try to disable the antivirus software that is installed on your computer.

Caution Antivirus software helps protect your computer from viruses. When your antivirus software is disabled, you should not download or open files from sources that you do not trust, visit websites that you do not trust, or open email attachments.

In some cases, antivirus software can cause issues with Microsoft Update. Some new antivirus applications include firewall functionality. You may have to create an exclusion in the antivirus software or even disable the antivirus software temporarily. After you disable the antivirus software, restart the computer before you try the installation again. Restarting the computer prevents files from being locked when the installation process has to access them. After the installation is complete, make sure that you re-enable your antivirus software. Visit your antivirus software vendor's website for the exact steps to follow to disable and then re-enable your antivirus software.

How to determine the error by using the SQL Server logs

When you troubleshoot the SQL Server Product Update feature, you must first find the exact error message. You will use this error message to search for known issues on support.microsoft.com or even to resolve the issue by using the following information.

To start, examine the following log files from the latest SQL Server installation attempt.

Note Every time that you try to run the SQL Server Setup program, log files are created in a folder whose name uses a time-stamp format. The time-stamp format is YYYYMMDD_hhmmss and reflects the time when the SQL Server Setup program was started. By default, these log files are in the following location:
%ProgramFiles%\Microsoft SQL Server\110\Setup Bootstrap\Log

Summary log file (Summary.txt)

The Summary.txt file is an overall summary report for all components and shows success or failure messages. In addition, this log file shows the input parameters that were used with the Setup program.

Note The Summary.txt file is overwritten every time Setup.exe is run. If you try to run the Setup program again after a failure, you have to investigate the log files for more information. You will have to open each folder to look for the individual Summary.txt files. After the files are added in their specific time-stamped folder, the files are named Summary_MachineName_YYYYMMDD_HHMMSS.txt. For example, a file could have the following name:
Summary_2008R2Node1_20110628_044645.txt
After you open the summary log file, look for specific items that indicate that the Product Update feature was used. This helps determine the approach you have to take for troubleshooting.

If the installation succeeded but you find that after the installation no updates were installed, see whether the UpdateEnabled value is set to True or to False.

The most important part of the summary log file is the value of the UpdateSource parameter. This value specifies the location where SQL Server Product Update will search for valid updates. The values that it can contain are as follows:
  • MU
  • Valid folder path or UNC path

Note MU is the default value when no value is specified during setup.

When you download SQL Server updates manually and then put them on a network share or on a local share, make sure that you specify a valid path such as \\ServerName\ShareName. Or, if you define a local path, make sure that the path is set correctly. For example, the path C:\MyUpdateFolder is a correctly set path. Additionally, the UpdateSource value can be in relation to where you run the Setup program. For example:
UpdateSource = ".\MyUpdates"
This statement makes the Setup program look for the MyUpdates folder in one directory under the current Setup program location. Make sure that the UpdateSource value is set correctly.

If an error message occurred during your setup attempt, the overall error message should be listed in this log file and will be an optimal place to start your troubleshooting. You can search on this error code and message to see whether there are any known issues or Microsoft Knowledge Base articles that may help you resolve the issue quickly. Based on the error code or message, look for common mistakes. For example, the UpdateSource parameter may not be pointing to a valid location for the update packages that you have downloaded. In addition, make sure that the user credentials that you used to start the SQL Server Setup program have at least Read permissions.

When you use a file location and have problems downloading or accessing the updates, you have to make sure that you check not only the File System permissions but also share permissions. In addition, you could run the Process Monitor utility. To download this utility, visit the following Microsoft TechNet website:
Process Monitor
This utility can help identify security issues or incorrect permissions to the account that is running SQL Server when that account tries to access the local or remote share.

When you use Microsoft Update, you can try to search for the error code, or you can refer to the links in the "References" section.

For detailed information about which updates were discovered during the scanning, or for problems that may have occurred, see the Component Update Detail log file.

Component Update Detail log file (Detail_ComponentUpdate.txt)

The Detail_ComponentUpdate.txt file provides details of the Setup program and other workflows. To find the folder that contains this file, refer back to the Summary.txt log file. If you do not find the file in the log file location, refer to the configuration file location. For example, the configuration file location will be listed in the log file as follows:
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20110728_044645\ConfigurationFile.ini
In this example, the directory that you have to locate is as follows:
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20110728_044645
When you have this log file opened, start your search by finding the following:
SearchUpdatesAction
For example, search for SearchUpdatesAction in the following sample log file:
(04) 2011-06-28 04:58:44 Slp: Running Action: SearchUpdatesAction
(04) 2011-06-28 04:58:44 Slp: Inspecting update packages in directory 'D:\Update Packages'
…..
(04) 2011-06-28 04:58:44 Slp: Sco: Attempting to check if directory D:\Update Packages exists
(04) 2011-06-28 04:58:44 Slp: Sco: Attempting to set directory full path
(04) 2011-06-28 04:58:44 Slp: Sco: Attempting to normalize directory path D:\Update Packages
(04) 2011-06-28 04:58:44 Slp: Sco: Attempting to get files for directory D:\Update Packages, search pattern *.exe
(04) 2011-06-28 04:58:44 Slp: Inspecting update package 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe'
(04) 2011-06-28 04:58:44 Slp: Sco: Attempting to set file full path to 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe'
(04) 2011-06-28 04:58:44 Slp: Sco: Attempting to normalize directory path 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe'
(04) 2011-06-28 04:58:44 Slp: Sco: Attempting to check if file 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe' exists
(04) 2011-06-28 04:58:44 Slp: Package 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe' is a valid update.
…..
(04) 2011-06-28 04:58:44 Slp: Package 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe' is a valid update.
…..
(04) 2011-06-28 04:58:44 Slp: Update: {Name: Hotfix Pack; KB Article: CU01_RTM1422.3; Version: 11.0.1500.0; Achitecture: x64; Language: All; Update Type: CU} is available but is temporarily not considered to be selected for installation, because its update type 'CU' does not match the update type 'PCU' that setup is currently looking for.
(04) 2011-06-28 04:58:44 Slp: Update: {Name: Hotfix Pack; KB Article: CU01_RTM1422.3; Version: 11.0.1500.0; Achitecture: x64; Language: All; Update Type: CU} is considered to be selected for installation.
(04) 2011-06-28 04:58:44 Slp: Update: {Name: Hotfix Pack; KB Article: CU01_RTM1422.3; Version: 11.0.1500.0; Achitecture: x64; Language: All; Update Type: CU} is available but is temporarily not considered to be selected for installation, because its update type 'CU' does not match the update type 'Setup' that setup is currently looking for.
(04) 2011-06-28 04:58:44 Slp: 
(04) 2011-06-28 04:58:44 Slp: Available Product Updates Discovered:
(04) 2011-06-28 04:58:44 Slp: Title: Hotfix Pack
(04) 2011-06-28 04:58:44 Slp: Knowledge Based Article: KB CU01_RTM1422.3
(04) 2011-06-28 04:58:44 Slp: Version: 11.0.1500.0
(04) 2011-06-28 04:58:44 Slp: Architecture: x64
(04) 2011-06-28 04:58:44 Slp: Language: All
(04) 2011-06-28 04:58:44 Slp: 
(04) 2011-06-28 04:58:44 Slp: 
(04) 2011-06-28 04:58:44 Slp: Product Updates Selected for Installation:
(04) 2011-06-28 04:58:44 Slp: Title: Hotfix Pack
(04) 2011-06-28 04:58:44 Slp: Knowledge Based Article: KB CU01_RTM1422.3
(04) 2011-06-28 04:58:44 Slp: Version: 11.0.1500.0
(04) 2011-06-28 04:58:44 Slp: Architecture: x64
(04) 2011-06-28 04:58:44 Slp: Language: All
(04) 2011-06-28 04:58:44 Slp: 
(04) 2011-06-28 04:58:44 Slp: Update Source: D:\Update Packages
….
(04) 2011-06-28 04:58:44 Slp: Completed Action: SearchUpdatesAction, returned True
As you can see in this example, the log file contains some very detailed information, such as the following:
  • Whether the directory could be accessed
  • Which updates were found
  • Whether the update was valid 

Additionally, the file may list errors that may have occurred during discovery.

If the issue is not with discovery, you may want to search the log file for the following:
PackageExtractAction
For example, search for PackageExtractAction in the following sample log file:
(01) 2011-06-28 04:59:17 Slp: Running Action: PackageExtractAction
(01) 2011-06-28 04:59:17 Slp: Sco: Attempting to set directory full path
(01) 2011-06-28 04:59:17 Slp: Sco: Attempting to normalize directory path D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe
(01) 2011-06-28 04:59:17 Slp: Sco: Attempting to check if directory D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe exists
(01) 2011-06-28 04:59:17 Slp: Sco: Attempting to set file full path to 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe'
(01) 2011-06-28 04:59:17 Slp: Sco: Attempting to normalize directory path 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe'
(01) 2011-06-28 04:59:17 Slp: Sco: Attempting to check if file 'D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe' exists
(01) 2011-06-28 04:59:17 Slp: Running: D:\Update Packages\SQLServer2011-KBCU01_RTM1422.3-x64.exe /x:"C:\Users\Administrator.CLUSTERTEST\AppData\Local\Temp\SQL Server Denali CTP3\Hotfix" /q
(01) 2011-06-28 05:00:32 Slp: Process returned 0
(01) 2011-06-28 05:00:32 Slp: Completed Action: PackageExtractAction, returned True

As you can see in this example, the package was local, because the hotfix package was extracted to the %Temp% location. If there was a problem with the actual package such as corrupted files, you would see an error message. In this example, the return was 0 or Success.

There are several other areas where you could look for an error. Although the areas that we describe here do not make up a complete list, they will get you started with your investigation. In these examples, it is best to look for the start (Running Action) and stop of that section (Completed Action). Then, analyze the data between the start and stop to determine why an error occurred.

Detail Setup log file (Detail.txt)

The Detail.txt file contains information about which updates are included in the installation. This file also contains details about the complete setup workflow.

To find the start of the Update Actions section, search for the following:
RunSmartSetupWorkflow
For example, the log file may resemble the following:
(01) 2011-06-28 05:03:35 Slp: ----------------------------------------------------------------------
(01) 2011-06-28 05:03:35 Slp: Running Action: RunSmartSetupWorkflow
(04) 2011-06-28 05:03:35 Slp: ----------------------------------------------------------------------

This is the start of the Product Update workflow. 

Then, search for the following entry:
SearchUpdatesAction
This shows you all the packages that were found or whether there was an error message. For example:
(04) 2011-06-28 05:03:35 Slp: Running Action: SearchUpdatesAction
(04) 2011-06-28 05:03:35 Slp: Discovered update on path C:\Users\Administrator.CLUSTERTEST\AppData\Local\Temp\SQL Server Denali CTP3\Hotfix; Update: Hotfix Pack, Type: CU, KB: CU01_RTM1422.3, Baseline: 11.0.1422, Version: 11.0.1500
(04) 2011-06-28 05:03:35 Slp: Update: {Name: Hotfix Pack; KB Article: CU01_RTM1422.3; Version: 11.0.1500.0; Achitecture: x64; Language: All; Update Type: CU} is available but is temporarily not considered to be selected for installation, because its update type 'CU' does not match the update type 'PCU' that setup is currently looking for.
(04) 2011-06-28 05:03:35 Slp: Update: {Name: Hotfix Pack; KB Article: CU01_RTM1422.3; Version: 11.0.1500.0; Achitecture: x64; Language: All; Update Type: CU} is considered to be selected for installation.
(04) 2011-06-28 05:03:35 Slp: Update: {Name: Hotfix Pack; KB Article: CU01_RTM1422.3; Version: 11.0.1500.0; Achitecture: x64; Language: All; Update Type: CU} is available but is temporarily not considered to be selected for installation, because its update type 'CU' does not match the update type 'Setup' that setup is currently looking for.
(04) 2011-06-28 05:03:35 Slp: 
(04) 2011-06-28 05:03:35 Slp: Available Product Updates Discovered:
(04) 2011-06-28 05:03:35 Slp: Title: Hotfix Pack
(04) 2011-06-28 05:03:35 Slp: Knowledge Based Article: KB CU01_RTM1422.3
(04) 2011-06-28 05:03:35 Slp: Version: 11.0.1500.0
(04) 2011-06-28 05:03:35 Slp: Architecture: x64
(04) 2011-06-28 05:03:35 Slp: Language: All
(04) 2011-06-28 05:03:35 Slp: 
(04) 2011-06-28 05:03:35 Slp: 
(04) 2011-06-28 05:03:35 Slp: Product Updates Selected for Installation:
(04) 2011-06-28 05:03:35 Slp: Title: Hotfix Pack
(04) 2011-06-28 05:03:35 Slp: Knowledge Based Article: KB CU01_RTM1422.3
(04) 2011-06-28 05:03:35 Slp: Version: 11.0.1500.0
(04) 2011-06-28 05:03:35 Slp: Architecture: x64
(04) 2011-06-28 05:03:35 Slp: Language: All
(04) 2011-06-28 05:03:35 Slp: 
(04) 2011-06-28 05:03:35 Slp: Update Source: D:\Update Packages
(04) 2011-06-28 05:03:35 Slp: 
(04) 2011-06-28 05:03:35 Slp: Completed Action: SearchUpdatesAction, returned True
(04) 2011-06-28 05:03:35 Slp: ----------------------------------------------------------------------
(04) 2011-06-28 05:03:35 Slp: Running Action: PackageDownloadAction
(04) 2011-06-28 05:03:35 Slp: Completed Action: PackageDownloadAction, returned True
(04) 2011-06-28 05:03:35 Slp: ----------------------------------------------------------------------
(04) 2011-06-28 05:03:35 Slp: Running Action: PackageExtractAction
(04) 2011-06-28 05:03:35 Slp: Completed Action: PackageExtractAction, returned True
(01) 2011-06-28 05:03:35 Slp: Completed Action: RunSmartSetupWorkflow, returned True
(01) 2011-06-28 05:03:35 Slp: Completed Action: ExecuteUpdateInitWorkflow, returned True

Additionally, search for the following:
ProcessUpdateParametersAction
This section is basically a summary similar to the contents of the Detail Component Update log. For example:
(01) 2011-06-28 06:02:43 Slp: ----------------------------------------------------------------------
(01) 2011-06-28 06:02:43 Slp: Running Action: ProcessUpdateParametersAction
(01) 2011-06-28 06:02:43 Slp: 
(01) 2011-06-28 06:02:43 Slp: Product Updates Selected for Installation:
(01) 2011-06-28 06:02:43 Slp: Title: Hotfix Pack
(01) 2011-06-28 06:02:43 Slp: Knowledge Based Article: KB CU01_RTM1422.3
(01) 2011-06-28 06:02:43 Slp: Version: 11.0.1500.0
(01) 2011-06-28 06:02:43 Slp: Architecture: x64
(01) 2011-06-28 06:02:43 Slp: Language: All
(01) 2011-06-28 06:02:43 Slp: 
(01) 2011-06-28 06:02:43 Slp: Update Source: D:\Update Packages
(01) 2011-06-28 06:02:43 Slp: 
(01) 2011-06-28 06:02:43 Slp: 
(01) 2011-06-28 06:02:43 Slp: Product Update Status:
(01) 2011-06-28 06:02:43 Slp: Success: KB CU01_RTM1422.3
(01) 2011-06-28 06:02:43 Slp: Completed Action: ProcessUpdateParametersAction, returned True
(01) 2011-06-28 06:02:43 Slp: ----------------------------------------------------------------------

In these examples, you can clearly see the workflow of each action and any error messages that occurred during that action. For most searches, include both the action and the error message in your search to best help find the solution. For example, if an error occurred during SearchUpdatesAction, search the Microsoft Knowledge Base for the following:
SearchUpdatesAction error 0xc0000005

REFERENCES

For more information about the Product Update feature in SQL Server "Denali," visit the following Microsoft Developer Network (MSDN) websites:
"Product Update" in SQL Server code-named "Denali"

Product Updates in SQL Server "Denali" Installation
For more information about how to view and to read SQL Server Setup log files, visit the following Microsoft TechNet website:
How to: View and Read SQL Server Setup Log Files

Properties

Article ID: 2528485 - Last Review: August 18, 2011 - Revision: 1.0
Keywords: 
kbexpertiseinter kbprb kbsurveynew KB2528485

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com