S - Cannot upgrade to SQL Server 2005 Express edition SP 3

Hi,

I cannot upgrade my SQL Server 2005 Express edition to SP3.  It constantly fails with the error: Windows failed to install the following update with error 0x80070643.  Searching on the web gives me no results.  Any ideas or options ?  (Nothing good in event viewer).

Thanks,
 VSACIT
VSACITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VSACITAuthor Commented:
Here is the end of the log file :

Property(S): CostingComplete = 0
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SqlStateManaged = 3
Property(S): SqlActionManaged = 3
Property(S): Sql_sqlSqlUpgradeInstallSequence = 282357800
MSI (s) (A8:B8) [14:26:05:620]: Note: 1: 1729
MSI (s) (A8:B8) [14:26:05:620]: Product: Microsoft SQL Server 2005 Express Edition -- Configuration failed.

MSI (s) (A8:B8) [14:26:05:808]: Cleaning up uninstalled install packages, if any exist
MSI (s) (A8:B8) [14:26:05:808]: MainEngineThread is returning 1603
MSI (s) (A8:C4) [14:26:05:808]: Destroying RemoteAPI object.
MSI (s) (A8:34) [14:26:05:808]: Custom Action Manager thread ending.
=== Logging stopped: 6/30/2009  14:26:05 ===
MSI (c) (60:A0) [14:26:05:823]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (60:A0) [14:26:05:823]: MainEngineThread is returning 1603
=== Verbose logging stopped: 6/30/2009  14:26:05 ===
0
Jim P.Commented:
Which KB is this?

Have you downloaded and done it manually, or is it firing from WSUS?

What is the OS of the machine?

What is the results from
-----------------------------------------
SELECT @@Version
-----------------------------------------
0
VSACITAuthor Commented:
This is not from a KB, this is from the error log I got.

I have tried manually, as well as from liveupdate, as well as from HFNetcheck (SUS equivalent).

It is a Windows 2003 SP 2 server.  I am running SQL Server Express 2005 SP 2, so I cannot run the query.  What utility can I use to get that info ?

Thanks
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Jim P.Commented:
>> This is not from a KB

It should say somewhere in the title or log something about
"SQLTools9_Hotfix_KB960089_sqlrun_tools.msp.log" or inside find "KBNUMBER=KB960089"

>> I am running SQL Server Express 2005 SP 2, ...

There is a free downloadable SQL Server Management Studio Express. You can do it in there. You can also use the SQLCMD from a DOS prompt.

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLCMD.EXE


Microsoft SQL Server Management Studio Express
http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
0
VSACITAuthor Commented:
When I bring up the SQLCMD.exe and paste in your command, I get no results.  The file is called SQLSetup0022_Netmon2_SQL.log.  The text kbnumber= is not found on my server anywhere.

0
Jim P.Commented:
Here is the syntax for the SQLCMD:
------------------------------------------------------------------
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqlcmd -S MySrvr\MyInstance -U sa -P MyPassword -q "select @@version"
------------------------------------------------------------------

Do you have a folder like this?
------------------------------------------------------------------
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB955706_SQLEXPR.EXE\Files
------------------------------------------------------------------
And if you go to the summary.txt at the \SQL9Express_Hotfix_KB955706_SQLEXPR.EXE\ root -- is this the first error?
0
VSACITAuthor Commented:
Within the C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB955706_SQLEXPR.EXE\Files directory, there are lots of log files, but no txt file.

Your command seems to work, but what is the context for the default instance, is it SERVERNAME\Default ?

0
Jim P.Commented:
Then it would be
------------------------------------------------------------------
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqlcmd -S MySrvrName -U sa -P MyPassword -q "select @@version"
------------------------------------------------------------------

From eggheadcafe.com
------------------------------------------------------------------
Note If you are upgrading from SQL Server 2005 SP2 Cumulative Update 10 or
from SQL Server 2005 SP2 Cumulative Update 11, you must apply a post-SQL
Server 2005 SP3 cumulative update after you upgrade to SQL Server 2005 SP3
to obtain all the fixes.
For more information about the post-SQL Server 2005 SP3 cumulative update,
click the following article number to view the article in the Microsoft
Knowledge Base: http://support.microsoft.com/kb/959195/
Source: http://support.microsoft.com/kb/955706
--
~Robear Dyer (PA Bear)
------------------------------------------------------------------

