WSUS services not showing up in Services and event error 364

I have two problems that I've been struggling with for awhile now.

I've installed and reinstalled several times and I can not get the
WSUSservice and the ContentSyncAgent to show up in the Services window. The
program seems to work for awhile after installing but eventually I get a
message in the To Do List saying: "One or more Update Service components
could not be contacted. Check your server status and ensure that the Windows
Server Update Service is running. Non-running services: ContentSyncAgent,
WSUSService". There is no was to start the service because it doesn’t exist.

While WSUS is working, I am unable to download updates. Here is there error
I get in the Application event log :

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Synchronization
Event ID: 364
Date: 9/20/2006
Time: 4:37:09 AM
User: N/A
Computer: GHOST
Description:
Content file download failed. Reason: The server does not support the
necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
requires that the server support the Range protocol header.
Source File:
/msdownload/update/v3-19990518/cabpool/windowsxp-kb890175-x86-hun_fbe352cf862eb2a0273f6b7e8ac9b19a07b980e1.exe
Destination File:
e:\WSUS\WsusContent\E1\FBE352CF862EB2A0273F6B7E8AC9B19A07B980E1.exe.

Any help is much appreciated!

"MShrake" <MShrake@discussions.microsoft.com> wrote in message
news:5A32751E-7478-4AFD-BF15-8413A6D3C744@microsoft.com...
>I have two problems that I've been struggling with for awhile now.
>
> I've installed and reinstalled several times and I can not get the
> WSUSservice and the ContentSyncAgent to show up in the Services window.

The "WSUSservice" as you call it, is listed as "Update Services".

> could not be contacted. Check your server status and ensure that the
> Windows
> Server Update Service is running. Non-running services: ContentSyncAgent,
> WSUSService". There is no was to start the service because it doesn't
> exist.

The "ContentSyncAgent" is an 'internal' service, like the "SelfUpdate"
service.

> Content file download failed. Reason: The server does not support the
> necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
> requires that the server support the Range protocol header.
> Source File:
> /msdownload/update/v3-19990518/cabpool/windowsxp-kb890175-x86-hun_fbe352cf862eb2a0273f6b7e8ac9b19a07b980e1.exe
> Destination File:
> e:\WSUS\WsusContent\E1\FBE352CF862EB2A0273F6B7E8AC9B19A07B980E1.exe.

This is a commonly encountered error in environments with SonicWall
appliances. Search Google Groups in this newsgroup for keywords "SonicWall"
and "Range Protocol Header", or call SonicWall support who has probably
fielded no less than a hundred calls on this issue in the past year.

However, the RPH error is not likely the culprit in causing your "Update
Services" service to shutdown, since that error is uniquely a concern of the
Background Intelligent Transfer Service and WSUS would be oblivious to that
problem.



--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Thanks for the guidance Lawrence! I called Sonicwall but they were no help.
They believe it's something to do with the server running WSUS.

I'll take your advice and continue to search this newsgroup.

Thanks again!


"Lawrence Garvin (MVP)" wrote:

> "MShrake" <MShrake@discussions.microsoft.com> wrote in message
> news:5A32751E-7478-4AFD-BF15-8413A6D3C744@microsoft.com...
> >I have two problems that I've been struggling with for awhile now.
> >
> > I've installed and reinstalled several times and I can not get the
> > WSUSservice and the ContentSyncAgent to show up in the Services window.
>
> The "WSUSservice" as you call it, is listed as "Update Services".
>
> > could not be contacted. Check your server status and ensure that the
> > Windows
> > Server Update Service is running. Non-running services: ContentSyncAgent,
> > WSUSService". There is no was to start the service because it doesn't
> > exist.
>
> The "ContentSyncAgent" is an 'internal' service, like the "SelfUpdate"
> service.
>
> > Content file download failed. Reason: The server does not support the
> > necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
> > requires that the server support the Range protocol header.
> > Source File:
> > /msdownload/update/v3-19990518/cabpool/windowsxp-kb890175-x86-hun_fbe352cf862eb2a0273f6b7e8ac9b19a07b980e1.exe
> > Destination File:
> > e:\WSUS\WsusContent\E1\FBE352CF862EB2A0273F6B7E8AC9B19A07B980E1.exe.
>
> This is a commonly encountered error in environments with SonicWall
> appliances. Search Google Groups in this newsgroup for keywords "SonicWall"
> and "Range Protocol Header", or call SonicWall support who has probably
> fielded no less than a hundred calls on this issue in the past year.
>
> However, the RPH error is not likely the culprit in causing your "Update
> Services" service to shutdown, since that error is uniquely a concern of the
> Background Intelligent Transfer Service and WSUS would be oblivious to that
> problem.
>
>
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
>

"MShrake" <MShrake@discussions.microsoft.com> wrote in message
news:32F521AC-BB28-4276-8943-4B381D7D2D42@microsoft.com...

> Thanks for the guidance Lawrence! I called Sonicwall but they were no
> help.
> They believe it's something to do with the server running WSUS.

Call back and get a competent support tech... there /are/ people at
SonicWall that know about this issue, because I, personally, can count about
50 incidents in the past year discussed in this newsgroup alone. Many of
which were resolved as a result of telephone calls to SonicWall. In fact, it
was poster(s) in this newsgroup who first 'educated' SonicWall that they had
a major issue with the default configuration of their appliances.

Here's a composite of one variation of the 'fix', which I dug out of my own
archives, from messages posted in December, 2005. (Obviously I never got
around to updating my website with this information.)

>> Here is how we fixed the SonicWALL.
>>
>> Two of the SonicWALL's security services were interfering with the HTTP
>> 1.1
>> Range protocol header. These services are "Gateway Anti-Virus" and
>> "Anti-Spyware." With either one of those two SonicWALL services enabled,
>> downloads by the WSUS server failed. The "Intrusion Prevention" service
>> and
>> other SonicWALL security services did not affect this one way or the
>> other.
>>
>> The cure was to create client exclusions for the WSUS server for the
>> Gateway
>> Anti-Virus and Anti-Spyware services. (See page 30 of the SonicWALL
>> Anti-Spyware Administrator's Guide.)

>Thank you for the info about the 'cure' now being published in the formal
>SonicWall documentation. I'll add a note to my article that specific
>instructions for resolution can be found in that publication.



--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....