Client/Server Synchronization issues

Fehler 0x8024400E in WindowsUpdate.log - MCSEboard.de MCSE Forum

Fehler 0x8024400E in WindowsUpdate.log - MCSEboard.de MCSE Forum — Wed, 18 Jun 2008 22:30:16 GMT

PingBack from http://www.mcseboard.de/tipps-links-5/fehler-0x8024400e-windowsupdate-log-136224.html#post835635

Potential WSUS 3 Issues

Jeff's Connected Corner — Wed, 18 Jun 2008 22:58:18 GMT

This morning I received notice from Microsoft about a potential issue with WSUS 3.0 - specifically installations

re: Client/Server Synchronization issues

Joswald Mata — Wed, 18 Jun 2008 23:45:37 GMT

Hi,

I have this problem but my Office 2003 SP1 update is declined and superseded by the most recent Office SP's and I can't approve it again.

Any ideas?

re: Client/Server Synchronization issues

WSUS — Thu, 19 Jun 2008 00:56:47 GMT

Dear Joswald,

Thank you for your feedback. What you need to do is approve the update with an action of "Not Approved". I know this can be a little confusing since you cannot approve an "Expired" update for an "Install" for example, but a "Declined" update can be returned to "Not Approved" (which means it is "Undeclined"). This is why we indicated to just hit "Enter" on the dialog per instructions on the main post.

I hope this helps.

Thank you.

More Info: WSUS Offline Scan Catalog Fails to Sync on ConfigMgr 2007

The WSUS Support Team Blog — Thu, 19 Jun 2008 01:51:43 GMT

Just a quick heads up that it looks like Cecilia Cole from the WSUS product team posted some more information

More Info: WSUS Offline Scan Catalog Fails to Sync on ConfigMgr 2007

SMS&MOM — Thu, 19 Jun 2008 01:55:04 GMT

Just a quick heads up that it looks like Cecilia Cole from the WSUS product team posted some more information

re: Client/Server Synchronization issues

Bastian Haas — Thu, 19 Jun 2008 10:24:51 GMT

Thanks Cecilia, I had found this issue in my environment two days ago and did not manage to correct this until now. Your instructions did solve the problem.

re: Client/Server Synchronization issues

Christopher Hill — Thu, 19 Jun 2008 14:17:20 GMT

Hi,

In the post, instruction 2c seems a little unclear:

c. Decline the update.

i. Right-click the update and then click Approve in the shortcuts menu.

ii. In the Approve Updates dialog that opens, just click OK. Dismiss the Approval Progress dialog that appears.

This isn't the way that you decline an update in WSUS - you have to right-click and click 'Decline', then in the 'Decline Update' dialog, select 'Yes'. Could you check this and update the post with what we're meant to do?

re: Client/Server Synchronization issues

Christopher Hill — Thu, 19 Jun 2008 14:31:14 GMT

I've also noticed that the Office 2003 SP1 update now has a release date of '10/6/3008' on my WSUS server (note the year is *waaay* in the future!)

Is this the reason why we're having problems, or is it just my server?

re: Client/Server Synchronization issues

Dustin Freeman — Thu, 19 Jun 2008 15:49:46 GMT

This Resolved the issue! The instuctions in 2c are incorrect but just replace Approve with Dismiss. :)

re: Client/Server Synchronization issues

John — Thu, 19 Jun 2008 18:35:50 GMT

Oh, thank goodness this was posted--I started running into this exact problem this week, and was stumped!

Christopther -- I see the same crazy date on my server. It's not just you.

re: Client/Server Synchronization issues

Kirk — Fri, 20 Jun 2008 00:04:48 GMT

THANK YOU!!!!

I've been trying everything - to no avail. I was just about to re-format and do a fresh install. After finding this post it has finally fixed the 0x8024400E errors showing in the WindowsUpdate.log.

Date shows 6/10/3008 here also for Office 2003 SP1.

re: Client/Server Synchronization issues

Cal — Fri, 20 Jun 2008 16:37:18 GMT

so what is the first indication that there is a problem? Surely we don't have to read logs just to make this determination!

re: Client/Server Synchronization issues

Klaus — Fri, 20 Jun 2008 16:38:26 GMT

Approving and Declining the Office update removed the 0x8024400E error.

Instead I am receiving now another error on the client and I am still not getting updates:

WARNING: Exceeded max server round trips: 0x80244010

WARNING: Sync of Updates: 0x80244010

WARNING: SyncServerUpdatesInternal failed: 0x80244010

re: Client/Server Synchronization issues

Klaus — Fri, 20 Jun 2008 23:01:38 GMT

The clients did update eventually without any additional changes.

So it seems that the 0x80244010 error does not prevent a successful update at another time.

