July 10, 2008 at 10:10 am
I just tried to install the critical update KB948109 for service pack 2 of SQL Server 2005, but it failed. This is on our test database server, which has a pitifully low amount of disk space on the system drive (< 1 GB). Could the low disk space be the cause of the problem?
Kindest Regards, Rod Connect with me on LinkedIn.
July 10, 2008 at 12:45 pm
It could.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 10, 2008 at 1:11 pm
check the log produced by the install for errors:
%PROGRAMFILES%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
If this patch has a tendency to fail would sure like to know about it.Were you able to back it out?
---------------------------------------------------------------------
July 10, 2008 at 2:05 pm
George, it is a rather large .LOG file (~ 9 MB in size), and I see several errors in it, even at the beginning. However, I will assume that the fatal error occrred towards the end of the .log file and so I'll copy that here:
Property(S): DTS200532Hotfix3042 = c:\WINDOWS\Installer\c762fd.msp
MSI (s) (48:10) [03:14:00:243]: Product: Microsoft SQL Server 2005 Integration Services - Update 'GDR 3068 for SQL Server Integration Services 2005 ENU (KB948109)' installed successfully.
MSI (s) (48:10) [03:14:00:243]: Note: 1: 1728
MSI (s) (48:10) [03:14:00:274]: Transforming table Error.
MSI (s) (48:10) [03:14:00:274]: Transforming table Error.
MSI (s) (48:10) [03:14:00:274]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:10) [03:14:00:274]: Transforming table Error.
MSI (s) (48:10) [03:14:00:274]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:10) [03:14:00:274]: Transforming table Error.
MSI (s) (48:10) [03:14:00:274]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:10) [03:14:00:290]: Transforming table Error.
MSI (s) (48:10) [03:14:00:305]: Transforming table Error.
MSI (s) (48:10) [03:14:00:305]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:10) [03:14:00:305]: Transforming table Error.
MSI (s) (48:10) [03:14:00:305]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:10) [03:14:00:305]: Transforming table Error.
MSI (s) (48:10) [03:14:00:305]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:10) [03:14:00:305]: Product: Microsoft SQL Server 2005 Integration Services -- Configuration completed successfully.
MSI (s) (48:10) [03:14:00:321]: Attempting to delete file C:\WINDOWS\Installer\2eea6a34.msp
MSI (s) (48:10) [03:14:00:321]: Unable to delete the file. LastError = 32
MSI (s) (48:10) [03:14:00:352]: Cleaning up uninstalled install packages, if any exist
MSI (s) (48:10) [03:14:00:352]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\2eea6a34.msp'
MSI (s) (48:10) [03:14:00:352]: MainEngineThread is returning 0
MSI (s) (48:08) [03:14:00:352]: Destroying RemoteAPI object.
MSI (s) (48:DC) [03:14:00:352]: Custom Action Manager thread ending.
=== Logging stopped: 7/9/2008 3:14:00 ===
MSI (c) (4C:50) [03:14:00:415]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (4C:50) [03:14:00:415]: MainEngineThread is returning 0
=== Verbose logging stopped: 7/9/2008 3:14:00 ===
Kindest Regards, Rod Connect with me on LinkedIn.
July 10, 2008 at 4:22 pm
Failed for me too, running MSSQL Express at work on a newer laptop w/ plenty of RAM and free disk space, Win XP. It failed when installing via automatic updates. I also tried downloading the patch directly, also did not work. The gold shield keeps popping up in the system tray, but three attempts have failed 🙁
Early today, it succeeded via automatic updates on my two home office PC's running MSSQL Developer, Win XP. It did take quite a long time to install, compared to the usual patches.
Any ideas?
EDIT: For both machines that did work, @@version returns:
Microsoft SQL Server 2005 - 9.00.3068.00 (Intel X86) Feb 26 2008 18:15:01 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
July 11, 2008 at 12:22 am
I've noticed a large number or issues reported on this update.
Not just failures to install, but problems with the SQL instances after the install.
There are some interesting posts on the MS public newsgroups (windowsupdate and sqlserver)
Personally, I'm going to hold off on this for a few days.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 11, 2008 at 3:43 am
gail, intersting news, thanks, I will hold off too.
rod, does @@version return 2273 after you install?
---------------------------------------------------------------------
July 11, 2008 at 8:39 am
On my work PC, the failed update left SQL Server stopped, so it would not connect. (The browser service was still running.) I went into the SAC tool and started the server service, then tried the update & again it failed. Re-started the server service, and here is my @@version:
---
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
---
I asked the network admin about this, they responded:
---
The SQL update issue seems to stem from a configuration issue in SQL.
"GetServiceUserGroup failed for SQLEXPRESS, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No mapping between account names and security IDs was done."
I would suggest a reinstall.
---
Oh well.
July 14, 2008 at 8:42 am
Rod at work (7/14/2008)
george sibbald (7/11/2008)
gail, intersting news, thanks, I will hold off too.rod, does @@version return 2273 after you install?
George, I'm getting a 9.00.3068.00 when I run the @@version.
I'm sorry, I ran it on the wrong server. On the test server, where I'm having problems installing that critical update, when I run @@version I get 9.00.3054.00.
Kindest Regards, Rod Connect with me on LinkedIn.
July 14, 2008 at 10:22 am
I had two issues installing this update. The first issue was because I separate my data files from my log files. This separation has been deployed for both my user databases and my system databases. On one of my servers, the SQL Server service would not restart because the update renamed the log file for mssqlsystemresource and put the renamed file in the same folder as the log file. On another server, it tried to make a copy of distmdl.ldf (which is a template for creating the distribution database used for replication). It expected this file to be in the same folder as distmdl.mdf. so when it didn't find it there, it threw an error.
If you look in the log for the hotfix ("SQL9_Hotfix_KB948109_sqlrun_sql.msp_9.log"), which is usually in "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\" you'll see an error like this one:
Error 29538. SQL Server Setup did not have the administrator permissions required to rename a file: "e:\MSSQL\Data\distmdl1.ldf". To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again. The error code is (2) The system cannot find the file specified.
I knew my account couldn't be the problem because I a member of both the Windows Administrator group and the SQL Server sysadmin group. So I moved the distmdl.ldf file to e:\MSSQL\Data and the update installed.
It's kind of irritating for the update to have issues with log files being separated from data files, when Microsoft preaches this very practice as a "Best Practice".
“If you're not outraged at the media, you haven't been paying attention.”
July 14, 2008 at 3:48 pm
oops, its 2005 so it wouldn't return 2273 would it....:blush:
if its still 3054 hotfix definitely not applied.
From the errorlog it was unable to delete file because:
The process cannot access the file because it is being used by another process.
two upgrades running at once perhaps?
the Transforming table Error message, any files in your data folder in read only mode? Only post I can find points to backupexec which creates read only copies of the database files in the data folder, and this caused a problem with an upgrade (to SP1)
---------------------------------------------------------------------
July 15, 2008 at 10:38 am
My boss sent me this link to a post that contains the reg keys to delete. I tried it, the patch worked, and my version is 3068 hurray.
This fixed it for me:
1. Remove the following registry subkeys that store SID settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\SQLGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\AGTGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\FTSGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\ASGroup
Note In these registry subkeys, MSSQL.X is a placeholder for the
corresponding value on a specific system. You can determine MSSQL.X on a
specific system by examining the value of the MSSQLSERVER registry entry
under the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance
Names\SQL\
2. Reinstall the SQL Server 2005 service pack or the SQL Server 2005 hotfix
package.
July 28, 2008 at 5:05 am
I received this error while applying the Patch KB948109. In Aaron Stebner's weblog he elaborates on a way to find the error in the verbose logging of the patch. In this case the logfile C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log
Search for the string "return value 3". In this way I found this error:
GetServiceUserGroup failed for SBO, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No mapping between account names and security IDs was done.
This relates to a known issue http://support.microsoft.com/kb/925976
The workaround worked for me. Please make an export of the registry before applying the workaround.
Greets,
Rob
July 28, 2008 at 2:03 pm
That's SP2
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply