Hey Barry,
Make sure that the security descriptor on the BITS service hasn't been
changed by comparing the broken server with a working one. You can use sc.exe
to do this.
For example:
D:\>sc sdshow bits
D

A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLO CRSDRCWDWO;;;BA)(A;;CCLCSWLOCR
RC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
If the output is different from the working box you can reset it with sc and
then attempt to start the service.
D:\>sc sdset bits <correct sddl output>
Good Luck.
"Barry" wrote:
>
> "Net_Man" <> wrote in message
> news:0E030DB5-E782-439F-BB22-...
> > Hi,
> > I have wsus server with 2003 sp1.
> > All computers what i have tested will be shown in wsus server, and
> > etc...etc.
> > BUT when pc should check updates, or if i run wuauclt /detectnow, i
> > allways
> > get same error...
> >
> > The Background Intelligent Transfer Service service terminated with
> > service-specific error 2147500053 (0x80004015).
> >
> > First it will start BITS
> > The Background Intelligent Transfer Service service was successfully sent
> > a
> > start control
> >
> > then it succesfully informing:
> > The Background Intelligent Transfer Service service entered the stopped
> > state
> >
> > And then i got eroormessage:
> > The Background Intelligent Transfer Service service terminated with
> > service-specific error 2147500053 (0x80004015).
> >
> > Any ideas?
> >
>
> only thing i can find is "The Remote Procedure Call service was using a
> different account than the Local System Account. I changed the Log On as
> Local System Account, rebooted, then started The Background Intelligent
> Transfer Service."
>
> from a quick ish search
>
>
>