re: Client/Server Synchronization issues

James Newton — Sat, 21 Jun 2008 23:27:21 GMT

I seem to have had exactly this problem, with one exception, and one problem with the resolution given. The exception is that my SoftwareDistribution.log shows:

"Key in dictionary: '8915' Key being added: '8915'"

Rather than the

"Key in dictionary: '8862' Key being added: '8862'"

Listed here. Maybe that doesn't matter? I'm afraid I don't know enough about WSUS to know if it does or doesn't.

The problem I have with the resolution is that I don't have an update called "Office 2003 Service Pack 1" in my list of updates. It is not listed under "Declined" and it is not listed under "Any Except Declined". I do have Office 2003 Service Pack 2 and 3, and I have "Office 2003 Service Pack 1 for English User Interface Pack" and "...for Multilingual Interface Pack" and "...for Proofing Tools" but nothing with the update ID you specified.

However... I did a search for the update by name and it appeared in the results. I was able to decline the update, and then it appeared in the list of updates in the WSUS console. I followed the instructions given above except that in step C. I right clicked and selected "Decline" then pressed "Yes".

And that fixed the problem! Thanks!

re: Client/Server Synchronization issues

Michael — Mon, 23 Jun 2008 19:51:27 GMT

I have the same problem. I followed the steps above several times. For some reason, the service pack "Has expired" and is being superseded by something, not allowing it to be approved. At this point, I still cannot get workstations to talk to the server. Has a magic fix been implemented to correct the 3008 Office 2003 Service Pack 1 error?

Help and Thanks.

re: Client/Server Synchronization issues

Michael — Mon, 23 Jun 2008 23:14:07 GMT

I went into WSUS, did a search for Office 2003, right clicked on Service Pack 1 and choose revisions. From that screen, I right clicked on each revision, chose approved for install. After approving each one (even the ones that were expired) I then declined each one (even the ones that would not approve). I then did a manual synchro, then they SLOWLY started coming back to the server.

re: Client/Server Synchronization issues

Chad Kelley — Wed, 25 Jun 2008 16:56:44 GMT

After a full day of researching this problem I stumbled onto this site & saw Cecilia's post & thankfully it has resolved the issue where all other attempts had failed. Thanks Cecilia.

re: Client/Server Synchronization issues

Chris — Thu, 26 Jun 2008 23:23:06 GMT

WOO! Hopefully this fixes the issues I have been having running updates after Office 2003 installs.

Reloading a computer tomorrow to find out.

re: Client/Server Synchronization issues

Michael — Fri, 27 Jun 2008 09:43:51 GMT

Where is the KB article for this problem?

Do we really have to resort to blog entries to fix faults in Microsoft's software?

re: Client/Server Synchronization issues

Paul Thomas — Fri, 27 Jun 2008 15:30:30 GMT

I spent hours looking for a fix for this. Ten mins after reading this WSUS was working again. Nice one, thanks

re: Client/Server Synchronization issues

Jeff — Mon, 30 Jun 2008 19:43:43 GMT

Wow did this save me from slitting my wrist. Shoot microsoft this week admits to the issue and a hot fix in a couple of weeks.

Decline office SP1 and shazam.

THANK YOU

re: Client/Server Synchronization issues

127 — Tue, 01 Jul 2008 09:07:34 GMT

@Michael,

********************************************************************

Title: Microsoft Security Advisory Notification

Issued: June 30, 2008

********************************************************************

Security Advisories Updated or Released Today ==============================================

* Microsoft Security Advisory (954960)

- Title: Microsoft Windows Server Update Services

(WSUS) Blocked from Deploying Security Updates

- http://www.microsoft.com/technet/security/advisory/954960.mspx

- Revision Note: Advsiory published.

Advisory 954960 su WSUS: un problema non-security impedisce il corretto aggiornamento di client con Office 2003

Security Blog di Feliciano Intini — Tue, 01 Jul 2008 11:44:46 GMT

C'è purtroppo l'evidenza di un problema non-security analogo negli effetti a quello descritto dallo

re: Client/Server Synchronization issues

Eric Vinckel — Mon, 07 Jul 2008 11:54:25 GMT

Hi,

I guess that i have a similar issue with another update :

WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200

PT WARNING: SOAP Fault: 0x000190

WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"

PT WARNING: ID:2a7512fe-2d8f-4c3b-a586-1ce1197cb468

Can you tell which update shall i decline ???

Many thanks in advance

Eric

re: Client/Server Synchronization issues

Rainer — Wed, 09 Jul 2008 03:14:28 GMT

Hi,

I have WSUS 3.0 SP1 and SCCM 2007 SP1 in the same server. 95% of all our machines have Office 2003 SP3 and the rest Office 2007 or no Office at all.

