Possible fix for 0x8007045A problem

Daniel Chow has come up with a possible reason for this problem.

What I need you, out there, to do, is to try this out and let me know if it
works.

This message is directed to SBS 2003 users where the client IE has a default
setting of http://companyweb/default.aspx.

I simply ask that you reset the default page on your client workstations to
something else, like http://www.msn.co.uk/default.asp?Ath=f. Reboot to clear
everything.

Then try WU5.

Please let me know what happens.

Now, why do this. As I understand it, this is something to do with
riched20.dll and the fact that SBS 2003 now employs SharePoint. However, we
need your feadback to confirm this.

I look forward to hearing from you all.

Tony

Worked here! -- I have also not been able to have the clients download
automatically using Automatic Updates and SUS on the SBS server... The next
schedule update is tomorrow. I'll let you know if this fixes that as well.

Cheers,

Steve K.

"Tony Vaughan" <> wrote in message
news4B0A5DA-AAFB-4A1E-A48E-...
> Daniel Chow has come up with a possible reason for this problem.
>
> What I need you, out there, to do, is to try this out and let me know if
> it
> works.
>
> This message is directed to SBS 2003 users where the client IE has a
> default
> setting of http://companyweb/default.aspx.
>
> I simply ask that you reset the default page on your client workstations
> to
> something else, like http://www.msn.co.uk/default.asp?Ath=f. Reboot to
> clear
> everything.
>
> Then try WU5.
>
> Please let me know what happens.
>
> Now, why do this. As I understand it, this is something to do with
> riched20.dll and the fact that SBS 2003 now employs SharePoint. However,
> we
> need your feadback to confirm this.
>
> I look forward to hearing from you all.
>
> Tony

Hi Steve

Thanks for that.

Maybe we've got it.

Keep this topic informed, as will I.

Tony

"Steve Kemp" wrote:

> Worked here! -- I have also not been able to have the clients download
> automatically using Automatic Updates and SUS on the SBS server... The next
> schedule update is tomorrow. I'll let you know if this fixes that as well.
>
> Cheers,
>
> Steve K.
>
> "Tony Vaughan" <> wrote in message
> news4B0A5DA-AAFB-4A1E-A48E-...
> > Daniel Chow has come up with a possible reason for this problem.
> >
> > What I need you, out there, to do, is to try this out and let me know if
> > it
> > works.
> >
> > This message is directed to SBS 2003 users where the client IE has a
> > default
> > setting of http://companyweb/default.aspx.
> >
> > I simply ask that you reset the default page on your client workstations
> > to
> > something else, like http://www.msn.co.uk/default.asp?Ath=f. Reboot to
> > clear
> > everything.
> >
> > Then try WU5.
> >
> > Please let me know what happens.
> >
> > Now, why do this. As I understand it, this is something to do with
> > riched20.dll and the fact that SBS 2003 now employs SharePoint. However,
> > we
> > need your feadback to confirm this.
> >
> > I look forward to hearing from you all.
> >
> > Tony
>
>
>

I can confirm that this fix has corrected the problem on all of my WinXP SP2
clients that I have tested it on (and all were having the problem).

As for the Automatic update issue I mentioned.... if it is related I can no
longer difinitively confirm that this will fix it, I have made a number of
changes to the SUS service, including moving it to another server (off the
SBS server) which had room to download the patches locally. So if it if
fixed (waiting for next update interval) I can't say what was the cause of
the fix.

Anyway, nice job... this was an obscure fix.

Cheers,

Steve K.



"Tony Vaughan" <> wrote in message
news:B4573E77-B96A-40E4-AB30-...
> Hi Steve
>
> Thanks for that.
>
> Maybe we've got it.
>
> Keep this topic informed, as will I.
>
> Tony
>
> "Steve Kemp" wrote:
>
>> Worked here! -- I have also not been able to have the clients download
>> automatically using Automatic Updates and SUS on the SBS server... The
>> next
>> schedule update is tomorrow. I'll let you know if this fixes that as
>> well.
>>
>> Cheers,
>>
>> Steve K.
>>
>> "Tony Vaughan" <> wrote in message
>> news4B0A5DA-AAFB-4A1E-A48E-...
>> > Daniel Chow has come up with a possible reason for this problem.
>> >
>> > What I need you, out there, to do, is to try this out and let me know
>> > if
>> > it
>> > works.
>> >
>> > This message is directed to SBS 2003 users where the client IE has a
>> > default
>> > setting of http://companyweb/default.aspx.
>> >
>> > I simply ask that you reset the default page on your client
>> > workstations
>> > to
>> > something else, like http://www.msn.co.uk/default.asp?Ath=f. Reboot to
>> > clear
>> > everything.
>> >
>> > Then try WU5.
>> >
>> > Please let me know what happens.
>> >
>> > Now, why do this. As I understand it, this is something to do with
>> > riched20.dll and the fact that SBS 2003 now employs SharePoint.
>> > However,
>> > we
>> > need your feadback to confirm this.
>> >
>> > I look forward to hearing from you all.
>> >
>> > Tony
>>
>>
>>

