1. Go to Run, type regedit, and click ok, or press Enter. 2. Back up your registry, if you don't know how to do this, google it... 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup] [Note that if you have multiple instances of MSSQL installed, the reg key might be different for you] 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. 5. install the update, and restart the machine.
If you don't want to install this update using the automatic update (WUAUCLT), you can download the hotfix directly from microsoft, just google "download KB970892 ". you will still need to manually change the registy "Resume" value, or else the hotfix will fail to install...
> Someone more with the same problem. KB970892 failed with error code > 0x80070643. Running sql desktop engine sp3 on windows xp. After uninstalling > and re-installting the sql server the problem was gone - but it returned > after the next windows update.
> Folder compression is disabled. What else could cause this error?
Sorry for posting this twice, i didn't know that it wasn't the last page :)
Hi there,
To resolve this issue, do the following:
1. Go to Run, type regedit, and click ok, or press Enter. 2. Back up your registry, if you don't know how to do this, google it... 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup] [Note that if you have multiple instances of MSSQL installed, the reg key might be different for you] 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. 5. install the update, and restart the machine.
If you don't want to install this update using the automatic update (WUAUCLT), you can download the hotfix directly from microsoft, just google "download KB970892 ". you will still need to manually change the registy "Resume" value, or else the hotfix will fail to install...
I had this issue on one of the servers of the company that I work for, and it is a SharePoint server. I resolved it using the points described above.
> > > The above update has failed; does anyone know either how to resolve > > > this issue or disable the update requirement
> > Is the SQL Server service actually running?
> > The update will fail if it's not, with something like this in the System > > event log:
> > Windows Update Agent Event_ID 20
> > Installation Failure: Windows failed to install the following update > > with error 0x80070643: Security Update for SQL Server 2005 Service Pack > > 3 (KB970892).
> > -- > > Bert Hyman St. Paul, MN b...@iphouse.com > > . > > Interesting note - I'm getting the same thing without any error indicated, just "not installed." Watching the system as the update is being "installed", SQL Server 2005 starts out activated. At some point during the process however, it shuts down. A few seconds later, the window then indicates it was not installed. I'm running WinXP Pro as well.
Berry, to answer your question, the MSSQL service is operational when you try to install the hotfix, when the hotfix runs, it stops the service during the installation so that it can overwrite some older files, and in the end it should start the service again. but since the update is failing, it is not operating the way that it's designed, and thus does not restart the service.
"David Kochkerian" wrote: > Sorry for posting this twice, i didn't know that it wasn't the last page :)
> Hi there,
> To resolve this issue, do the following:
> 1. Go to Run, type regedit, and click ok, or press Enter. > 2. Back up your registry, if you don't know how to do this, google it... > 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL > Server\MSSQL.1\Setup] > [Note that if you have multiple instances of MSSQL installed, the reg key > might be different for you] > 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. > 5. install the update, and restart the machine.
> If you don't want to install this update using the automatic update > (WUAUCLT), you can download the hotfix directly from microsoft, just google > "download KB970892 ". you will still need to manually change the registy > "Resume" value, or else the hotfix will fail to install...
> I had this issue on one of the servers of the company that I work for, and > it is a SharePoint server. I resolved it using the points described above.
> > > > The above update has failed; does anyone know either how to resolve > > > > this issue or disable the update requirement
> > > Is the SQL Server service actually running?
> > > The update will fail if it's not, with something like this in the System > > > event log:
> > > Windows Update Agent Event_ID 20
> > > Installation Failure: Windows failed to install the following update > > > with error 0x80070643: Security Update for SQL Server 2005 Service Pack > > > 3 (KB970892).
> > > -- > > > Bert Hyman St. Paul, MN b...@iphouse.com > > > . > > > Interesting note - I'm getting the same thing without any error indicated, just "not installed." Watching the system as the update is being "installed", SQL Server 2005 starts out activated. At some point during the process however, it shuts down. A few seconds later, the window then indicates it was not installed. I'm running WinXP Pro as well.
I'm having the same problem with Vista Bus SP1. I read where, and I had just done it, that it wouldn't install to a compressed directory. I expanded it back - still no joy. -- Jim Szatkowski, PE, NSPE State of Idaho, IPELS
I copied this from another discussion group and it worked on my computer, I am running XP
Hi there,
To resolve this issue, do the following:
1. Go to Run, type regedit, and click ok, or press Enter. 2. Back up your registry, if you don't know how to do this, google it... 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup] [Note that if you have multiple instances of MSSQL installed, the reg key might be different for you] 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. 5. install the update, and restart the machine.
If you don't want to install this update using the automatic update (WUAUCLT), you can download the hotfix directly from microsoft, just google "download KB970892 ". you will still need to manually change the registy "Resume" value, or else the hotfix will fail to install...
I copied this from another discussion group and it worked on my computer. I am running XP Professional.
To resolve this issue, do the following:
1. Go to Run, type regedit, and click ok, or press Enter. 2. Back up your registry, if you don't know how to do this, google it... 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup] [Note that if you have multiple instances of MSSQL installed, the reg key might be different for you] 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. 5. install the update, and restart the machine.
If you don't want to install this update using the automatic update (WUAUCLT), you can download the hotfix directly from microsoft, just google "download KB970892 ". you will still need to manually change the registy "Resume" value, or else the hotfix will fail to install.
Best of luck!
P.S. This is a lot faster and easier than calling Microsoft Customer Support. Trust me, I tried. Three times.
sido wrote:
Security Update for SQL Server 2005 Service Pack 3 (KB970892) 16-Oct-09
Unable to update - error code 0x737D Any ideas how to fix? -- cairngorm
I copied this from another discussion group and it worked on my computer. I am running XP Professional.
To resolve this issue, do the following:
1. Go to Run, type regedit, and click ok, or press Enter. 2. Back up your registry, if you don't know how to do this, google it... 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup] [Note that if you have multiple instances of MSSQL installed, the reg key might be different for you] 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. 5. install the update, and restart the machine.
If you don't want to install this update using the automatic update (WUAUCLT), you can download the hotfix directly from microsoft, just google "download KB970892 ". you will still need to manually change the registy "Resume" value, or else the hotfix will fail to install.
Best of luck!
P.S. This is a lot faster and easier than calling Microsoft Customer Support. Trust me, I tried. Three times.
eagle231 wrote: "dtunstallnc" wrote:Same thing here with error code 0x7358, running XP Pro.
16-Oct-09
"dtunstallnc" wrote:
Same thing here with error code 0x7358, running XP Pro. Has anyone heard about this issue?
> donphx wrote: > > Hello - I am new and I am having a problem downloading Security Update > > for SQL Server 2005 Service Pack 3 (KB970892) HELP!!!- Zitierten Text ausblenden -
> I copied this from another discussion group and it worked on my computer. I > am running XP Professional.
> To resolve this issue, do the following:
> 1. Go to Run, type regedit, and click ok, or press Enter. > 2. Back up your registry, if you don't know how to do this, google it... > 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL > Server\MSSQL.1\Setup] > [Note that if you have multiple instances of MSSQL installed, the reg key > might be different for you] > 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. > 5. install the update, and restart the machine.
> If you don't want to install this update using the automatic update > (WUAUCLT), you can download the hotfix directly from microsoft, just google > "download KB970892 ". you will still need to manually change the registy > "Resume" value, or else the hotfix will fail to install.
> Best of luck!
> P.S. This is a lot faster and easier than calling Microsoft Customer Support. Trust me, I tried. Three times.
> eagle231 wrote:
> "dtunstallnc" wrote:Same thing here with error code 0x7358, running XP Pro. > 16-Oct-09
> "dtunstallnc" wrote:
> Same thing here with error code 0x7358, running XP Pro. Has anyone heard > about this issue?
> 1. Go to Run, type regedit, and click ok, or press Enter. > 2. Back up your registry, if you don't know how to do this, google > it... > 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft > SQL > Server\MSSQL.1\Setup] > [Note that if you have multiple instances of MSSQL installed, the reg > key > might be different for you] > 4. find the Resume REG_DWORD, and change its decimal value from 1, to > 0. > 5. install the update, and restart the machine.
> If you don't want to install this update using the automatic update > (WUAUCLT), you can download the hotfix directly from microsoft, just > google > "download KB970892 ". you will still need to manually change the > registy > "Resume" value, or else the hotfix will fail to install...
Thanks!!!!
This solved it for me. Now maybe my Business Contact Manager will stay up.
> My regedit was already set like this. So, now what? > -- > Steph
> "Nicholas DiDonna" wrote: > > Hey all,
> > I copied this from another discussion group and it worked on my computer. I > > am running XP Professional.
> > To resolve this issue, do the following:
> > 1. Go to Run, type regedit, and click ok, or press Enter. > > 2. Back up your registry, if you don't know how to do this, google it... > > 3. In Regedit, go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL > > Server\MSSQL.1\Setup] > > [Note that if you have multiple instances of MSSQL installed, the reg key > > might be different for you] > > 4. find the Resume REG_DWORD, and change its decimal value from 1, to 0. > > 5. install the update, and restart the machine.
> > If you don't want to install this update using the automatic update > > (WUAUCLT), you can download the hotfix directly from microsoft, just google > > "download KB970892 ". you will still need to manually change the registy > > "Resume" value, or else the hotfix will fail to install.
> > Best of luck!
> > P.S. This is a lot faster and easier than calling Microsoft Customer Support. Trust me, I tried. Three times.
> > eagle231 wrote:
> > "dtunstallnc" wrote:Same thing here with error code 0x7358, running XP Pro. > > 16-Oct-09
> > "dtunstallnc" wrote:
> > Same thing here with error code 0x7358, running XP Pro. Has anyone heard > > about this issue?
Exactly same with me, I;d had that number set to 0, so that is not issue which would apply to everyone. I downloaded patch from mic. website but still won't work. I have tried the one, where you go to remove programs, SQL server 2005 Change and try to install it from here, but it was asking me to locate patch. So I located patch downloaded from web BUT it only accepts msi files, and Microsoft patch is named as msp. I think this is the issue, but I don't know how to resolve it. I've tried almost all options available while searching net but unsuccessful. I am so fed up with microsoft. This issue is messing with my Eset smart security, with my printer, and every time i swith my pc on it takes ages cause of these silly attempts to install it. Please don't tell me there's no proffesionals to help us here and solve this issue. I am not talking about 10 ppl I am talking about milions with same problem. Will Microsoft do something about it, or they just don't care as usually???? IT MASTERS WHERE ARE YOU? HEEEELP!!!!
Same problem here, my regedit was already set to 0. I am afraid there are no IT professionals to help us here. This regedit thing doesn't apply to everyone, so thanks for you participation and help but that's not the issue.
I had the same problem for weeks. It would runs for a bit and then report it could not install. This was a pain because it would stop my BackupExec and not restart it. So some of my backups that run passed 4 am would be stopped in their tracks. I tried all the suggestions on the web, from uninstalling to reinstalling, but nothing worked until I finally figured out that my problem was a missing local group. If you look at the hotfix install log, summary.txt (which I found in C: \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\) you can see why the install failed. As you can see below mine was do to a missing local group.
Error Number : 29512 Error Description : MSP Error: 29512 SQL Server Setup was unable add user NT AUTHORITY\SYSTEM to local group CNTV \SQLServer2005MSSQLUser$MYCOMPUTER$BKUPEXEC.
I searched this error in google and found a posting that suggested the problem was that a previous install had removed the group and now when this hotfix tries to add the user to the missing local group the install fails. The solution is to convince the installer to recreate the groups. This is accomplished by deleting some registry keys. If you want to read the posting it is at this page http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/c7d0a..., but I will summarize below.
- Run the regedit.exe program. - Back up your registry (use File -> Export and choose to export All) - Find any of the keys listed below and delete them. Don't worry if you do not have all the keys, I only had 2 of them.
- Once I deleted the keys, I downloaded the hot fix instead of running the Windows Update (http://download.microsoft.com/download/B/E/0/ BE0F87BC-37A4-4AB7-84C1-0E1A46F5463B/SQLServer2005-KB970892-x86- ENU.exe). - Last, I ran the hotfix and to my surprise it completed.
I hope this helps anyone in this group who has suffered with this annoying hotfix.
"Jason Martinez" <m...@jasonmartinez.com> wrote in message news:677d7846-0f11-42e1-be7a-e93dcb823b8a@x6g2000prc.googlegroups.com... >I had the same problem for weeks. It would runs for a bit and then > report it could not install. This was a pain because it would stop my > BackupExec and not restart it. So some of my backups that run passed 4 > am would be stopped in their tracks. I tried all the suggestions on > the web, from uninstalling to reinstalling, but nothing worked until I > finally figured out that my problem was a missing local group. If you > look at the hotfix install log, summary.txt (which I found in C: > \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\) > you can see why the install failed. As you can see below mine was do > to a missing local group.
> Error Number : 29512 > Error Description : MSP Error: 29512 SQL Server Setup was > unable add user NT AUTHORITY\SYSTEM to local group CNTV > \SQLServer2005MSSQLUser$MYCOMPUTER$BKUPEXEC.
> I searched this error in google and found a posting that suggested the > problem was that a previous install had removed the group and now when > this hotfix tries to add the user to the missing local group the > install fails. The solution is to convince the installer to recreate > the groups. This is accomplished by deleting some registry keys. If > you want to read the posting it is at this page > http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/c7d0a..., > but I will summarize below.
> - Run the regedit.exe program. > - Back up your registry (use File -> Export and choose to export All) > - Find any of the keys listed below and delete them. Don't worry if > you do not have all the keys, I only had 2 of them.
> - Once I deleted the keys, I downloaded the hot fix instead of running > the Windows Update (http://download.microsoft.com/download/B/E/0/ > BE0F87BC-37A4-4AB7-84C1-0E1A46F5463B/SQLServer2005-KB970892-x86- > ENU.exe). > - Last, I ran the hotfix and to my surprise it completed.
> I hope this helps anyone in this group who has suffered with this > annoying hotfix.
Thanks for sharing the resolution. Cross-post added to SQL Setup for its info.
Thanks in advance. I have read over the posts and nothing here seems to be what my log shows.
2009-11-14 13:49:53.26 spid11s The Service Broker protocol transport is disabled or not configured. 2009-11-14 13:49:53.26 spid11s The Database Mirroring protocol transport is disabled or not configured. 2009-11-14 13:49:53.32 spid11s Service Broker manager has started. 2009-11-14 14:20:07.59 Server Server resumed execution after being idle 1782 seconds: user activity awakened the server. This is an informational message only. No user action is required. 2009-11-14 14:20:08.10 spid11s Service Broker manager has shut down. 2009-11-14 14:20:08.32 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 2009-11-14 14:20:08.32 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I begin having the problem at "Sevice Broker" manager.
I don't even believe I need this update but I don't want to miss anything for future adjustments.
|