Only machines without Office 2003 scan and synchronize OK with SCCM 2007 SP1 while all the rest 95 % of machines with Office 2003 won't synchronize at all. WindowsUpdate-logs show no errors on clientside.

In SCCM 2007 Software Update console show "Not Required" for all those machines with office 2003. I have used all the known tricks to start synchronizing but no avail. This has been like few weeks. I removed Office 2003 fram one computer and rebooted and synchronizing started for that machine.

Now I cant deliver any updates for those 95 % of machines and I haven't seen any advertisement from Microsoft to resolve this major problem.

re: Client/Server Synchronization issues

Malte — Thu, 10 Jul 2008 07:53:02 GMT

Update available now

http://support.microsoft.com/kb/954960

Patching WSUS 3.0 with KB954960

sKatterBrainZ — Thu, 10 Jul 2008 23:28:24 GMT

The WSUS Team finally posted word that an update/hotfix is now available (KB954960) for public download

re: Client/Server Synchronization issues

Eric Vinckel — Fri, 11 Jul 2008 12:07:03 GMT

Dear all,

That has fixed my issue (after applying SP1 and KB954960)

Many thanks

Windows Server Update Services Update (KB954960)

beqiraj.net — Sat, 12 Jul 2008 21:53:59 GMT

Windows Server Update Services Update (KB954960)

re: Client/Server Synchronization issues

James Newton — Mon, 14 Jul 2008 18:49:09 GMT

Reguarding:

http://www.microsoft.com/technet/security/advisory/954960.mspx

I would comment that this is of no use to the community at large; because it doesn't list the error messages the client is likly to encounter as a result of this bug, there is little chance that a user suffering from the problem will ever find the resolution.

I recommend you/they amend this advisory to include the following error messages:

Client Event Viewer shows Event ID 16, Source: Windows Update Agent, Category: Software Sync, Description: "Unable to connect..."

Viewing the WSUS log at C:\windows\WindowsUpdate.log (most recent entries at the bottom) shows "WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200 ... SOAP Fault: 0x000190 ... faultstring:Fault occurred ... ErrorCode:InternalServerError(5)"

Then when people google (sorry, when people use "Live" search) for those error messages, they will find that solution.

re: Client/Server Synchronization issues

Saku — Wed, 16 Jul 2008 11:58:37 GMT

Few weeks ago I installed a new computer.

Last week I did do another. At that point I noticed that

bot of them did not report to WSUS server having error 0x80244010 in their log.

After long Googling and tests without result I found this blog and did

Decline/approve Office sp1.

That helped and those 2 clients started to report/get updates.

1Note!

BEFORE

that I had done upgrade to WSUS from 3.0 to 3.0-SP1

Also installed the patch 954960 and checked that ddl version was 3.1.6001.66

Today I installed a new PC again. Just joticed that it gets same error 0x80244010 !!!

"¤##&%/&%¤%&#" I would like to say !

I have now done same things I did with those 2 PCs, but this time it seeems that

it does not help !

Now I'm totaly confused and so angry that ....

It seems that every time I add a new PC I have this trouble over and over again!

What should be done next?

re: Client/Server Synchronization issues

Saku — Thu, 17 Jul 2008 07:34:56 GMT

Ohh...the wonders of M$-world !

Story continues. After several tries (more than 10) I left this new computer on and went home.

On second morning when I came back to work I noticed that this poor PC had succesfully reported at 19:31 local time and downloaded all missing updates.

Every time I tried as follows:

- stopped automatic updates and Windows management instumentation services

- deleted contetns of %systemroot%\Softwaredistribution and %systemroot%\system32\WBEM\Repository

- deleted HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Windowsupdate\SusClientID

-removed computer from WSUS server's database

-started client services again

-launched wuauclt /resetauthorization /detectnow

The result was failure with error code 0x80244010

Now, when left alone, it has succeeded !

HOW CAN I TRUST THIS KIND OF SYSTEM ???

Now every time I install a new PC I have to look after updates. Do they ever start, or not.

Before this mess it was always clear that after few minutes of issuing wuauclt PC was downloading updates.

A fix for Client/Server Synchronization Issues

WSUS Product Team Blog — Fri, 01 Aug 2008 19:32:44 GMT

Hi all, We have released a fix for the synchronization issues that Cecilia described in http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx

re: Client/Server Synchronization issues

Dan Overes — Tue, 05 Aug 2008 19:27:59 GMT

Fantastic, I was able to use the workaround in this post to resolve a problem I was having where four machines had stopped talking to WSUS. (I should have scrolled down further to see that a fix has now been released, but the workaround worked just great.)