http://www.eggheadcafe.com/conversation.aspx?messageid=33986750&threadid=33986741
0
VSACITAuthor Commented:
so after I type in the password, it goes right back to a prompt, with out any results.  Am I missing something ?

But I am not running SP3 on the default instance yet.  And it is weird that my default instance will not upgrade, while the other two did.

0
Jim P.Commented:
This isn't a Domain Controller machine?

KB955706 fails to install
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=426402

Try it this way:
------------------------------------------------------------------
"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqlcmd" -S MySrvrName -U sa -P MyPassword
------------------------------------------------------------------

It should leave you at a prompt like:
------------------------------------------------------------------
1>
------------------------------------------------------------------

Then do:
------------------------------------------------------------------
1> select @@version
2> go

------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------
------------------------------
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
        Nov 24 2008 13:01:59
        Copyright (c) 1988-2005 Microsoft Corporation
        Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)



(1 rows affected)
1>
------------------------------------------------------------------
0
VSACITAuthor Commented:
That worked ... I got as a reply :

-----------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------
------------------------------------------------------------
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
        Nov 24 2008 13:01:59
        Copyright (c) 1988-2005 Microsoft Corporation
        Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)


(1 rows affected)

This is not a DC ...

0
Jim P.Commented:
Are you using the the service pack from this download?

SQLEXPR32.EXE  35.9 MB

http://www.microsoft.com/downloads/details.aspx?FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6&displaylang=en
0
VSACITAuthor Commented:
I used SQLEXPR.exe.  I tried your 32.exe and got a different message in the log (it still failed the install though ... )

Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2:  3:  4:  



Error Code: 1627
MSI (s) (E4!B4) [07:47:24:287]: Product: Microsoft SQL Server 2005 Express Edition -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database:  Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database:  Table(s) Update failed
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Wed Jul 08 07:47:24 2009
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (E4!B4) [07:47:24:693]: Note: 1: 2205 2:  3: _sqlSqlUpgradeInstallSequence
MSI (s) (E4!B4) [07:47:24:693]: Note: 1: 2228 2:  3: _sqlSqlUpgradeInstallSequence 4: CREATE TABLE `_sqlSqlUpgradeInstallSequence` (`Action` CHAR(255) NOT NULL, `Sequence` INT NOT NULL, `Param` CHAR(0), `Retryable` INT NOT NULL, `Fatal` INT NOT NULL PRIMARY KEY `Action`, `Sequence`)
MSI (s) (E4!B4) [07:47:24:709]: Note: 1: 2262 2: _sqlSqlUpgradeInstallSequence 3: -2147287038
<Func Name='GetFileTargetPath'>
MSI (s) (E4!B4) [07:47:24:740]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '282314400'. Its new value: '297314400'.
MSI (s) (E4!B4) [07:47:24:756]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '297314400'. Its new value: '297354400'.
MSI (s) (E4!B4) [07:47:24:756]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '297354400'. Its new value: '297364400'.
MSI (s) (E4!B4) [07:47:24:771]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '297364400'. Its new value: '367364400'.
MSI (s) (E4!B4) [07:47:24:771]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '367364400'. Its new value: '549528800'.
MSI (s) (E4!B4) [07:47:24:771]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '549528800'. Its new value: '564528800'.
MSI (s) (E4!B4) [07:47:24:787]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '564528800'. Its new value: '564628800'.
Couldn't find SQL Agent service SQLSERVERAGENT. Skipping service stop
<EndFunc Name='SqlComponentUpgrade' Return='0' GetLastError='0'>
Added REPL to SqlUpgrade property
0
Jim P.Commented:
Are any of the SQL Services set to disabled in the services.msc? If so, change them to manual.

And what account are the SQL Services running under?


The other thing to try is just run an unpack only, then try from that after a reboot. The easiest way I found to get the unpacked files is fire up the installer. Then on one of your local drives, you'll have a directory that is like "a2167flagkdadsaooter" (some long gobbeldy gook name). Copy the files out to a new directory. Then end the install. Reboot, and try the install from the copied files.
0
VSACITAuthor Commented:
Nope, all three are set to automatic, all started, and all log on as "Network Service".

