| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
|
| Windows Update for KB948109 (SQL Server 2005) fails repeatedly with unelaborated error code 66E. I have found one other report of this particular failure in the Windows Update newsgroup and many reports of failure with 735D. I tried a manual install of KB948109 with no success. This with Vista SP1 (x86). This update appears to be all over the floor, so I suppose I just need to be patient and put up with repeated attempts to reinstall every time I shut down. -- Walt |
|
#2
|
| MS is offering free support on the KB948110, (same problem - update wont install), I suspect they are doing the same for the KB948109. I just tried reinstalling the SP4 update on the MSFW from WMSDE for the Server 2003 R2 with no result... KB still fails. It looks like I will have to call MS on this. I see the problem popping up all over the internet - so far, no solutions. -- Regards, Jamie "WaltN" wrote: > Windows Update for KB948109 (SQL Server 2005) fails repeatedly with > unelaborated error code 66E. I have found one other report of this > particular failure in the Windows Update newsgroup and many reports of > failure with 735D. I tried a manual install of KB948109 with no success. > This with Vista SP1 (x86). This update appears to be all over the floor, so > I suppose I just need to be patient and put up with repeated attempts to > reinstall every time I shut down. > -- > Walt |
|
#3
|
| Hello there, found five other reports on other website just about a day after the patch was out, so this seems to be not to seldom a problem. However on one of my computers it simply worked, o the other it did not. Its difficult to figure out relevant differences. Not working on intel dual core preinstallend vista home premium, now with sp 1, all other patches, in use for about 9 months. Working on a freshly installed vista with sp1, all other patches on an "aldi notbook" which is an msi wind u100 essentially. Its just one week on the market. Both computers have VS 2008, office 2007 including access 2007, adobe flash, adobe air and adobe acrobat reader (i hate it), silverlight installed. Both unfortunaltely are 32-bit cpus. Regards, Frank |
|
#4
|
| Microsoft's update site is a free web chat site. They hooked me up with a batch file to clean up the issue. In the post previous to this one with the KB948110 label, I review their steps. Whatever the issue is, it gets cleaned right up. In my case I suspected the Windows Defender. -- Regards, Jamie "F.L." wrote: > Hello there, > > found five other reports on other website just about a day after the patch > was out, so this seems to be not to seldom a problem. > > However on one of my computers it simply worked, o the other it did not. Its > difficult to figure out relevant differences. > > Not working on intel dual core preinstallend vista home premium, now with sp > 1, all other patches, in use for about 9 months. > > Working on a freshly installed vista with sp1, all other patches on an "aldi > notbook" which is an msi wind u100 essentially. Its just one week on the > market. > > Both computers have VS 2008, office 2007 including access 2007, adobe flash, > adobe air and adobe acrobat reader (i hate it), silverlight installed. Both > unfortunaltely are 32-bit cpus. > > Regards, > Frank |
|
#5
|
| Even I am facing the same problem with Windows Vista SP1 and from yesterday it is contineously prompting for new software updates available, but when I try to install it is not getting installed. Thanks Chand "WaltN" wrote: > Windows Update for KB948109 (SQL Server 2005) fails repeatedly with > unelaborated error code 66E. I have found one other report of this > particular failure in the Windows Update newsgroup and many reports of > failure with 735D. I tried a manual install of KB948109 with no success. > This with Vista SP1 (x86). This update appears to be all over the floor, so > I suppose I just need to be patient and put up with repeated attempts to > reinstall every time I shut down. > -- > Walt |
|
#6
|
| Just to add that I have also received a failure on this SQL 2005 update (66E). I also have VS2005, Office 2003 and an AMD Athlon Dual-Core TK-55. Hope we can all get past this annoyance soon. Phil "WaltN" wrote: > Windows Update for KB948109 (SQL Server 2005) fails repeatedly with > unelaborated error code 66E. I have found one other report of this > particular failure in the Windows Update newsgroup and many reports of > failure with 735D. I tried a manual install of KB948109 with no success. > This with Vista SP1 (x86). This update appears to be all over the floor, so > I suppose I just need to be patient and put up with repeated attempts to > reinstall every time I shut down. > -- > Walt |
|
#7
|
| UPDATE: I have established contact with Windows Update email support on this matter. They suggested that I manually install the update, available as a separate download. This is something I had done previously on my own with no success. The standalone install fails with an error code of 1646, which is 0x66E. It identifies a log file, which identifies the problem as an inability to remove Hotfix 3024, a previous patch. I have replied to Windows Update email support, reporting this and including the log file. I am awaiting their replay. My fear is that they will throw up their arms and try to send me to SQL support, which is a for-charge service. -- Walt |
|
#8
|
| > Microsoft's update site is a free web chat site. They hooked me up with a > batch file to clean up the issue. I just spent a couple of hours with the chat site and they couldn't help but didn't suggest a batch file to clean the issue. Can you please post what was in the batch file they gave you? |
|
#9
|
| FURTHER UPDATE: Windows Update Support has passed me to SQL Server (PAID) Support. I objected strenuously. I requested that Windows Update at least tell me how to get their damned update out of Vista's "Power" button queue. -- Walt |
|
#10
|
| RESOLVED: KB948109 install failure with error code 1646 (0x66e) finally resolved by Microsoft support. It took an entire morning, and, when I finally got proper attention, it took a guy the better part of an hour working with a remote console to get a good install of KB948109. I started Saturday by initiating an email session with Windows Update Support. Sunday, they told me to seek paid SQL Server support. This morning, I tried a chat session as recommended by MS08-040 via a link to PC Safety Support. They told me they deal only with viruses and spyware, and they sent me to SQL Server Support. Getting through the call-screener, kicking and screaming when they suggested paid support, the technical person wouldn’t work on the problem when he found out I wasn’t a business. However, he sent me to 1-800-936-5700 and told me specifically to request an “escalation specialist.” Surviving another call-screener got me to a guy who was willing to take over my machine with a remote console. He attempted an install of KB948109 via Windows Update, and it failed, as before. Then he did some fiddling around (to be described below) and downloaded the standalone install, SQLServer2005-KB948109-x86-ENU.exe. The install succeeded. The fiddling did the job. In signing off, I asked the guy what I could tell other people who had the problem. He told me he renamed two folders: C:\Windows\System32\CatRoot2 and C:\Windows\SoftwareDistribution by appending a .old suffix to each folder’s name. This before the install with SQLServer2005-KB948109-x86-ENU.exe. (I might add that he did this with User Account Control turned off, although I suspect this was not necessary.) He explained that these two folders were used by the update mechanism, and one of the files must have been “corrupted.” (Oh how I hate that meaningless word.) By renaming the folders, the update mechanism rebuilt the original folders properly and the standalone install succeeded. -- Walt |
![]() |
| Thread Tools | |
| Display Modes | |