WSUS event 364 Content file download failed. The user has not logged on to the network. The specified service does not exist.

Henderson, Norm 1 Reputation point

I have set up a WSUS server on Win 2019, it downloaded many GB of updates and then stopped with a number of updates needed. The specific error is: Content file download failed. Reason: The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. (Exception from HRESULT: 0x800704DD) Source File: /d/upgr/2020/12/windowsupdatebox_23eacde287c7c0a824d4af36ff8b6494472c1bda.exe Destination File: C:\Program Files\Update Services\LogFiles\WSusTemp\23EACDE287C7C0A824D4AF36FF8B6494472C1BDA.exe I can see the full URL of the source file in SoftwareDistribution.log and I am able to download it, to the WSUS server, using a browser. That eliminates the usual issues with proxy server (the WSUS server doesn't go through one), firewall (wide open for outbound HTTP), and other connectivity issues. I am not using HTTPS. The fact that a good percentage of needed updates WERE downloaded, and clients are picking them up, eliminates the usual issues of permissions on WsusContent. Via bitsadmin.exe, I can see that when I tell WSUS to "Retry Download" there are a large number of jobs created (167 jobs for 5 updates) but all "SUSPENDED 0/0 0/0". There are no HTTP requests whatever to the Internet, although there are periodic HTTPS requests Here is a sample: GUID: {6A6747CE-EFFC-4F89-BEB4-397BD37E8A1A} DISPLAY: '63063b79-8035-4e80-8f88-fcad239311e1' TYPE: DOWNLOAD STATE: SUSPENDED OWNER: DOM\wsus PRIORITY: NORMAL FILES: 0 / 0 BYTES: 0 / 0 CREATION TIME: 2021-03-08 12:20:16 PM MODIFICATION TIME: 2021-03-08 12:20:16 PM COMPLETION TIME: UNKNOWN ACL FLAGS: NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3 RETRY DELAY: 600 NO PROGRESS TIMEOUT: 1209600 ERROR COUNT: 0 PROXY USAGE: PRECONFIG PROXY LIST: NULL PROXY BYPASS LIST: NULL DESCRIPTION: JOB FILES: NOTIFICATION COMMAND LINE: none owner MIC integrity level: HIGH owner elevated ? true Peercaching flags Enable download from peers :false Enable serving to peers :false CUSTOM HEADERS: NULL I tried bitsadmin /resume for a couple of the jobs and got "Unable to resume job - 0x80200003" - saying the job is empty, has no files... There is a particularity here. I am running wsusservice under a domain account because, the content is on a NAS drive. It has to be that way, because if I were to store it locally on the (virtualized) WSUS server, it would be far too large to create snapshots. I set the IIS WsusPool application pool identity, and the WSUS Administration site physical path accordingly (with the UNC) and created a SPN, which is allowing the clients to connect and retrieve content. The NAS (Synology) is a Domain Member. The entire NAS share for WSUS, allows R/W access for the wsus AD account, the machine account of the WSUS server, and "Domain Computers". I read in another post that WsusContent isn't supported on a network drive although, I didn't find that in the actual documentation, nor does it seem to be a necessary restriction. 1) What the error message DOES NOT say, is WHICH user is not logged in to WHICH network, nor WHICH service "does not exist" ? 2) I don't understand why there are so many BITS jobs nor why they are SUSPENDED? And why do they have no files? 3) Is there a definitive way to prove if, somehow, permissions on the network drive are the problem?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,627 questions
{count} votes