Re: New thread same issue - Monitoring and reporting kaput - Clues
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Mon, 4 Aug 2008 07:23:04 +1000
Yes, it is relatively normal for the cleanup task to take a long time, particularly if it hasn't been run for a while (or at all). You are likely to also see the MMC lose connection to WSUS at this time, simply take the 'Reset Server node' choice and run the wiz again.
The timing and loss of connection can be reduced by deselecting all but the first task, Unused Updates..., but even so you are likely to see the long processing time.
"David Hampson" <microsoft@xxxxxxxxxxxxx> wrote in message news:%2377ESgZ9IHA.5756@xxxxxxxxxxxxxxxxxxxxxxx
Woodie,
I started the cleanup wizard with just Delete Unused Updates selected. It's beeing going since Thursday night, and is halfway done. Not sure if it's supposed to take this long, but it is, and it's making progress. I'll post again when it's done to let everyone know if it worked or not.
HTH,
Dave H.
"Woodie" <Woodie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:DCC9E7B1-63BC-482D-BDB0-6A07147FC512@xxxxxxxxxxxxxxxxI'm running the cleanup agent but it seems hung on "deleting unused updates"
where it has been for several hours. The process is causing CPU and disk
activity so it isn't dead. Is this normal? I've not run the agent before and
WSUS has been running since January 2007. Many thanks.
"Jan" wrote:
Thanks for suggestion Les.
Running cleanup does seem to help. After cleanup WSUS status page displays
twice as fast on four servers I had problem with.
On my server it took two days and four restarts to complete but finally I
can get to monitoring page.
Let's see if it is lasting solution.
--
Jan Wakulicz
www.micropol.com.au
"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:%23HYjEJn8IHA.5596@xxxxxxxxxxxxxxxxxxxxxxx
> That's an ancient issue, which self corrected within a day.
>
> Try the cleanup wizard in WSUS console. It's corrected the monitoring
> report issue on 2 servers for me so far. Unfortunately I don't yet > know
> whether it's a lasting correction, but it looks promising. Running it > on 8
> more servers now.
>
> -- > Les Connor [SBS MVP]
> ________________________
> Get the SBS BPA here:
> http://support.microsoft.com/kb/940439/en-us
>
>
> "JamesS" <JamesS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:20436520-C915-4861-8567-35F02FDF8450@xxxxxxxxxxxxxxxx
>> Have you tried the following:
>> http://blogs.technet.com/sbs/archive/2007/11/12/wsus-2-0-and-3-0-errors-on-small-business-server.aspx
>> I was having the same issue when I came across this page.
>>
>> -- >> JamesS
>>
>>
>> "Chris" wrote:
>>
>>> False hope unfortunately as it has stopped working again now!!
>>>
>>>
>>> "Chris" wrote:
>>>
>>> > Rob,
>>> >
>>> > I had a reply to the original post I made which fixed the issue >>> > for
>>> > me. It
>>> > was to run a SQL query which defrags the SUSDB and re-indexes. I >>> > ran
>>> > the
>>> > Performance report (it failed), then the SQL defrag, then the
>>> > Performance
>>> > report again and it worked. We'll see if the automated email >>> > version
>>> > works
>>> > tomorrow, but no reason to suspect it won't.
>>> >
>>> > Regards
>>> >
>>> > Chris
>>> >
>>> >
>>> > "Rob C" wrote:
>>> >
>>> > > Hi folks,
>>> > >
>>> > > From the users of this newsgroup we have dentified 4x SBS >>> > > servers
>>> > > with exact
>>> > > same issues with monitoring and reporting having failed between >>> > > 14th
>>> > > and 15th
>>> > > of July. I think I am safe to report companyweb is working fine >>> > > so
>>> > > cannot be
>>> > > related to the KB948110 fix for companyweb although it could be
>>> > > related to
>>> > > the kb.
>>> > >
>>> > > Can any Microsoftites help us here?
>>> > >
>>> > > Previous thread-
>>> > > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&lang=&cr=&guid=&sloc=en-us&dg=microsoft.public.windows.server.sbs&p=1&tid=2fdc6bdc-065b-4f0e-9088-078f60492c27
>>> > >
>>> > > Rob C
>>> > >
>
.
- Follow-Ups:
- Re: New thread same issue - Monitoring and reporting kaput - Clues
- From: David Hampson
- Re: New thread same issue - Monitoring and reporting kaput - Clues
- References:
- Prev by Date: Re: suggestions on network storage
- Next by Date: Re: suggestions on network storage
- Previous by thread: Re: New thread same issue - Monitoring and reporting kaput - Clues
- Next by thread: Re: New thread same issue - Monitoring and reporting kaput - Clues
- Index(es):
Relevant Pages
|
