Re: WSUS Verteilerprobleme

Hallo Heinsolo,

"Heinsolo" <Heinsolo@xxxxxxxxxxxxxxxxxxxxxxxxx> schrieb im Newsbeitrag
news:14991FF1-E498-4ECF-8789-98875DEE269D@xxxxxxxxxxxxxxxx
Hallo Helmut,
DANKE erstmal für Deine schnelle Antwort. Okidoki, hier Auszüge aus dem
Logfile. Es ist so, dass diese Meldung ca. 85% des Logs ausmacht (es ist
also
immer die gleiche Meldung):

------begin-------

2006-04-25 15:00:27 2444 aa8 PT WARNING: GetCookie failure, error =
0x8024400A, soap client error = 10, soap error code = 0, HTTP status code
=
200
2006-04-25 15:00:27 2444 aa8 Report WARNING: Reporter failed to upload
events with hr = 8024400a.
2006-04-25 15:26:06 2444 768 PT Initializing simple targeting cookie,
clientId = e1aa9c9b-e04b-4d1a-a64c-650fa2d12677, target group = , DNS name
=
-> rechnername.domäne.xxx <-von mir geändert, Wert war richtig)


----end----

Hoffentlich hilft Dir das bei einer Fehlersuche. DANKE schon einmal
vorab!!!!

dazu habe ich das hier gefunden:

The 0x8024400a errors, which are a SOAP client parsing error, are believed
to be an issue between IIS and http.sys, and for Windows Server 2003 Service
Pack 1 systems, there is a hotfix available.

The scenario and fix are discussed in the summary article posted by Bobbie
Harder on Friday
7/16. Here is the extract that I believe may be applicable to your
situation:

Some clients have been impacted by a known issue in with Windows Server
2003 http.sys and IIS. In some cases, this transient issue will appear to
prevent clients from checking in, because they receive invalid responses
from the server after some attempts. It was previously believed to be an
issue with IIS compression and there was a workaround suggested to disable
compression, and then rename the %windir%\system32\inetsrv\suscomp.dll
file and restart the IIS, and the Update Services service.

Further Investigation shows the problem source to be a known condition with
IIS and http.sys, which is not related to compression, and for which there
is an available hotfix. It is not recommended to disable compression as
this will not impact the problem source, and possibly increase network
traffic & server load, while reducing the number of clients you can
effectively serve. Further information about the issue and obtaining the
hotfix can be found: http://support.microsoft.com/?id=898708.


--
Stefan Zivkovic


.

Relevant Pages

  • Re: RPC over HTTP 2000 / XP clients
    ... 2000 clients are not supported on the Windows Server 2003 version of IIS but apparenty it can be put in IIS 5.0 mode to support the older clients. ...
    (microsoft.public.exchange.connectivity)
  • RPC over HTTP 2000 / XP clients
    ... Just wondering if anyone has implemeted an RPC / HTTP solution that supports both 2000 and XP clients. ... 2000 clients are not supported on the Windows Server 2003 version of IIS but apparenty it can be put in IIS 5.0 mode to support the older clients. ...
    (microsoft.public.exchange.connectivity)
  • Re: IIS Compression and Windows Sharepoint Services
    ... Now static compression of ows.js and ie55up.js work fine. ... > - Changing HcFileExtensions requires restarting IIS for it to take ... Only ISAPI Extensions and CGI EXEs need to be added to Web ... > <IIsCompressionScheme Location ...
    (microsoft.public.inetserver.iis)
  • How to get my CA to be trusted by external clients?
    ... I have an IIS box that issued it's own cert for the ... clients use IE 6. ... avialable in the alert message (when you hit details, or advanced, or... ... and so there's no way for the client to install my CA as a trusted CA. ...
    (microsoft.public.inetserver.iis.security)
  • Use or Not to use ISA
    ... I am looking for advice on the best way to protect my web server. ... I currently sit behind a Symantec Gateway 360 security appliance firewall ... Win2k3 with IIS installed. ... small number of clients as well as my own. ...
    (microsoft.public.isa)