SP2 + v5 activex + SUS 2 = WU dead

Ever since the second v5 activex was relased I am no longer able to download
from WU site. We use SUS 2 internally. SUS does work right anymore either.

SUS downloads to the client but never installs, just gives the AU icon in
the system tray.

WU makes it all the way to the start download page. When we click Install we
get Error number: 0x8007045A. Googling the error produces things that have
nothing to dow tih this scenario. The update log indicates it is trying to
start the SUS client to initiate the new download dialog. This of course does
not work because SUS control has no idea what the new dialog is. I have
reproduced this a dozen times, 100% of the time.

The v4 site does not show any Post SP2 updates anymore, so I can't use that
as a work around, though it was previously usable.

Does anyone know if MS is addressing this or of any work-around, reg hack,
etc? The Dell engineers I've worked with on other matters have also
reproduced this, so there is clearly a major problem here.

Hi

Have you looked at the section 'Possible fix for 0x8007045A problem'?

The solution is to change the default web page on your client machine
browsers to anything other than the SBS 2003 server companyweb; e.g.
microsoft.com.

The section mentioned above explains why.

Yours sincerely

Tony Vaughan

"Dan B" wrote:

> Ever since the second v5 activex was relased I am no longer able to download
> from WU site. We use SUS 2 internally. SUS does work right anymore either.
>
> SUS downloads to the client but never installs, just gives the AU icon in
> the system tray.
>
> WU makes it all the way to the start download page. When we click Install we
> get Error number: 0x8007045A. Googling the error produces things that have
> nothing to dow tih this scenario. The update log indicates it is trying to
> start the SUS client to initiate the new download dialog. This of course does
> not work because SUS control has no idea what the new dialog is. I have
> reproduced this a dozen times, 100% of the time.
>
> The v4 site does not show any Post SP2 updates anymore, so I can't use that
> as a work around, though it was previously usable.
>
> Does anyone know if MS is addressing this or of any work-around, reg hack,
> etc? The Dell engineers I've worked with on other matters have also
> reproduced this, so there is clearly a major problem here.

Hello.

Actually, it is not SBS, it is Sharepoint 2003 that is the problem. Yes,
already tried that and that fixes it using a web browser for WU, however it
does not fix the SUS 2 problem. Not a very attractive solution for Enterprise
customers who use SPS technology for Intranet purposes.

SUS never loads any controls from SharePoint, but definitely stops auto
installing updates. Still downloads them, just does not auto-install as GPO
tells it to anymore.

Although the 2 may be related from what I am seeing. It looks like MS did
not test the newest v5 control with some of their most common earlier
controls, like SPS2003 and SUS 2. I have not tested SPS2003 SP1 yet on this,
so I don't know if that fixes it for the Web problem.

I know they are trying to make one big happy client control now, but it
would have been a lot better for enterprise customers if they released
updates for earlier systems (SPS, SUS) or insured backward compatibility.
This was handled very sloppy by them, they usually do better.

"Tony Vaughan" wrote:

> Hi
>
> Have you looked at the section 'Possible fix for 0x8007045A problem'?
>
> The solution is to change the default web page on your client machine
> browsers to anything other than the SBS 2003 server companyweb; e.g.
> microsoft.com.

Hi Dan

Yes, I was aware that the browser fix is actually related to SharePoint,
which is used by SBS 2003, but I find it laborious to keep having to explain
the cause, feeling that the solution for most people is so simple to
implement. I have the latest update releases for SBS 2003 and the problem
hasn't been fixed yet. I nearly started to use SUS before it was discovered
that riched20.dll was being corrupted on client machines by sharepoint
derived software like companyweb, so I haven't hit your problem.

I absolutely agree with you about Microsoft's approach to this problem,
which has been cavalier to say the least. As you say, Microsoft have make
great efforts to avoid this sort of thing recently. My guess is that they
have neem swamped with SP2 issues and haven't given adequate resources to
fixing this.

Good luck.

Yours sincerely

Tony Vaughan

"Dan B" wrote:

> Hello.
>
> Actually, it is not SBS, it is Sharepoint 2003 that is the problem. Yes,
> already tried that and that fixes it using a web browser for WU, however it
> does not fix the SUS 2 problem. Not a very attractive solution for Enterprise
> customers who use SPS technology for Intranet purposes.
>
> SUS never loads any controls from SharePoint, but definitely stops auto
> installing updates. Still downloads them, just does not auto-install as GPO
> tells it to anymore.
>
> Although the 2 may be related from what I am seeing. It looks like MS did
> not test the newest v5 control with some of their most common earlier
> controls, like SPS2003 and SUS 2. I have not tested SPS2003 SP1 yet on this,
> so I don't know if that fixes it for the Web problem.
>
> I know they are trying to make one big happy client control now, but it
> would have been a lot better for enterprise customers if they released
> updates for earlier systems (SPS, SUS) or insured backward compatibility.
> This was handled very sloppy by them, they usually do better.
>
> "Tony Vaughan" wrote:
>
> > Hi
> >
> > Have you looked at the section 'Possible fix for 0x8007045A problem'?
> >
> > The solution is to change the default web page on your client machine
> > browsers to anything other than the SBS 2003 server companyweb; e.g.
> > microsoft.com.
>

We were early adopters for both SUS2 and SPS2003. They worked fine together
in our environment, never had the riched problem. In fact, the first v5
control released when the new WU site first went public also worked fine with
both. It was the second control about 9 days after going public with the v5
WU that started all the problems.

MS are you reading the timeline here? Perhaps a clue on what the coders
missed?

"Tony Vaughan" wrote:

> Hi Dan
>
> Yes, I was aware that the browser fix is actually related to SharePoint,
> which is used by SBS 2003, but I find it laborious to keep having to explain
> the cause, feeling that the solution for most people is so simple to
> implement. I have the latest update releases for SBS 2003 and the problem
> hasn't been fixed yet. I nearly started to use SUS before it was discovered
> that riched20.dll was being corrupted on client machines by sharepoint
> derived software like companyweb, so I haven't hit your problem.