Thanks so much for this. There were a lot of mentions of this error on the web but this was the only solution which actually worked.

re: Client/Server Synchronization issues

John Jersey — Fri, 08 Aug 2008 20:50:33 GMT

I had a machine this morning that had not reported status in 7 days - it had Microsoft Office viewer installed. I removed the software, and viola, ran wuauclt /resetauthorization /detectnow and within minutes it reported in to the wsus server.

A fix for Client/Server Synchronization Issues

Microsoft Teams & Staff — Sun, 10 Aug 2008 06:50:37 GMT

Hi all, We have released a fix for the synchronization issues that Cecilia described in http://blogs

re: Client/Server Synchronization issues

wsus_user — Tue, 12 Aug 2008 02:37:21 GMT

We have applied the fix on all wsus servers but the problem still exsist. We still have System.ArgumentException: Item has already been added. Key in dictionary .... error messages in softwaredistribution.log.

Has anyone seen similar issue?

re: Client/Server Synchronization issues

ламинат — Wed, 13 Aug 2008 21:15:24 GMT

yfw Een plaatje zegt alles, toch ? foc Het volledige rapport is hier te vinden. Lees natuurlijk z de blogposting. i t

Thanks for interesting post! jgc

[url=http://skuper.ru]ламинированный парке[/url] 8e

Monthly Articles for June 2008

Team Blogs at Microsoft — Fri, 15 Aug 2008 01:47:34 GMT

132 Microsoft Team blogs searched, 105 blogs have new articles in the past 30 days. 641 new articles

re: Client/Server Synchronization issues

сайдинг — Mon, 18 Aug 2008 16:41:03 GMT

5qGood idea.4o I compleatly agree with last post.

<a href="http://all-siding.ru/index.php?section_id=83">медный сайдинг</a> 2c

<a href="http://all-siding.ru/index.php?section_id=127">под сайдинг</a> 1z

re: Client/Server Synchronization issues

ламинат — Fri, 05 Sep 2008 12:57:58 GMT

3jI dont think so.0s I compleatly agree with last post. vob

I'll happy if you come here <a href="http://skuper.ru">укладка ламината</a> 2m

re: Client/Server Synchronization issues

сайдинг — Mon, 08 Sep 2008 04:17:30 GMT

5cПознавательный материал!.8z Буду признателен, если посетите мой сайт.!

<a href="http://all-siding.ru/index.php?section_id=84">деревянный сайдинг</a> 4l

<a href="http://all-siding.ru/index.php?section_id=83">медный сайдинг</a> 4e

Удачи

re: Client/Server Synchronization issues

megaaslavik — Tue, 23 Sep 2008 22:30:59 GMT

В частности, были освещены вопросы изъятии земельных участков и иных объектов недвижимости для ?государственных нужд

Появился <a href="http://privlaw.ru">сайт школы российского частного права</a>.

Приглашаем всех заинтересованных в образовании, новостях в сфере права, а так же тех, кто заинтересован в повышении своей квалификации!

Обсуждения, новости, консультации и многое другое!

<a href="http://all-siding.ru/index.php?section_id=8">экспертиза</a> 6o

<a href="http://all-siding.ru/index.php?section_id=5">Российская школа частного права</a> 9t

re: Client/Server Synchronization issues

megaaslavik — Thu, 25 Sep 2008 09:49:37 GMT

Отвечу

Появился <a href="http://privlaw.ru">сайт школы российского частного права</a>.

Обсуждения, новости, консультации и многое другое!

<a href="http://privlaw.ru/index.php?section_id=41">учредительные документы</a> 0i

<a href="http://privlaw.ru/index.php?section_id=16">преподаватели</a> 3i Обсуждения

re: Client/Server Synchronization issues

ламинат — Thu, 25 Sep 2008 12:12:30 GMT

5cСпасибо за интересную информацию!.0w Буду рад, если посетите мой сайт.!

Сайдинг - защитит Ваш дом от неблагоприятного воздействия внешней ?среды, кроме того он позволяет значительно уменьшить затраты на ?обогрев дома.

<a href="http://skuper.ru/collections.php?collection_id=21">Сайдинг Вологда</a> 5g

<a href="http://skuper.ru/makers.php?maker_id=8">Ламинат kronotex</a> 0n

панели пвх

Удачи

re: Client/Server Synchronization issues

ilahi dinle — Sat, 18 Oct 2008 22:42:24 GMT

Client Event Viewer shows Event ID 16, Source: Windows Update Agent, Category: Software Sync, Description: "Unable to connect..."

thanks!

re: Client/Server Synchronization issues

müzik dinle — Mon, 20 Oct 2008 19:25:43 GMT

Microsoft Office viewer installed. I removed the software, and viola, ran wuauclt /resetauthorization /detectnow and within minutes it reported in to the wsus server.

re: Client/Server Synchronization issues

gelinlikler — Mon, 20 Oct 2008 19:26:29 GMT

Office 2003 Service Pack 1" in my list of updates. It is not listed under "Declined" and it is not listed under "Any Except Declined". I do have Office 2003 Service Pack 2 and 3, and I have "Office 2003 Service Pack 1 for English User Interface Pack" and

re: Client/Server Synchronization issues

yeni klipler — Mon, 20 Oct 2008 19:27:37 GMT

was having where four machines had stopped talking to WSUS. (I should have scrolled down further to see that a fix has now been released, but the workaround worked just great.)

re: Client/Server Synchronization issues

cizgi film — Mon, 20 Oct 2008 19:28:51 GMT

Item has already been added. Key in dictionary .... error messages in softwaredistribution.log.

Has anyone seen similar issue?

re: Client/Server Synchronization issues

belgesel — Mon, 20 Oct 2008 19:29:45 GMT

Now every time I install a new PC I have to look after updates. Do they ever start, or not.

Before this mess it was always clear that after few minutes of issuing wuauclt PC was downloading updates.

thanks!

re: Client/Server Synchronization issues

autocad kursu — Wed, 12 Nov 2008 16:14:21 GMT

Item has already been added. Key in dictionarys thanks you very nice

re: Client/Server Synchronization issues

film izle — Wed, 12 Nov 2008 16:15:13 GMT

Before this mess it was always clear that afters few minute of issuing wuauclt PC was downloading update thanks you very nice

re: Client/Server Synchronization issues

gaziosmanpaşa — Wed, 12 Nov 2008 16:17:01 GMT

(I should have scrolleds down furthers to see that a fix has now been releaseds, but the workarounds worked just great.)

thank you very nice

re: Client/Server Synchronization issues

gelinlikler — Wed, 12 Nov 2008 16:17:57 GMT

Item has already been added. Key in dictionarys .... error messages in softwaredistribution.log thanks

re: Client/Server Synchronization issues

havuz — Wed, 12 Nov 2008 16:19:59 GMT

Now every time I install a new PC I have to look afters update. Do they ever start, or not's thanks you very nice

re: Client/Server Synchronization issues

dermedic — Fri, 05 Dec 2008 12:26:08 GMT

Very nice site, helpful articles - good job, thanks

re: Client/Server Synchronization issues

dasd — Thu, 11 Dec 2008 15:53:38 GMT

http://www.battery-export.com/hp/hp-pavilion-dv9500-series.html HP Pavilion dv9500 Series

http://www.battery-export.com/hp/hp-pavilion-dv9600-series.html HP Pavilion dv9600 Series

http://www.battery-export.com/hp/hp-pavilion-tx1000-series.html HP Pavilion tx1000 Series

re: Client/Server Synchronization issues

dass — Thu, 11 Dec 2008 15:53:58 GMT

http://www.battery-export.com/hp/hp-pavilion-tx1100-series.html HP Pavilion tx1100 Series

http://www.battery-export.com/hp/hp-pavilion-tx1200-series.html HP Pavilion tx1200 Series

http://www.battery-export.com/hp/hp-pavilion-tx1300-series.html HP Pavilion tx1300 Series

re: Client/Server Synchronization issues

film izle — Sun, 28 Dec 2008 04:27:57 GMT

Client Event Viewer shows Event ID 16, Source: Windows Update Agent, Category: Software Sync, Description: "Unable to connect..."

thanks and regards..

re: Client/Server Synchronization issues

sohbet odaları — Thu, 01 Jan 2009 18:23:01 GMT

thansk <a href="http://www.trstar.net" title="chat sohbet, sohbet odalari">sohbet chat</a> sites no spam :D

re: Client/Server Synchronization issues

ghhgfx — Fri, 02 Jan 2009 21:46:08 GMT

http://mircse.com http://mircindir.cc mirc download mirc yükle mirc indir

re: Client/Server Synchronization issues

hardingdgh — Wed, 21 Jan 2009 21:36:46 GMT

Is there some prohibition against Vista Home PC's from using WSUS 3.0 within a workgroup?

I have home network setup with as a workgroup (not AD). I have a Win2003 server with WSUS 3.0 installed. I can get my WinXP Pro, WinXP Home, Vista Pro computers to update against the WSUS server. No matter what I try I cannot get my Vista Home PC to updated against the WSUS 3.0 server.

I have been Googling for more than a week and I've seen several articles with users stating they can't get their Vista Home PC's to update via the WSUS server.

I do have connectivity between server and PC. I have a WSUS shared drive mapped onto the Vista Home PC. I am able to RemoteDesktop into the WSUS server from the Vista Home PC.

I welcome you suggestions and/or URLS

Thank you :-)

