J
John
All,
The fix in the blog was the trick for me too:
http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx
Thank you all. We've had our share lately!
John
"Alexander" wrote:
> This definetely works!! Thanks to everybody!
>
> (Mention the misspelling in step "c": I guess the author meant to select
> Decline, not Approve)
>
> "groovyf" <groovyf@discussions.microsoft.com> wrote in message
> news:80F74FB4-109B-4D93-87C2-30CED43615F8@microsoft.com...
> > Someone (mendocinosunrise) has posted something rather interesting over at
> > www.wsus.info forums. I've yet to try this, but shall do so in the
> > morning.
> > I'll paste it here:
> >
> > I fought with the same error, then gave up & emailed MS.
> > NOTE: the workaround below didn't work at first because the problem update
> > was expired. However, I ran through the steps a couple of times & then
> > manually resynchronized the WSUS server. After that, clients started
> > synchronizing correctly.
> >
> > Here's their workaround from the MS tech:
> > Thank you for the log. The error you see repeated in the log, 0x8024400E,
> > is
> > consistent with an issue that has been appearing recently. I've posted
> > some
> > root cause information and steps to resolve below. Please review the
> > information and apply the workaround. This is a new problem, so a KB
> > article
> > has not yet been released.
> >
> > <snip>
> >
> > " Root Cause:
> > A recent revision to the 'Office 2003 Service Pack 1' update has resulted
> > in
> > some WSUS 3.0 servers syncing that revision to enter an inconsistent state
> > with respect to the update's approvals. When computers with products
> > related
> > to Office 2003 talk to such a server, the web service is unable to process
> > the approvals resulting in the detection failure.
> >
> > Workaround:
> > In order to reset the approvals to a consistent state on the WSUS server,
> > follow these steps from the WSUS Administration Console
> > 1. Find the 'Office 2003 Service Pack 1' update in the updates list. This
> > may involve changing the Approval and Status filters in the update UI (set
> > the Status to "Any" and the Approval to "Declined" - if you don't see it
> > then
> > set the Approval to "Any except Declined"
> > 2. Perform the following steps:
> > a. First make sure the update is declined.
> > i. If the update is not yet declined, right click on the update and
> > decline
> > it.
> > b. Next, approve the update.
> > i. Right click on the update and select the 'Approve...' option in the
> > context menu.
> > ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss
> > the
> > 'Approval Progress' dialog that appears.
> > c. Next, decline the update.
> > i. Right click on the update and select the 'Approve...' option in the
> > context menu.
> > ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss
> > the
> > 'Approval Progress' dialog that appears.
> >
> > The computers that were failing detection will now successfully complete
> > detection against the server and receive any applicable updates.
> >
> > Note: If you have a hierarchy of WSUS servers, these steps must be
> > performed
> > on each server, starting with the top-level server. If one of the servers
> > is
> > a replica child, one must first change it to be autonomous, then perform
> > the
> > steps above, then change it back to being a replica. This can be done from
> > the Options/Update Source and Proxy Server Dialog."
> >
> >
> >
> > "Ray Chan" wrote:
> >
> >> Can you try uninstalling it and see if it'll register with WSUS? That's
> >> the
> >> only way it works for me and I just wanted to see if others are having
> >> the
> >> same issue.
> >>
>
>
>
The fix in the blog was the trick for me too:
http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx
Thank you all. We've had our share lately!
John
"Alexander" wrote:
> This definetely works!! Thanks to everybody!
>
> (Mention the misspelling in step "c": I guess the author meant to select
> Decline, not Approve)
>
> "groovyf" <groovyf@discussions.microsoft.com> wrote in message
> news:80F74FB4-109B-4D93-87C2-30CED43615F8@microsoft.com...
> > Someone (mendocinosunrise) has posted something rather interesting over at
> > www.wsus.info forums. I've yet to try this, but shall do so in the
> > morning.
> > I'll paste it here:
> >
> > I fought with the same error, then gave up & emailed MS.
> > NOTE: the workaround below didn't work at first because the problem update
> > was expired. However, I ran through the steps a couple of times & then
> > manually resynchronized the WSUS server. After that, clients started
> > synchronizing correctly.
> >
> > Here's their workaround from the MS tech:
> > Thank you for the log. The error you see repeated in the log, 0x8024400E,
> > is
> > consistent with an issue that has been appearing recently. I've posted
> > some
> > root cause information and steps to resolve below. Please review the
> > information and apply the workaround. This is a new problem, so a KB
> > article
> > has not yet been released.
> >
> > <snip>
> >
> > " Root Cause:
> > A recent revision to the 'Office 2003 Service Pack 1' update has resulted
> > in
> > some WSUS 3.0 servers syncing that revision to enter an inconsistent state
> > with respect to the update's approvals. When computers with products
> > related
> > to Office 2003 talk to such a server, the web service is unable to process
> > the approvals resulting in the detection failure.
> >
> > Workaround:
> > In order to reset the approvals to a consistent state on the WSUS server,
> > follow these steps from the WSUS Administration Console
> > 1. Find the 'Office 2003 Service Pack 1' update in the updates list. This
> > may involve changing the Approval and Status filters in the update UI (set
> > the Status to "Any" and the Approval to "Declined" - if you don't see it
> > then
> > set the Approval to "Any except Declined"
> > 2. Perform the following steps:
> > a. First make sure the update is declined.
> > i. If the update is not yet declined, right click on the update and
> > decline
> > it.
> > b. Next, approve the update.
> > i. Right click on the update and select the 'Approve...' option in the
> > context menu.
> > ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss
> > the
> > 'Approval Progress' dialog that appears.
> > c. Next, decline the update.
> > i. Right click on the update and select the 'Approve...' option in the
> > context menu.
> > ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss
> > the
> > 'Approval Progress' dialog that appears.
> >
> > The computers that were failing detection will now successfully complete
> > detection against the server and receive any applicable updates.
> >
> > Note: If you have a hierarchy of WSUS servers, these steps must be
> > performed
> > on each server, starting with the top-level server. If one of the servers
> > is
> > a replica child, one must first change it to be autonomous, then perform
> > the
> > steps above, then change it back to being a replica. This can be done from
> > the Options/Update Source and Proxy Server Dialog."
> >
> >
> >
> > "Ray Chan" wrote:
> >
> >> Can you try uninstalling it and see if it'll register with WSUS? That's
> >> the
> >> only way it works for me and I just wanted to see if others are having
> >> the
> >> same issue.
> >>
>
>
>
null)