I have tried copy the files out of that ugly temp directory and running it that way.  Still no go.  Also a pain that the ugly directory disappears after the install fails.
0
Jim P.Commented:
>> Nope, all three are set to automatic, all started,
>> and all log on as "Network Service".

There should be some others like SQL AD Helper. Are they set to Manual as well and not Disabled?

>>  Also a pain that the ugly directory disappears after the install fails.

There is a command line to unpack only. I have just found it is easier to copy it off after the installer unpacks the files for you.
Name				Status  Startup Type	Log On As
SQL Server (Instance2)		Started	Automatic	Network Service
SQL Server (Instance3)		Started	Automatic	Network Service
SQL Server (MSSQLSERVER)		Manual		MyDomain\MyUser
SQL Server Active Directory Helper	Manual		Network Service
SQL Server Browser		Started	Automatic	MyDomain\MyUser
SQL Server Integration Services	Started	Automatic	Network Service
SQL Server VSS Writer		Started	Automatic	MyDomain\MyUser

Open in new window

0
VSACITAuthor Commented:
The only ones not running are :
SQL Server Active Directory Helper
SQL Server Browser
0
Jim P.Commented:
The SQL Server Browser should be up -- that's the redirector if you have multiple instances running on a single server using ports 1433/1434.

And the AD helper is not disabled?

SQL Server Browser Service
http://msdn.microsoft.com/en-us/library/ms181087.aspx
0
VSACITAuthor Commented:
same error 2259.  The AD helper was disabled.
0
VSACITAuthor Commented:
different error this time.  See attached pic.
Picture-1.png
0
Jim P.Commented:
Were you able to reboot before trying it this latest time?
0
VSACITAuthor Commented:
yup, I have rebooted multiple times ...
0
Jim P.Commented:
I just looked at your http:/Q_24533377.html#24797322 again.

Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)

That is SP3.

If you run the query
-----------------------------------
SELECT  SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
-----------------------------------

Through the SQLCMD.

SQL Server 2005 Service Pack 3      2005.90.4035

How to identify your SQL Server version and edition
http://support.microsoft.com/kb/321185
0
VSACITAuthor Commented:
Then why, when I go to SQL Server Configuration Manager, does it say that SQL Server (MSSQLSERVER) says SP level 2 under the advanced tab, while SQL Server (HPWJA) and SQL server (SQLExpress) say SP 3 ?

0
Jim P.Commented:
It is now sounding like a dll or exe didn't get updated.

The best way to identify the bad file(s) would be to grab a copy of Beyond Compare from http://www.scootersoftware.com. (The 30 day trial is a fully functional version, and to buy it at $30-$50 license cost is so truly worth the cost to have in your toolkit.)

Load it on the server and then do a compare of the C:\Program Files\Microsoft SQL Server\MSSQL.#\ folders.

If you find mismatches in the .exe/.dll files you should be able extract the list shut down both services copy one to the other and then manually register them (i.e. regsvr32 NewSQL.DLL file).

At this point it is my best suggestion. You can't really do a support call to M$ on SQL Express. I know it isn't pretty, but.....
0
VSACITAuthor Commented:
Yeah, that is the worst part, Microsoft creates a product, provides no support for it, and if you want support, get a paid for version first, and then spend the 250 bucks on a support call.

Comparing files and registering DLLS did not seem to help.
0
Jim P.Commented:
Do they all match? If so, then it is time to look in the registry.

Take all the required backups and the warnings about editing the registry. I won't repeat them; but the cautions are in place.

There are 2 different keys that can be causing this:
-----------------------------------------------------------------------
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.#\Setup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.#
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
-----------------------------------------------------------------------

As long as you have confirmed the sqlservr.exe and other files are correct in the X:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL\Binn directory, then it sounds like the issue is that the registry is a little off. The first key has the version number in it. Update that and hopefully your issues should be solved.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
VSACITAuthor Commented:
That was the ticket.  I fixed the registry keys accordingly.  Thanks for all your help.
0
Jim P.Commented:
Glad to be of assistance. May all your days get brighter and brighter.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.