re: Client/Server Synchronization issues

mirc — Sat, 14 Feb 2009 16:07:06 GMT

Client Event Viewer shows Event ID 16, Source: Windows Update Agent, Category: Software Sync, Description: "Unable to connect..???

re: Client/Server Synchronization issues

mirc yükle — Sat, 14 Feb 2009 16:08:35 GMT

Very nice site, helpful articles - good job, thanks

re: Client/Server Synchronization issues

mirc — Sat, 14 Feb 2009 16:14:22 GMT

re: Client/Server Synchronization issues

kafkasya — Sat, 14 Feb 2009 16:15:39 GMT

Отвечу

re: Client/Server Synchronization issues

karot — Sun, 15 Feb 2009 18:47:56 GMT

This morning I received notice from Microsoft about a potential issue with WSUS 3.0 - specifically installations

re: Client/Server Synchronization issues

kartvizit — Sun, 15 Feb 2009 18:48:14 GMT

re: Client/Server Synchronization issues

Alf — Thu, 19 Feb 2009 12:57:15 GMT

Hi,

I got the same error and did not have that SP1 for O2k3 in my WSUS Server. I applied the patch referenced at http://support.microsoft.com/kb/954960#top (it needs to be applied in the server only) and forced the update in the clients. Seems to work fine.

