WSUS downstream server fails

Getting "Invalid Operation Exception: There is an error in xml document
(1,2236983) --> system.id.idexception unable to read data from the transport
connection. The connection was closed."

We see data on the router passing back and forth and our firewall rules are
ok. but WSUS fails after 10% syncronization.

Any ideas ?

[[ Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
]]

Travan wrote:
> Getting "Invalid Operation Exception: There is an error in xml document
> (1,2236983) --> system.id.idexception unable to read data from the
> transport
> connection. The connection was closed."
>
> We see data on the router passing back and forth and our firewall rules
> are
> ok. but WSUS fails after 10% syncronization.
>
> Any ideas ?

Sorry for going to the wrong church. But does anybody have a clue? Thanks.

"PA Bear [MS MVP]" wrote:

> [[ Right pew, wrong church. Forwarded to WSUS newsgroup
> (microsoft.public.windows.server.update_services) via crosspost as a
> convenience to OP.
>
> On the web:
> http://www.microsoft.com/communities...pdate_services
>
> In your newsreader:
> news://msnews.microsoft.com/microsof...pdate_services
> ]]
>
> Travan wrote:
> > Getting "Invalid Operation Exception: There is an error in xml document
> > (1,2236983) --> system.id.idexception unable to read data from the
> > transport
> > connection. The connection was closed."
> >
> > We see data on the router passing back and forth and our firewall rules
> > are
> > ok. but WSUS fails after 10% syncronization.
> >
> > Any ideas ?
>
>

Patience, please. We're all volunteers here.

Travan wrote:
> Sorry for going to the wrong church. But does anybody have a clue? Thanks.
>
> "PA Bear [MS MVP]" wrote:
>
>> [[ Right pew, wrong church. Forwarded to WSUS newsgroup
>> (microsoft.public.windows.server.update_services) via crosspost as a
>> convenience to OP.
>>
>> On the web:
>> http://www.microsoft.com/communities...pdate_services
>>
>> In your newsreader:
>> news://msnews.microsoft.com/microsof...pdate_services
>> ]]
>>
>> Travan wrote:
>>> Getting "Invalid Operation Exception: There is an error in xml document
>>> (1,2236983) --> system.id.idexception unable to read data from the
>>> transport
>>> connection. The connection was closed."
>>>
>>> We see data on the router passing back and forth and our firewall rules
>>> are
>>> ok. but WSUS fails after 10% syncronization.
>>>
>>> Any ideas ?

OK. Understand. Just that I'm under the gun on this one.

Am getting the following error:
Invalid Operation Exception:
There is an error in xml document (1,2236983) ---> system.id.idexception
unable to read data from the transport connection. The connection was closed.

still not working....

"Travan" wrote:

> OK. Understand. Just that I'm under the gun on this one.
>
>

"Travan" <> wrote in message news:2E60F6E4-1DE0-4850-951E-...
> Am getting the following error:
> Invalid Operation Exception:
> There is an error in xml document (1,2236983) ---> system.id.idexception
> unable to read data from the transport connection. The connection was closed.
>

> still not working....


That's no more information than you gave us the first time. ; }


---


>
> "Travan" wrote:
>
>> OK. Understand. Just that I'm under the gun on this one.
>>
>>

Found solution a while ago. Related to the WSUSPool Properties and recycling
the worker process.

"Robert Aldwinckle" wrote:

>
> "Travan" <> wrote in message news:2E60F6E4-1DE0-4850-951E-...
> > Am getting the following error:
> > Invalid Operation Exception:
> > There is an error in xml document (1,2236983) ---> system.id.idexception
> > unable to read data from the transport connection. The connection was closed.
> >
>
> > still not working....
>
>
> That's no more information than you gave us the first time. ; }
>
>
> ---
>
>
> >
> > "Travan" wrote:
> >
> >> OK. Understand. Just that I'm under the gun on this one.
> >>
> >>
>
>
>