RE: Can't install Service Pack 3.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




..) Start the SQL Server 2005 SP3 installation. When it fails refer to the
log file.

2.) You can refer the installation log stored at “C:\Program
Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB955706_sqlrun_tools.msp.log” the path
may differ according to your installation.

3.) When you will refer this log file you will find it is unable to find
one .msp file which ideally should be in .\windows\installer folder. This
file name is different for each n every server. Now the work around will be
as below-

“Download the SQL Server 2005 SP2 if you have it already then it’s cool.
Extract the *.exe by using /extract or /x switch to a folder. Now search for
“sqlrun_sql.msp” file. Rename this file by copying it somewhere else to the
same name which the log file is showing missing in c:\windows\installer
folder and paste the file to C:\windows\installer folder.

4.) Now run the SP3 setup again. It should be completed this time. But if
still fails, refer the log file again. Now what you will found that that it
has found the previously missed .msp file but got struck at the second .msp
file (In my case it was like this). Now the workaround is-

“Go Ahead and download SQL Server 2005 SP1 and extract it the same way as we
did about SP2 now again search for “sqlrun_sql.msp” file and paste it to the
c:\windows\installer and rename it to the the name which log file is showing
missing.”

Now run the SP3 setup again and this time you should be successful.

The Sample Installation Log File

*************************************************************

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: UIText 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: Media 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: Shortcut 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: SxsMsmGenComponents 3:
-2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: RemoveFile 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: Environment 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _sqlUpgradeFile 3:
-2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _sqlUpgradeRegistry 3:
-2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _sqlUpgradeFolders 3:
-2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _MsiPatchTransformView 3:
-2147287038

MSI (s) (44:80) [14:29:07:518]: Opening existing patch
‘C:\WINDOWS\Installer\2691b4.msp’.———-“In first failure this msp file was
causing failure.”

MSI (s) (44:80) [14:29:07:518]: Opening existing patch
‘C:\WINDOWS\Installer\389d4c59.msp’.———“In second failure this msp file was
causing failure.”

MSI (s) (44:80) [14:29:07:518]: File will have security applied from OpCode.

MSI (s) (44:80) [14:29:14:394]: Original patch ==>
d:\604b2713b936ee0404\HotFixSQL\Files\sqlrun_sql.msp

MSI (s) (44:80) [14:29:14:394]: Patch we’re running from ==>
C:\WINDOWS\Installer\8ecaac.msp

MSI (s) (44:80) [14:29:14:394]: Opening existing patch
‘C:\WINDOWS\Installer\4208e404.msp’.

*******************************************************************

"minfald" wrote:

It seems the C:\windows\installer files from previous SQL server installs
were deleted. Thus when I attempt to upgrade to SQL Server 2005 SP3, I
receive the "the feature you are trying to install is not....." error.

The logs indicate as follows:

SOURCEMGMT: Now checking product {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
MSI (s) (24:2C) [22:23:44:867]: SOURCEMGMT: Media is enabled for product.
MSI (s) (24:2C) [22:23:44:867]: SOURCEMGMT: Attempting to use LastUsedSource
from source list.
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (24:2C) [22:23:44:914]: SOURCEMGMT: Source is invalid due to
missing/inaccessible package.
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 1706 2: -2147483647 3:
SqlRun_DTS.msi
MSI (s) (24:2C) [22:23:44:914]: SOURCEMGMT: Processing net source list.
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 1402 2: UNKNOWN\Net 3: 2
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 1706 2: -2147483647 3:
SqlRun_DTS.msi
MSI (s) (24:2C) [22:23:44:914]: SOURCEMGMT: Processing media source list.
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 1706 2: -2147483647 3:
SqlRun_DTS.msi
MSI (s) (24:2C) [22:23:44:914]: SOURCEMGMT: Processing URL source list.
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 1706 2: -2147483647 3:
SqlRun_DTS.msi
MSI (s) (24:2C) [22:23:44:914]: Note: 1: 1706 2: 3: SqlRun_DTS.msi
MSI (s) (24:2C) [22:23:45:586]: SOURCEMGMT: Failed to resolve source

How do I get around this?

Thank you.
.



Relevant Pages

  • Re: **to trace what has happened**
    ... Andrew J. Kelly SQL MVP ... time should I save the changes as a log file, or is there any place to ... SQL Server will not log the events by default. ... I don't want to monitor the changes simentanously, I want to refer to ...
    (microsoft.public.sqlserver.security)
  • Re: PerfMon recording to SQL 2005
    ... I've been out of the SQL world for a couple years so dusting ... A System DSN, specifying windows authentication, and change to an ... Configuring the log file, choose the tested DSN as the System DSN ... The user account I created in SQL is an owner of the ...
    (microsoft.public.sqlserver.server)
  • Re: PerfMon recording to SQL 2005
    ... I've been out of the SQL world for a couple years so dusting off ... A System DSN, specifying windows authentication, and change to an existing ... Configuring the log file, choose the tested DSN as the System DSN ... The user account I created in SQL is an owner of the ...
    (microsoft.public.sqlserver.server)
  • Re: recover mode and the transaction log file question
    ... Andrew J. Kelly SQL MVP ... "Dan Guzman" wrote in message ... > changing the recovery model to FULL. ... >> I have setup the log file to not grow at all. ...
    (microsoft.public.sqlserver.programming)
  • Re: Security Update for SQL Server 2005 Service Pack 2 (KB948109)
    ... through the latest log file Summary.txt under the directory C:\Program ... SQL Express Features: ... that the account and domain running SQL Server Setup exist, ... have the administrator permissions required to rename a file: C: ...
    (microsoft.public.windowsupdate)