SQL Server
United States - English
Home
2012
2008 R2
2008
2005
2000
Library
Forums
10 out of 19 rated this helpful - Rate this topic

How to: View SQL Server 2005 Setup Log Files

SQL Server 2005

Logging for Microsoft SQL Server Setup has changed in this release. The main log you should look at is located in

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

This file will have content like:

--------------------------------------------------------------------------------

Machine : MYSERVER

Product : Microsoft XML Parser

Product Version : 8.60.1639.0

Installation : Successful

--------------------------------------------------------------------------------

Machine : MYSERVER

Product : MSXML 6.0 Parser and SDK

Product Version : 6.00.3562.0

Installation : Successful

--------------------------------------------------------------------------------

Machine : MYSERVER

Product : Microsoft SQL Server 2005 Analysis Services

Product Version : 9.00.787

Installation : Successful

--------------------------------------------------------------------------------

Machine : MYSERVER

Product : Microsoft SQL Native Client

Product Version : 9.00.121

Installation : Successful

--------------------------------------------------------------------------------

If the log file shows a failure for a "Product" you can investigate the root cause of the failure by looking at the log for that product (search for "return value 3"). The product logs can be found in:

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

The logs have the following naming convention:

SQLSetup[XXXX][s]_[COMPUTERNAME]_[PRODUCTNAME]_[Y].log, where

  • XXXXX = the enumerated number of the install, where the last installation performed has the highest number
  • COMPUTERNAME= The computer where Setup is being run
  • PRODUCTNAME= Product name (the name of the .msi file); for example, SQLSetup0001_MachineName_RS.log for Reporting Services, SQLSetup0001_MachineName_NS.log for Notification Services
  • Y= If a Microsoft Windows Installer file (.msi) is installed more than once during a single setup run this number is added and incremented to the log name. This is mainly seen for Microsoft XML Core Services (MSXML).

The following table contains sample log file names and log file descriptions for installation of each SQL Server component.

Log file Description

SQLSetup0001_MachineName_Core.log

The primary SQL Server Setup log file that contains information about the success or failure of all .msi installations.

SQLSetup0001_MachineName_SCC.log

Detailed information from the SQL Server 2005 System Configuration Checker that runs system checks during SQL Server Setup.

SQLSetup0001_MachineName_SQL.log

The Database Engine Setup log file.

SQLSetup0001_MachineName_AS.log

The Analysis Services Setup log file.

SQLSetup0001_MachineName_RS.log

The Reporting Services Setup log file.

SQLSetup0001_MachineName_NS.log

The SQL Server 2005 Notification Services Setup log file.

SQLSetup0001_MachineName_DTS.log

The Integration Services Setup log file.

SQLSetup0001_MachineName_Tools.log

The client components, SQL Server Management Studio, and Books Online Setup log file.

SQLSetup0001_MachineName_WI.log

The Setup user interface (UI) Setup log file.

SQLSetup0001_MachineName_SNAC.log

The SQL Server Native Client Setup log file.

SQLSetup0001_MachineName_.NET Framework 2.0.log

The .NET Framework 2.0 Setup log file.

SQLSetup0001_MachineName_MSXML.log

MSXML Setup log file.

SQLSetup0001_MachineName_SQLXML.log

SQLXML Setup log file.

SQLSetup0001_MachineName_Logs.cab

For failover cluster installations, this file will contain logs from all cluster nodes.

SQLSetup0001_MachineName_Datastore.xml

A dump of all properties that are cached during Setup. This information may be requested by Product Support Services to troubleshoot and debug failures.

Tasks

How to: Read a SQL Server 2005 Setup Log File

Concepts

Troubleshooting an Installation of the SQL Server Database Engine

Help and Information

Getting SQL Server 2005 Assistance
Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Contents of Summary.txt file from SQL Server 2008 SP3 Failed Install

Adding this per request from Albert Morillo in response to a posting I added yesterday to the SQL Server Setup & Upgrade forum in Technet.


Overall summary:

Final result: The patch installer has failed to update the following instance: SQLEXPRESS. To determine the reason for failure, review the log files.

Exit code (Decimal): -2068643839

Exit facility code: 1203

Exit error code: 1

Exit message: The patch installer has failed to update the following instance: SQLEXPRESS. To determine the reason for failure, review the log files.

Start time: 2011-12-01 11:42:47

End time: 2011-12-01 11:55:43

Requested action: Patch


Instance SQLEXPRESS overall summary:

Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.

Exit code (Decimal): -2068643839

Exit facility code: 1203

Exit error code: 1$

Exit message: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.

Start time: 2011-12-01 11:45:12

End time: 2011-12-01 11:55:41

Requested action: Patch

Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111201_114243\SQLEXPRESS\Detail.txt

Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.5500.0%26EvtType%3d0xCA8CE9A5%400x0A2FBD17%401211%401


Machine Properties:

Machine name: WINDEVHUTRUNKP

Machine processor count: 16

OS version: Windows Server 2003

OS service pack: Service Pack 2

OS region: United States

OS language: English (United States)

OS architecture: x86

Process architecture: 32 Bit

OS clustered: No


Product features discovered:

Product Instance Instance ID Feature Language Edition Version Clustered

Sql Server 2005 Tools 1033 Express Edition 9.4.5000 No

Sql Server 2005 ToolsClient 1033 Express Edition 9.4.5000 No

Sql Server 2005 ToolsClient\Connectivity 1033 Express Edition 9.4.5000 No

Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services 1033 Express Edition 10.1.2531.0 No

Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication 1033 Express Edition 10.1.2531.0 No


Package properties:

Description: SQL Server Database Services 2008

SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}

ProductName: SQL2008

Type: RTM

Version: 10

SPLevel: 3$

KBArticle: KB2546951

KBArticleHyperlink: http://support.microsoft.com/?kbid=2546951

PatchType: SP

AssociatedHotfixBuild: 0

Platform: x86

PatchLevel: 10.3.5500.0

ProductVersion: 10.0.1600.22

GDRReservedRange: 10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0;10.0.4010.0:10.0.4250.0;10.0.5501.0:10.0.5750.0

PackageName: SQLServer2008-KB2546951-x86.exe

Installation location: e:\280325dc10200551a9\x86\setup\

Updated product edition:

Instance Edition

SQLEXPRESS EXPRESS

User Input Settings:

ACTION: Patch

ALLINSTANCES: False

CLUSTERPASSIVE: False

CONFIGURATIONFILE:

HELP: False

INDICATEPROGRESS: False

INSTANCENAME: <empty>

QUIET: False

QUIETSIMPLE: False

X86: False


Rules with failures:

Global rules:

There are no scenario-specific rules.


Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111201_114243\SystemConfigurationCheck_Report.htm


[tfl - 19 11 11] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead,
you should visit the Technet Forums at http://forums.microsoft.com/technet, where such posts are welcomed and where you stand a much
better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.

History