|
|
In January I found one of our workstations thrashing CPU time with svchost.
After searching the web, I concluded that quick fix was to take it out of
scope of GPO implementing WSUS on clients. Sure enough it has not reported
status to the server since January.
That did fix the problem - until today.
I have been updating the workstation weekly direct from Microsoft Update.
When I tried that this morning, the thrashing started while checking for
needed updates.
What is the recommended fix?
Searching for svchost in this newsgroup returns three (only) threads of zero
relevance. Is there a fix for this too?
--
Newell White
|
|
|
|
Thanks for quick response Winfried.
Have installed the agent on the suspect machine, but it will be some time
before I am confident that problem is gone.
--
Newell White
"Winfried Sonntag [MVP]" wrote:
[Quoted Text]
|
|
FWIW, my understanding is that in addition to the agent, you also need
KB927891.
"Newell White" <NewellWhite[ at ]discussions.microsoft.com> wrote in message
news:51E92C42-6012-4624-9B92-05FFD44E9BAD[ at ]microsoft.com...
[Quoted Text]
|
|
Thanks Dave, will apply that too.
--
Newell White
"Dave Nickason [SBS MVP]" wrote:
[Quoted Text]
|
|
"Newell White" <NewellWhite[ at ]discussions.microsoft.com> wrote in message
news:EC273AE2-0FD4-4E56-BB66-775624F46812[ at ]microsoft.com...
[Quoted Text] > In January I found one of our workstations thrashing CPU time with
> svchost.
> After searching the web, I concluded that quick fix was to take it out of
> scope of GPO implementing WSUS on clients. Sure enough it has not reported
> status to the server since January.
No great surprise, there. :)
> That did fix the problem - until today.
Inasmuch as these issues are *not* =WSUS= issues, but =WUA= issues,
reassigning a client from a WSUS Server back to AU, is not likely to have
any appreciable improvement on the situation.
> I have been updating the workstation weekly direct from Microsoft Update.
> When I tried that this morning, the thrashing started while checking for
> needed updates.
Yep.
> What is the recommended fix?
[a] Install the hotfix.
[b] Upgrade the WUA to 7.0 (which should have already happened as a result
of your use of MU).
> Searching for svchost in this newsgroup returns three (only) threads of
> zero
> relevance. Is there a fix for this too?
You've got to be kidding me!
Any search for svchost in this newsgroup ought to return about three or four
dozen threads!
Albeit, only a few actually have the *correct* answer posted to them,
otherwise I'd be posting it hourly.
Consider this to be the /fourth/ thread with the correct answer. :-)
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
I kid you not - why don't you try it? Use browser, we don't use Outlook
Express here.
--
Newell White
"Lawrence Garvin (MVP)" wrote:
[Quoted Text]
|
|
|
|
Are you kidding me? This link returns 9 references, 1 in English (2004), 8 in
Spanish.
I was naively using the search tool provided by MS on the Discussions in
WSUS page. Maybe it is constructed to suppress bad news about Windows!
--
Newell White
"Lawrence Garvin (MVP)" wrote:
[Quoted Text]
|
|
Hi Newell - Even if you're not still having problems, this would be a good
idea:
- First, you will need to install or re-install the updated KB927891, here:
http://support.microsoft.com/?kbid=927891 for a complete fix.
- Then install the newly released 'standalone' version of Windows Update
Agent 3.0, v. 7.0.6000.374, for 32 bit machines which is available here:
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe
It may say "Install is not needed since Windows Update Agent is
already installed." If so, then run the exe with the command line switch
/wuforce , like this:
WindowsUpdateAgent30-x86.exe /wuforce
to force the install.
- For those using Windows Servers - Courtesy of Bobby Harter, Program
Manager, WSUS, Microsoft, WSUS 3.0 was released on April 30th and is
avaialble now on the Microsoft Download Center. Full information,
documentation, samples and links to the bits can be found here:
http://www.microsoft.com/wsus. WSUS 3.0 RC will be supported until May 31st
2007 - WSUS 3.0 supports upgrade of WSUS 2.0 SP1 and WSUS 3.0 RC.
- One MS recommended procedure is:
"1. Install the Windows Update Agent (WUA) for all the client computers
(both WSUS client and stand alone workstation)
2. Install the Update for Windows XP (KB927891) for all the client
computers (both WSUS client and stand alone workstation)
3. Upgrade the WSUS Server to version 3.0"
However, I've also seen a posting by MS which states that once the WSUS
client has been updated with the new Agent and KB927891 and then upgraded to
WSUS 3.0, it will then handle updating the others.
- The MS WSUS team believes that this solves all three 'svchost' problems
that folks have been experiencing. See here:
http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx
- Note that you may _still_ see high svchost usage, but with these new
components the machine should, however, remain responsive:
From a posting by Sudheer GN of Microsoft -
"Hi,
The biggest difference in WSUS 3.0 client (wrt performance) is that the
machines will still be responsive when WU client scans for updates. There
are also some optimization to reduce the number of update evaluations and
that will reduce the scan time in some scenarios.
It is still expected that CPU usage will be high so that the scan can
complete in lesser amount of time. But other applications can be launched
and used (they will still be a little sluggish because CPU is being shared
with WU client)
--
Sudheer GN
Microsoft, WU Client
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
Lastly, there appears to be some good evidence that scanning of certain
Update-related files by your AV can cause this issue as well. See:
http://support.microsoft.com/kb/822158 for a list of files which should be
excluded from real-time scanning.
--
Regards, Jim Byrd,
My Blog, Defending Your Machine,
http://defendingyourmachine2.blogspot.com/
In news:B56DB600-E524-4F1B-9384-F0F85A07DD24[ at ]microsoft.com,
Newell White <NewellWhite[ at ]discussions.microsoft.com> typed:
|| Are you kidding me? This link returns 9 references, 1 in English
|| (2004), 8 in Spanish.
||
|| I was naively using the search tool provided by MS on the
|| Discussions in WSUS page. Maybe it is constructed to suppress bad
|| news about Windows! --
|| Newell White
||
||
|| "Lawrence Garvin (MVP)" wrote:
||
|||
|||
http://news.google.com/archivesearch?q=wsus+svchost.exe+&ie=UTF-8&oe=UTF-8&btnG=Search+Archives
|||
||| --
||| Lawrence Garvin, M.S., MCTS, MCP
||| Independent WSUS Evangelist
||| MVP-Software Distribution (2005-2007)
|||
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
|||
||| Everything you need for WSUS is at
|||
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
|||
||| And, almost everything else is at
||| http://wsusinfo.onsitechsolutions.com
||| .....
|
|
|
|
Thanks Jim.
Check of workstations in our manufacturing area, and discussions with users
shows incidence of the problem has risen from 3% to 10% of XP workstations in
6 months.
So I have installed both Agent 3.0 and KB927891 on all workstations.
Of course I can't be confident for months yet whether problem has been
killed - but it doesn't hurt that I have been seen doing something to help
these people, who are fairly naive users.
--
Newell White
"Jim Byrd" wrote:
[Quoted Text] > Hi Newell - Even if you're not still having problems, this would be a good > idea: > > > - First, you will need to install or re-install the updated KB927891, here: > http://support.microsoft.com/?kbid=927891 for a complete fix. > > - Then install the newly released 'standalone' version of Windows Update > Agent 3.0, v. 7.0.6000.374, for 32 bit machines which is available here: > http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe> > It may say "Install is not needed since Windows Update Agent is > already installed." If so, then run the exe with the command line switch > /wuforce , like this: > > WindowsUpdateAgent30-x86.exe /wuforce > > to force the install. > > > > - For those using Windows Servers - Courtesy of Bobby Harter, Program > Manager, WSUS, Microsoft, WSUS 3.0 was released on April 30th and is > avaialble now on the Microsoft Download Center. Full information, > documentation, samples and links to the bits can be found here: > http://www.microsoft.com/wsus. WSUS 3.0 RC will be supported until May 31st > 2007 - WSUS 3.0 supports upgrade of WSUS 2.0 SP1 and WSUS 3.0 RC. > > > - One MS recommended procedure is: > > "1. Install the Windows Update Agent (WUA) for all the client computers > (both WSUS client and stand alone workstation) > 2. Install the Update for Windows XP (KB927891) for all the client > computers (both WSUS client and stand alone workstation) > 3. Upgrade the WSUS Server to version 3.0" > > However, I've also seen a posting by MS which states that once the WSUS > client has been updated with the new Agent and KB927891 and then upgraded to > WSUS 3.0, it will then handle updating the others. > > > - The MS WSUS team believes that this solves all three 'svchost' problems > that folks have been experiencing. See here: > http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx> > > - Note that you may _still_ see high svchost usage, but with these new > components the machine should, however, remain responsive: > > From a posting by Sudheer GN of Microsoft - > > "Hi, > The biggest difference in WSUS 3.0 client (wrt performance) is that the > machines will still be responsive when WU client scans for updates. There > are also some optimization to reduce the number of update evaluations and > that will reduce the scan time in some scenarios. > It is still expected that CPU usage will be high so that the scan can > complete in lesser amount of time. But other applications can be launched > and used (they will still be a little sluggish because CPU is being shared > with WU client) > > -- > Sudheer GN > Microsoft, WU Client > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm"> > > Lastly, there appears to be some good evidence that scanning of certain > Update-related files by your AV can cause this issue as well. See: > http://support.microsoft.com/kb/822158 for a list of files which should be > excluded from real-time scanning. > > > -- > Regards, Jim Byrd, > My Blog, Defending Your Machine, > http://defendingyourmachine2.blogspot.com/> > > > In news:B56DB600-E524-4F1B-9384-F0F85A07DD24[ at ]microsoft.com, > Newell White <NewellWhite[ at ]discussions.microsoft.com> typed: > || Are you kidding me? This link returns 9 references, 1 in English > || (2004), 8 in Spanish. > || > || I was naively using the search tool provided by MS on the > || Discussions in WSUS page. Maybe it is constructed to suppress bad > || news about Windows! -- > || Newell White > || > || > || "Lawrence Garvin (MVP)" wrote: > || > ||| > ||| > http://news.google.com/archivesearch?q=wsus+svchost.exe+&ie=UTF-8&oe=UTF-8&btnG=Search+Archives> ||| > ||| -- > ||| Lawrence Garvin, M.S., MCTS, MCP > ||| Independent WSUS Evangelist > ||| MVP-Software Distribution (2005-2007) > ||| > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> ||| > ||| Everything you need for WSUS is at > ||| > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> ||| > ||| And, almost everything else is at > ||| http://wsusinfo.onsitechsolutions.com> ||| ..... > > > |
|
Thanks Lawrence - I have used ask.com to research the problem and fixes.
I raised it in the group to get authoritative answer.
My recent beef is that Microsoft should make the search bar on this page
work effectively, or remove it.
Such persistent poor performance would not generally be tolerated in a human
employee!
--
Newell White
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > Try these, also... I got confused on the last link and was searching "News" > instead of "Groups"... > > http://groups.google.com/groups?ie=UTF-8&oe=UTF-8&q=wsus%20svchost.exe%20&sa=N&tab=ng> > > http://groups.google.com/groups?as_q=svchost+exe&num=10&scoring=r&as_epq=&as_oq=&as_eq=&as_ugroup=microsoft.public.windows.server.update_services&as_usubject=&as_uauthors=&lr=&as_drrb=q&as_qdr=&as_mind=1&as_minm=1&as_miny=1981&as_maxd=21&as_maxm=5&as_maxy=2007&safe=off> > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> ..... > > > "Newell White" <NewellWhite[ at ]discussions.microsoft.com> wrote in message > news:B56DB600-E524-4F1B-9384-F0F85A07DD24[ at ]microsoft.com... > > Are you kidding me? This link returns 9 references, 1 in English (2004), 8 > > in > > Spanish. > > > > I was naively using the search tool provided by MS on the Discussions in > > WSUS page. Maybe it is constructed to suppress bad news about Windows! > > -- > > Newell White > > > > > > "Lawrence Garvin (MVP)" wrote: > > > >> > >> http://news.google.com/archivesearch?q=wsus+svchost.exe+&ie=UTF-8&oe=UTF-8&btnG=Search+Archives> >> > >> -- > >> Lawrence Garvin, M.S., MCTS, MCP > >> Independent WSUS Evangelist > >> MVP-Software Distribution (2005-2007) > >> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> >> > >> Everything you need for WSUS is at > >> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> >> > >> And, almost everything else is at > >> http://wsusinfo.onsitechsolutions.com> >> ..... > >> > >> > >> > > > |
|
How did you update all workstations? Does/will WSUS provide KB927891? I
know that Agent 3.0 *IS* being provide, but what about the patch?
Regards,
Hank Arnold
Newell White wrote:
[Quoted Text] > Thanks Jim.
>
> Check of workstations in our manufacturing area, and discussions with users
> shows incidence of the problem has risen from 3% to 10% of XP workstations in
> 6 months.
>
> So I have installed both Agent 3.0 and KB927891 on all workstations.
> Of course I can't be confident for months yet whether problem has been
> killed - but it doesn't hurt that I have been seen doing something to help
> these people, who are fairly naive users.
|
|
Sorry Hank,
No magic technical fix.
Our manufacturing team and half the office staff get Friday p.m. off unless
overtime is required.
So on a smallish network like ours it was fast footwork and nimble fingers!
It is great for a sysadmin to have a few hours to sit at the workstations
and check how well things are working at the sharp end.
--
Newell White
"Hank Arnold" wrote:
[Quoted Text] > How did you update all workstations? Does/will WSUS provide KB927891? I
> know that Agent 3.0 *IS* being provide, but what about the patch?
>
> Regards,
> Hank Arnold
>
> Newell White wrote:
> > Thanks Jim.
> >
> > Check of workstations in our manufacturing area, and discussions with users
> > shows incidence of the problem has risen from 3% to 10% of XP workstations in
> > 6 months.
> >
> > So I have installed both Agent 3.0 and KB927891 on all workstations.
> > Of course I can't be confident for months yet whether problem has been
> > killed - but it doesn't hurt that I have been seen doing something to help
> > these people, who are fairly naive users.
>
|
|
Hi Newell - First, YW. :) Secondly, in a few case to my knowledge
the lockup has returned. It's thought that this is probably due to a
recurrance of corruption of the DataStore.edb and/or the log files in the
%windir%\SoftwareDistribution\DataStore
folder probably caused by interference by an AV scan during the Update
checks. If this does occur for any of your machines, you might wish to try
the following work arounds to the particular machine to get things back to
normal.
1. Defrag the DataStore.edb file using the following command line:
esentutl /d %windir%\SoftwareDistribution\Datastore\datastore.edb
2. If that doesn't do it, then try a Recovery of it:
esentutl /r %windir%\SoftwareDistribution\Datastore\datastore.edb
(Hopefully this will get all databases to a
consistent state)
3. If that doesn't help, then try a Repair:
esentutl /p %windir%\SoftwareDistribution\Datastore\datastore.edb
If those steps don't solve it, you can try the following procedure which I
worked out with some MS personnel which so far has worked when used:
The following assumes you're on Windows XP but will work OK for Win2k as
well. If you're confident about what you're doing, then try the following
first - only if it doesn't work, then there's another level of stuff that
can be done following:
1. Stop and Disable Automatic Updates, Background Intelligent Transfer
Service and the Cryptographic Service.
2. Rename the folder %SystemRoot%\SoftwareDistribution to
%SystemRoot%\OldSoftwareDistribution
3. Open Notepad and create a file containing the following:
REGSVR32 WUAPI.DLL
REGSVR32 WUAUENG.DLL
REGSVR32 WUAUENG1.DLL
REGSVR32 ATL.DLL
REGSVR32 WUCLTUI.DLL
REGSVR32 WUPS.DLL
REGSVR32 WUPS2.DLL
REGSVR32 WUWEB.DLL
Save this file as 'Wudll.cmd' (without the quotes) to any convenient
location then exit Notepad and double click on the file you just saved. You
should get a 'Sucess' mesage for each of the .dll's listed above.
4. Now Re-enable to Automatic status and then Start each of the services
you stopped before - Automatic Updates, Background Intelligent Transfer
Service and the Cryptographic Service.
5. Now Reboot. Now Reboot Again. (Yes, twice.)
See if that solves it - give it a couple of days. If so, then you can
delete 'OldSoftwareDistribution'. I would request that you post back with
your results. _Only if the problem does re-occur_, then do the following
_exactly_:
1. Go to http://wiki.djlizard.net/Dial-a-fix and download Dial-a-fix
v0.60.0.24 (2006-10-27) Here's a direct download link:
http://djlizard.net.nyud.net:8080/software/Dial-a-fix-v0.60.0.24.zip and a
secondary: http://djlizard.net/software/Dial-a-fix-v0.60.0.24.zip from
that page's download section, here:
http://wiki.djlizard.net/Dial-a-fix#Mirrors.2Fdownload_locations.2C_and_articles .
2. Unzip it to a new folder at root with any name, e.g.
c:\Dial-a-fix-v0.60.0.24
3. Double click on Dial-a-fix.exe in that folder.
4. Click on the following:
- Options/tooltips (just to get an idea of what it does in each
section.
:) )
- Both boxes under Prep
- The 'all' (top) box for Sections 2, 3 and 4 (which will automatically
be set when you check 3)
- In Section 3 click on 'Flush Software Distribution' and choose 'Yes'
to force the deletion of the folder.
- In Section 5, 'Programming cores/runtimes',
'Explorer/IE/OE/shell/WMP', and 'Object linking libraries (OLE)' only.
- Click 'Go' . (Some of the re-registrations may take what seems like
a
long time for some .dll's - Don't be impatient.)
5. Reboot. Now Reboot Again. (Yes, twice.)
See if that does the trick, and, again please post back with your
experience.
--
Regards, Jim Byrd,
My Blog, Defending Your Machine,
http://defendingyourmachine2.blogspot.com/
In news:98C78687-307E-482B-8217-9FF1E71623B1[ at ]microsoft.com,
Newell White <NewellWhite[ at ]discussions.microsoft.com> typed:
|| Thanks Jim.
||
|| Check of workstations in our manufacturing area, and discussions
|| with users shows incidence of the problem has risen from 3% to 10%
|| of XP workstations in 6 months.
||
|| So I have installed both Agent 3.0 and KB927891 on all workstations.
|| Of course I can't be confident for months yet whether problem has
|| been killed - but it doesn't hurt that I have been seen doing
|| something to help these people, who are fairly naive users.
|| --
|| Newell White
||
||
|| "Jim Byrd" wrote:
||
||| Hi Newell - Even if you're not still having problems, this would be
||| a good idea:
|||
|||
||| - First, you will need to install or re-install the updated
||| KB927891, here: http://support.microsoft.com/?kbid=927891 for a
||| complete fix.
|||
||| - Then install the newly released 'standalone' version of Windows
||| Update Agent 3.0, v. 7.0.6000.374, for 32 bit machines which is
||| available here:
|||
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe
|||
||| It may say "Install is not needed since Windows Update Agent is
||| already installed." If so, then run the exe with the command line
||| switch /wuforce , like this:
|||
||| WindowsUpdateAgent30-x86.exe /wuforce
|||
||| to force the install.
|||
|||
|||
||| - For those using Windows Servers - Courtesy of Bobby Harter,
||| Program Manager, WSUS, Microsoft, WSUS 3.0 was released on April
||| 30th and is avaialble now on the Microsoft Download Center. Full
||| information, documentation, samples and links to the bits can be
||| found here: http://www.microsoft.com/wsus. WSUS 3.0 RC will be
||| supported until May 31st 2007 - WSUS 3.0 supports upgrade of WSUS
||| 2.0 SP1 and WSUS 3.0 RC.
|||
|||
||| - One MS recommended procedure is:
|||
||| "1. Install the Windows Update Agent (WUA) for all the client
||| computers (both WSUS client and stand alone workstation)
||| 2. Install the Update for Windows XP (KB927891) for all the client
||| computers (both WSUS client and stand alone workstation)
||| 3. Upgrade the WSUS Server to version 3.0"
|||
||| However, I've also seen a posting by MS which states that once the
||| WSUS client has been updated with the new Agent and KB927891 and
||| then upgraded to WSUS 3.0, it will then handle updating the others.
|||
|||
||| - The MS WSUS team believes that this solves all three 'svchost'
||| problems that folks have been experiencing. See here:
||| http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx
|||
|||
||| - Note that you may _still_ see high svchost usage, but with these
||| new components the machine should, however, remain responsive:
|||
||| From a posting by Sudheer GN of Microsoft -
|||
||| "Hi,
||| The biggest difference in WSUS 3.0 client (wrt performance) is that
||| the machines will still be responsive when WU client scans for
||| updates. There are also some optimization to reduce the number of
||| update evaluations and that will reduce the scan time in some
||| scenarios.
||| It is still expected that CPU usage will be high so that the scan
||| can complete in lesser amount of time. But other applications can
||| be launched and used (they will still be a little sluggish because
||| CPU is being shared with WU client)
|||
||| --
||| Sudheer GN
||| Microsoft, WU Client
|||
||| This posting is provided "As Is" with no warranties, and confers no
||| rights. Use of included script samples are subject to the terms
||| specified at http://www.microsoft.com/info/cpyright.htm"
|||
|||
||| Lastly, there appears to be some good evidence that scanning of
||| certain Update-related files by your AV can cause this issue as
||| well. See: http://support.microsoft.com/kb/822158 for a list of
||| files which should be excluded from real-time scanning.
|||
|||
||| --
||| Regards, Jim Byrd,
||| My Blog, Defending Your Machine,
||| http://defendingyourmachine2.blogspot.com/
|||
|||
|||
||| In news:B56DB600-E524-4F1B-9384-F0F85A07DD24[ at ]microsoft.com,
||| Newell White <NewellWhite[ at ]discussions.microsoft.com> typed:
||||| Are you kidding me? This link returns 9 references, 1 in English
||||| (2004), 8 in Spanish.
|||||
||||| I was naively using the search tool provided by MS on the
||||| Discussions in WSUS page. Maybe it is constructed to suppress bad
||||| news about Windows! --
||||| Newell White
|||||
|||||
||||| "Lawrence Garvin (MVP)" wrote:
|||||
||||||
||||||
|||
http://news.google.com/archivesearch?q=wsus+svchost.exe+&ie=UTF-8&oe=UTF-8&btnG=Search+Archives
||||||
|||||| --
|||||| Lawrence Garvin, M.S., MCTS, MCP
|||||| Independent WSUS Evangelist
|||||| MVP-Software Distribution (2005-2007)
||||||
|||
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
||||||
|||||| Everything you need for WSUS is at
||||||
|||
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
||||||
|||||| And, almost everything else is at
|||||| http://wsusinfo.onsitechsolutions.com
|||||| .....
|
|
Thanks again, Jim, for this detailed Plan B.
Will let you know if I need it, and result.
Regards,
Newell White
"Jim Byrd" wrote:
[Quoted Text] > Hi Newell - First, YW. :) Secondly, in a few case to my knowledge > the lockup has returned. It's thought that this is probably due to a > recurrance of corruption of the DataStore.edb and/or the log files in the > %windir%\SoftwareDistribution\DataStore > folder probably caused by interference by an AV scan during the Update > checks. If this does occur for any of your machines, you might wish to try > the following work arounds to the particular machine to get things back to > normal. > > 1. Defrag the DataStore.edb file using the following command line: > > esentutl /d %windir%\SoftwareDistribution\Datastore\datastore.edb > > 2. If that doesn't do it, then try a Recovery of it: > > esentutl /r %windir%\SoftwareDistribution\Datastore\datastore.edb > > (Hopefully this will get all databases to a > consistent state) > > 3. If that doesn't help, then try a Repair: > > esentutl /p %windir%\SoftwareDistribution\Datastore\datastore.edb > > > > If those steps don't solve it, you can try the following procedure which I > worked out with some MS personnel which so far has worked when used: > > The following assumes you're on Windows XP but will work OK for Win2k as > well. If you're confident about what you're doing, then try the following > first - only if it doesn't work, then there's another level of stuff that > can be done following: > > 1. Stop and Disable Automatic Updates, Background Intelligent Transfer > Service and the Cryptographic Service. > > 2. Rename the folder %SystemRoot%\SoftwareDistribution to > %SystemRoot%\OldSoftwareDistribution > > 3. Open Notepad and create a file containing the following: > > REGSVR32 WUAPI.DLL > REGSVR32 WUAUENG.DLL > REGSVR32 WUAUENG1.DLL > REGSVR32 ATL.DLL > REGSVR32 WUCLTUI.DLL > REGSVR32 WUPS.DLL > REGSVR32 WUPS2.DLL > REGSVR32 WUWEB.DLL > > > Save this file as 'Wudll.cmd' (without the quotes) to any convenient > location then exit Notepad and double click on the file you just saved. You > should get a 'Sucess' mesage for each of the .dll's listed above. > > 4. Now Re-enable to Automatic status and then Start each of the services > you stopped before - Automatic Updates, Background Intelligent Transfer > Service and the Cryptographic Service. > > 5. Now Reboot. Now Reboot Again. (Yes, twice.) > > See if that solves it - give it a couple of days. If so, then you can > delete 'OldSoftwareDistribution'. I would request that you post back with > your results. _Only if the problem does re-occur_, then do the following > _exactly_: > > 1. Go to http://wiki.djlizard.net/Dial-a-fix and download Dial-a-fix > v0.60.0.24 (2006-10-27) Here's a direct download link: > http://djlizard.net.nyud.net:8080/software/Dial-a-fix-v0.60.0.24.zip and a > secondary: http://djlizard.net/software/Dial-a-fix-v0.60.0.24.zip from > that page's download section, here: > http://wiki.djlizard.net/Dial-a-fix#Mirrors.2Fdownload_locations.2C_and_articles . > > 2. Unzip it to a new folder at root with any name, e.g. > c:\Dial-a-fix-v0.60.0.24 > > 3. Double click on Dial-a-fix.exe in that folder. > > 4. Click on the following: > - Options/tooltips (just to get an idea of what it does in each > section. > :) ) > - Both boxes under Prep > - The 'all' (top) box for Sections 2, 3 and 4 (which will automatically > be set when you check 3) > - In Section 3 click on 'Flush Software Distribution' and choose 'Yes' > to force the deletion of the folder. > - In Section 5, 'Programming cores/runtimes', > 'Explorer/IE/OE/shell/WMP', and 'Object linking libraries (OLE)' only. > - Click 'Go' . (Some of the re-registrations may take what seems like > a > long time for some .dll's - Don't be impatient.) > > 5. Reboot. Now Reboot Again. (Yes, twice.) > > > See if that does the trick, and, again please post back with your > experience. > > > -- > Regards, Jim Byrd, > My Blog, Defending Your Machine, > http://defendingyourmachine2.blogspot.com/> > >
|
|
|