Alf

re: Client/Server Synchronization issues

Tom B — Thu, 26 Feb 2009 01:22:17 GMT

Unfortunately, I'm not running Office 2003. Have an almost-new server running Windows 2003 Server sp2, with Dynamics SL, and Office 2007. Getting the same old tedious 'windows update client failed to connect with error 0x80244010'

Run clientdiag.exe, and it reports everything passes, connects to the proper server (running wsus 3.0.600.374)

Stopped auto updates, emptied out the Windows\softwareupdates folder, and restarted it, same error.

I can IE to update.microsoft.com and it finds the updates that are sitting on the wsus server, but which it can't see.

Am I just sunk?

re: Client/Server Synchronization issues

kelebek — Mon, 02 Mar 2009 22:06:42 GMT

thansk you sites guzle eyr begendım

WSUS 3.0 e 3.0 SP1: Mancata sincronizzazione dei client

DevAdmin Blog — Tue, 17 Mar 2009 23:57:09 GMT

WSUS 3.0 e 3.0 SP1: Mancata sincronizzazione dei client

re: Client/Server Synchronization issues

mirc — Mon, 30 Mar 2009 02:32:06 GMT

Thank you This Site İs Nice :)

re: Client/Server Synchronization issues

tower defense — Tue, 14 Apr 2009 10:15:06 GMT

Wow did this save me from slitting my wrist. Shoot microsoft this week admits to the issue and a hot fix in a couple of weeks.

re: Client/Server Synchronization issues

loozer — Wed, 15 Apr 2009 06:34:21 GMT

