SBS 2008 - WSUS - Bits - Transient Error

We have a Windows 2008 SBS server which has WSUS installed, however the download status is stuck on downloading 223.27Mb of 4,591.86Mb and has been for the past month.

The server is on a network and has direct access to the internet, though there is also a proxy on the network.
In bitsadmin it lists 10 jobs along the lines of:
{90230019-8EF6-44BE-8AF7-4E5506A56FF7} 'f12e5174-33ff-4a41-8eee-0cd27b46ccc5' TRANSIENT_ERROR 0 / 1 0 / UNKNOWN
{986EDD08-7526-4F33-993E-92D0B3C7E7CA} 'f55f039e-67d0-47cc-afa4-5b03fe5d19fc' TRANSIENT_ERROR 0 / 1 0 / UNKNOWN

I have tried resuming these through bitsadmin running under the system account using psexec /s and whilst they resume they then show a transient error immediately after, i have tried showing the proxy settings for the job, they were orginally using no proxy, i have set the proxy settings in WSUS, cleared the bits jobs and restarted WSUS the jobs now show the proxy settings but still do not download and still show the same error.

Using wireshark when i resume a job i can't see anything that looks bits/http related, also on the proxy server there are not requests logged for the host related to windows update.

I have tried reinstalling WSUS using a fresh database and data folder and still get the same errors, i have tried manually submitting jobs through bits and they download fine.

I have tried enabling bits logging to an event log file however the messages in here appear to contain no readable/relevant information:
e.g. "GUID=09ecf323-51dd-2524-a519-b15654cfd8fb (No Format Information found)."

Any suggestions on how to get this working would be most appreciated, we had a 2003 SBS server before in the same network configuration and didn't have any problems with WSUS.

The update services version number is 3.2.7600.226

Many Thanks,
Who is Participating?
mcuk_stormConnect With a Mentor Author Commented:
Thank you for your suggestion, unfortunately this didn't solve the problem either, as i could add the exact same src and dst into my own bits job and it worked i tried changing the update services service over to my user account which caused more problems but bits didn't seem to complain as much, after another quick search i found  It appears the error was caused by the network service user not having read permission to the drive root where the wsuscontent folder is. After setting the permissions and changing the service back to the Network Service account it all seems to be running fine and bits has labelled the jobs as TRANSFERRING.
Donald StewartNetwork AdministratorCommented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.