Hi Steve

Thanks for your input.

You may not be aware that I have uninstalled SP2 from all my computers until
the various problems with SP2 have been resolved. Therefore, I have Automatic
Updates switched off to stop WU5 from prioritising SP2 all the time. So, I'm
sorry to say that I cannot comment on your specific problem.

Also, to be fair I cannot take any credit for the fix. This was spotted by
Daniel Chow, from Microsoft, who has been working in his spare time to
resolve this problem based upon the WindowsUpdate.Log file that I sent him.

This led him to think that riched20.dll had something to do with the issue
and one of his colleagues came up with the current theory about SharePoint.
Definitely obscure!!!

My role has merely been to advertise the possible fix which gets us around
the problem until Microsoft fix the riched20.dll, which I guess will happen
in some future update on SBS 2003 server and/or client. Beats having to log
on as administrator every time you want to run WU5.

Glad you're pleased though.

Tony

"Steve Kemp" wrote:

> I can confirm that this fix has corrected the problem on all of my WinXP SP2
> clients that I have tested it on (and all were having the problem).
>
> As for the Automatic update issue I mentioned.... if it is related I can no
> longer difinitively confirm that this will fix it, I have made a number of
> changes to the SUS service, including moving it to another server (off the
> SBS server) which had room to download the patches locally. So if it if
> fixed (waiting for next update interval) I can't say what was the cause of
> the fix.
>
> Anyway, nice job... this was an obscure fix.
>
> Cheers,
>
> Steve K.
>
>
>
> "Tony Vaughan" <> wrote in message
> news:B4573E77-B96A-40E4-AB30-...
> > Hi Steve
> >
> > Thanks for that.
> >
> > Maybe we've got it.
> >
> > Keep this topic informed, as will I.
> >
> > Tony
> >
> > "Steve Kemp" wrote:
> >
> >> Worked here! -- I have also not been able to have the clients download
> >> automatically using Automatic Updates and SUS on the SBS server... The
> >> next
> >> schedule update is tomorrow. I'll let you know if this fixes that as
> >> well.
> >>
> >> Cheers,
> >>
> >> Steve K.
> >>
> >> "Tony Vaughan" <> wrote in message
> >> news4B0A5DA-AAFB-4A1E-A48E-...
> >> > Daniel Chow has come up with a possible reason for this problem.
> >> >
> >> > What I need you, out there, to do, is to try this out and let me know
> >> > if
> >> > it
> >> > works.
> >> >
> >> > This message is directed to SBS 2003 users where the client IE has a
> >> > default
> >> > setting of http://companyweb/default.aspx.
> >> >
> >> > I simply ask that you reset the default page on your client
> >> > workstations
> >> > to
> >> > something else, like http://www.msn.co.uk/default.asp?Ath=f. Reboot to
> >> > clear
> >> > everything.
> >> >
> >> > Then try WU5.
> >> >
> >> > Please let me know what happens.
> >> >
> >> > Now, why do this. As I understand it, this is something to do with
> >> > riched20.dll and the fact that SBS 2003 now employs SharePoint.
> >> > However,
> >> > we
> >> > need your feadback to confirm this.
> >> >
> >> > I look forward to hearing from you all.
> >> >
> >> > Tony
> >>
> >>
> >>
>
>
>

Tony Vaughan wrote:

> Hi Steve
>
> Thanks for your input.
>
> You may not be aware that I have uninstalled SP2 from all my computers until
> the various problems with SP2 have been resolved. Therefore, I have Automatic
> Updates switched off to stop WU5 from prioritising SP2 all the time. So, I'm
> sorry to say that I cannot comment on your specific problem.

Just in case you are not aware of it:

To avoid that Automatic Updates tries to install SP2 (up to 16. April
2005):

Temporarily Disabling Delivery of Windows XP Service Pack 2 through
Windows Update and Automatic Updates
http://www.microsoft.com/technet/pro.../sp2aumng.mspx


Toolkit to Temporarily Block Delivery of Windows XP SP2 to a PC Through
Automatic Updates and Windows Update
http://www.microsoft.com/downloads/d...displaylang=en


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Hi Torgeir

Thanks for that. This link will be useful for people who want to keep
automatic downloads that omit SP2.

Tony

"Torgeir Bakken (MVP)" wrote:

> Tony Vaughan wrote:
>
> > Hi Steve
> >
> > Thanks for your input.
> >
> > You may not be aware that I have uninstalled SP2 from all my computers until
> > the various problems with SP2 have been resolved. Therefore, I have Automatic
> > Updates switched off to stop WU5 from prioritising SP2 all the time. So, I'm
> > sorry to say that I cannot comment on your specific problem.
>
> Just in case you are not aware of it:
>
> To avoid that Automatic Updates tries to install SP2 (up to 16. April
> 2005):
>
> Temporarily Disabling Delivery of Windows XP Service Pack 2 through
> Windows Update and Automatic Updates
> http://www.microsoft.com/technet/pro.../sp2aumng.mspx
>
>
> Toolkit to Temporarily Block Delivery of Windows XP SP2 to a PC Through
> Automatic Updates and Windows Update
> http://www.microsoft.com/downloads/d...displaylang=en
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Tony,

I will confirm that this seems to have worked here.

However, on another problem, I have yet to see ANY WinXP Pro SP2 computer (I
haven't tested XP Home), whether a member or a domain or not, pull down ANY
critical update using Auto Update.

--
Wayne Morgan
MS Access MVP


"Tony Vaughan" <> wrote in message
news4B0A5DA-AAFB-4A1E-A48E-...
> Daniel Chow has come up with a possible reason for this problem.
>
> What I need you, out there, to do, is to try this out and let me know if
> it
> works.
>
> This message is directed to SBS 2003 users where the client IE has a
> default
> setting of http://companyweb/default.aspx.
>
> I simply ask that you reset the default page on your client workstations
> to
> something else, like http://www.msn.co.uk/default.asp?Ath=f. Reboot to
> clear
> everything.
>
> Then try WU5.
>
> Please let me know what happens.
>
> Now, why do this. As I understand it, this is something to do with
> riched20.dll and the fact that SBS 2003 now employs SharePoint. However,
> we
> need your feadback to confirm this.
>
> I look forward to hearing from you all.
>
> Tony

Wayne Morgan wrote:

> Tony,
>
> I will confirm that this seems to have worked here.
>
> However, on another problem, I have yet to see ANY WinXP Pro SP2 computer
> (I haven't tested XP Home), whether a member or a domain or not, pull down
> ANY critical update using Auto Update.
>

Whoa! That's a bloody serious problem. Shoot Bill in the other foot and
tell him to get on it.

JosephKK

Hi Wayne

I've deinstalled SP2 from all my client machines because there are still
hardware and software manufacturers that haven't addressed the SP2 problem
yet; e.g. HP scanner sharing doesn't work under SP2. Microsoft have provided
a solutions page for many of the commonly used products that need to have
sharing across more than one PC; e.g. Veritas backup. Symantec have also
given extensive solutions to their sharing products like WinFax Pro.

But, before I deinstalled SP2 I got the same 0x8007045A problem. As I
understand it, the 0x8007045A problem is not related to SP2 at all, but is
involved with the interaction of SBS 2003 with WU5 which causes riched20.dll
to be corrupted. So, I am not surprised that you get the problem with SP2.

However, I am surprised by your claim that WU5 does not work on any Win XP
Pro SP2 machine, because I know people for whom it does work. The theory has
been that changing your browser's default homepage to something other than
'http://companyweb/default.aspx' seems to prevent a non WinXP compliant
version of riched20.dll, or one of its components, from being downloaded to
the client machine when the default homepage is called as IE starts up. This
seems to have nothing to do with SP2 as I explained above.

Could there be anything else about the machines you have tested which
indicate some common factor other than my experience that all seemed to be
clients of SBS 2003 and using the default company homepage?

Yours sincerely

Tony

"Wayne Morgan" wrote:

> Tony,
>
> I will confirm that this seems to have worked here.
>
> However, on another problem, I have yet to see ANY WinXP Pro SP2 computer (I
> haven't tested XP Home), whether a member or a domain or not, pull down ANY
> critical update using Auto Update.
>
> --
> Wayne Morgan
> MS Access MVP
>
>
> "Tony Vaughan" <> wrote in message
> news4B0A5DA-AAFB-4A1E-A48E-...
> > Daniel Chow has come up with a possible reason for this problem.
> >
> > What I need you, out there, to do, is to try this out and let me know if
> > it
> > works.
> >
> > This message is directed to SBS 2003 users where the client IE has a
> > default
> > setting of http://companyweb/default.aspx.
> >
> > I simply ask that you reset the default page on your client workstations
> > to
> > something else, like http://www.msn.co.uk/default.asp?Ath=f. Reboot to
> > clear
> > everything.
> >
> > Then try WU5.
> >
> > Please let me know what happens.
> >
> > Now, why do this. As I understand it, this is something to do with
> > riched20.dll and the fact that SBS 2003 now employs SharePoint. However,
> > we
> > need your feadback to confirm this.
> >
> > I look forward to hearing from you all.
> >
> > Tony
>
>
>