Nightmare - the system put in place to handle bugs/patches/updates has got a bug(s) in it :(

What was that about TCO?

Microsoft does not get it's reputation for no good reason.

re: Client/Server Synchronization issues

gdoran — Thu, 16 Apr 2009 00:57:43 GMT

From what I can tell, Office 2003 sp1 was already superceeded by Office 2003 sp3. Does this still apply? Here is what I get on the client:

50 PT +++++++++++ PT: Synchronizing server updates +++++++++++

2009-04-03 15:41:44:673 1036 f50 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ipsads-01/ClientWebService/client.asmx

2009-04-03 15:41:44:751 1036 f50 PT WARNING: Cached cookie has expired or new PID is available

2009-04-03 15:41:44:751 1036 f50 PT Initializing simple targeting cookie, clientId = 3b449fda-4a47-467e-89ac-121f70c5e04a, target group = , DNS name = csxp-1404.ipsmerchant.local

2009-04-03 15:41:44:751 1036 f50 PT Server URL = http://ipsads-01/SimpleAuthWebService/SimpleAuth.asmx

2009-04-03 15:41:44:798 1036 f50 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

2009-04-03 15:41:44:798 1036 f50 PT WARNING: SOAP Fault: 0x00012c

2009-04-03 15:41:44:798 1036 f50 PT WARNING: faultstring:Fault occurred

2009-04-03 15:41:44:798 1036 f50 PT WARNING: ErrorCode:ServerChanged(4)

2009-04-03 15:41:44:814 1036 f50 PT WARNING: Message:Server rolled back since last call to GetCookie

2009-04-03 15:41:44:814 1036 f50 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"

2009-04-03 15:41:44:814 1036 f50 PT WARNING: ID:6c5c5b43-6536-477a-9424-5ecd4c782c2c

2009-04-03 15:41:44:814 1036 f50 PT WARNING: PTError: 0x80244015

2009-04-03 15:41:44:814 1036 f50 PT WARNING: GetCookie_WithRecovery failed : 0x80244015

2009-04-03 15:41:44:814 1036 f50 PT WARNING: RefreshCookie failed: 0x80244015

2009-04-03 15:41:44:814 1036 f50 PT WARNING: RefreshPTState failed: 0x80244015

2009-04-03 15:41:44:814 1036 f50 PT WARNING: Sync of Updates: 0x80244015

2009-04-03 15:41:44:845 1036 f50 PT WARNING: Cached cookie has expired or new PID is available

2009-04-03 15:41:44:845 1036 f50 PT Initializing simple targeting cookie, clientId = 3b449fda-4a47-467e-89ac-121f70c5e04a, target group = , DNS name = csxp-1404.ipsmerchant.local

2009-04-03 15:41:44:845 1036 f50 PT Server URL = http://ipsads-01/SimpleAuthWebService/SimpleAuth.asmx

2009-04-03 15:41:45:157 1036 f50 Agent * WARNING: Failed to synchronize, error = 0x80244015

2009-04-03 15:41:45:173 1036 f50 DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed

2009-04-03 15:41:45:173 1036 f50 Agent Server changed and need resyncing with server

2009-04-03 15:41:45:267 1036 f50 PT +++++++++++ PT: Synchronizing server updates +++++++++++

2009-04-03 15:41:45:267 1036 f50 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ipsads-01/ClientWebService/client.asmx

2009-04-03 15:41:45:767 1036 f50 PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200

2009-04-03 15:41:45:767 1036 f50 PT WARNING: SOAP Fault: 0x000190

2009-04-03 15:41:45:767 1036 f50 PT WARNING: faultstring:Fault occurred

2009-04-03 15:41:45:767 1036 f50 PT WARNING: ErrorCode:InternalServerError(5)

2009-04-03 15:41:45:767 1036 f50 PT WARNING: Message:(null)

2009-04-03 15:41:45:767 1036 f50 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"

2009-04-03 15:41:45:767 1036 f50 PT WARNING: ID:20ad21de-5d25-4523-a30d-7f030a838e34

2009-04-03 15:41:45:767 1036 f50 PT WARNING: PTError: 0x8024400e

2009-04-03 15:41:45:767 1036 f50 PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400e

2009-04-03 15:41:45:767 1036 f50 PT WARNING: Sync of Updates: 0x8024400e

2009-04-03 15:41:45:767 1036 f50 PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e

2009-04-03 15:41:45:767 1036 f50 Agent * WARNING: Failed to synchronize, error = 0x8024400E

2009-04-03 15:41:45:782 1036 f50 Agent * WARNING: Exit code = 0x8024400E

2009-04-03 15:41:45:782 1036 f50 Agent *********

2009-04-03 15:41:45:782 1036 f50 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]

2009-04-03 15:41:45:782 1036 f50 Agent *************

2009-04-03 15:41:45:782 1036 f50 Agent WARNING: WU client failed Searching for update with error 0x8024400e

2009-04-03 15:41:45:782 1036 e18 AU >>## RESUMED ## AU: Search for updates [CallId = {9AC8F175-664B-402D-95AA-6B13FE0BDC15}]

2009-04-03 15:41:45:782 1036 e18 AU # WARNING: Search callback failed, result = 0x8024400E

2009-04-03 15:41:45:782 1036 e18 AU # WARNING: Failed to find updates with error code 8024400E

2009-04-03 15:41:45:782 1036 e18 AU #########

2009-04-03 15:41:45:782 1036 e18 AU ## END ## AU: Search for updates [CallId = {9AC8F175-664B-402D-95AA-6B13FE0BDC15}]

2009-04-03 15:41:45:782 1036 e18 AU #############

2009-04-03 15:41:45:798 1036 e18 AU AU setting next detection timeout to 2009-04-04 01:41:45

2009-04-03 15:41:45:798 1036 e18 AU Setting AU scheduled install time to 2009-04-04 08:00:00

2009-04-03 15:41:50:782 1036 f50 Report REPORT EVENT: {C055E9E4-F989-49A1-B73A-FB0B1323436

re: Client/Server Synchronization issues

forummu.com — Thu, 16 Apr 2009 15:10:49 GMT

Nice sharing

http://www.clubturknet2seoyarismasi.info/

http://www.lightme.biz/

re: Client/Server Synchronization issues

Norman Gifs — Fri, 24 Apr 2009 01:36:55 GMT

Thank you Cecilia!

http://www.hotbarbiegames.com

re: Client/Server Synchronization issues

Bosco Dilaggio — Wed, 06 May 2009 12:42:12 GMT

Английский в Пензе, итальянский язык в Пензе http://www.mirpenza.ru иностранные языки, обучение.

re: Client/Server Synchronization issues

club penguin — Sat, 16 May 2009 04:20:48 GMT

I was able to use the workaround in this post to resolve a problem I was having where four machines had stopped talking to WSUS. I should have scrolled down further to see that a fix has now been released, but the workaround worked just great. Thanks so much for this.

re: Client/Server Synchronization issues

real estate attorney connecticut — Mon, 01 Jun 2009 18:26:45 GMT

Thank you for providing the workaround steps to fix this critical issue that prevents computers from receiving updates from the WSUS server. One of my business friends owns a Vista Home PC with Win2003 server connected to it. He can't get it to update via the WSUS server! Any suggestions?

re: Client/Server Synchronization issues

dissertation — Sun, 14 Jun 2009 22:37:03 GMT

updates from the WSUS server. One of my business friends owns a Vista Home PC with Win2003 server connected to it. He can't get it to update via the WSUS server! Any suggestions?

re: Client/Server Synchronization issues

Oyunlar — Tue, 16 Jun 2009 02:48:56 GMT

WOO! Hopefully this fixes the issues I have been having running updates after Office 2003 installs.

re: Client/Server Synchronization issues

Holger Ronecker — Wed, 01 Jul 2009 04:46:12 GMT

Is there a way to deploy this update with the Database for the WSUS Server being a SQL server and not the internal database?

This update fails here complaining that no connection to the <WSUS-Server>\MICROSOFT##SSEE can be made.

best regards,

Holger

re: Client/Server Synchronization issues

agence — Mon, 06 Jul 2009 12:22:01 GMT

I hope that it will fixe the issues I have been having after my updates.

re: Client/Server Synchronization issues

agence — Mon, 06 Jul 2009 12:24:42 GMT

Yes it works ... Many thanks for this issue !!!

re: Client/Server Synchronization issues

Guvenlik Sistemleri — Wed, 15 Jul 2009 00:40:47 GMT

Thanks for putting up the information.

<a href="http://www.guvenliksistemleri.info" title="Güvenlik sistemleri">Güvenlik Sistemleri</a>

re: Client/Server Synchronization issues

Wed, 22 Jul 2009 21:27:54 GMT

Very nice site, helpful articles - good job, thanks

re: Client/Server Synchronization issues

TDM — Wed, 22 Jul 2009 21:28:35 GMT

Very nice site, helpful articles - good job, thanks

re: Client/Server Synchronization issues

söve — Sat, 25 Jul 2009 12:45:25 GMT

Thanks for putting up the information.

re: Client/Server Synchronization issues

medyum — Sat, 25 Jul 2009 13:58:32 GMT

Thanks Cecilia, I had found this issue in my environment two days ago and did not manage to correct this until now. Your instructions did solve the problem.

re: Client/Server Synchronization issues

izmirdesatilik — Sat, 25 Jul 2009 16:13:13 GMT

<a href="www.izmirdesatilik.net">dere emlak kısık sanayi izmirde satılık arazi arsa bina dükkan ev fabrika villa yazlık</a>

re: Client/Server Synchronization issues

sevry — Tue, 28 Jul 2009 18:59:54 GMT

HELP!!! WSUS is out to get me!

I am getting the following error in the WindowsUpdate.log on multiple XP clients. I am about to give up.

DnldMgr WARNING: CryptAcquireContext failed with 0x8009001a.

DnldMgr WARNING: GenerateHash failed with 0x8009001a.

DnldMgr WARNING: GenerateDownloadDirName failed with 0x8009001a.

I can not get anywhere with the error code "0x8009001a".

Any help would be appreciated.

Thanks.

re: Client/Server Synchronization issues

telefon dinleme — Sat, 01 Aug 2009 14:08:52 GMT

<a href="http://www.casustelefon.com">telefon dinleme</a>

Spy Phone software, you want to track the person's mobile phone conversations and the sounds of your spy and a copy of the message that without noticing that lets you capture a person's sistemdir.Yazılım goal, that wish to track a person's phone yüklenmelidir.Yazılım her mobile phone can not be installed! Compatible models that can be installed in short E and N series Nokia mobile telefonlarıdır.Yükleme process for the target phone in your hand is simple and olmalıdır.Yükleme business kısadır.Kullanım manual installation process and detailed with a simple language anlatılmıştır.Yükleme after their mobile phone number of the target phone is found to translate climate All messages and phone calls dinleyebilirsiniz.Ayrıca target person as you reach to your mobile phone or SMS.