FWIW.... WSUS is not supported when storing the content store on a network
The BITS service is actually what's trying to write the content files, and
since the BITS service runs under the Local System account, it's probably a
design consideration that "Local System" will not be able to write to a
network mapped resource.
Having said that, review the NTFS permissions documented in
and make sure they're matching at the point of your share
..... just on the off chance that my interpretation is incorrect
or it's one of those "unsupported, but it does work" sort of scenarios. :-)
"Toby" <***@discussions.microsoft.com> wrote in message news:469A957E-FC85-4E5Dfirstname.lastname@example.org...
| Hello.. I am experiencing this same issue on my WSUS box. I have checked
| permissions and everything seems right. Here is the evenlog entry I
| Event ID: 364
| Content file download failed. Reason: Error calling
| [kernel32.dll]:CreateDirectory(\\cksdupdate\e$\wsus\wsuscontent\48) Source
| File: Destination File: .
| I am receiving this event on multiple directories under the wsuscontent
| folder. I checked the permissions and "Network service" has full control
| which are inherited from above. The directory listed in the events are
| the wsuscontent folder, so they are being created.
| "????" wrote:
| > Hi,
| > My WSUS server reporting the following error:
| > Source: Windows Serer Update
| > Category: Synchronization
| > Evend ID: 364
| > Description:
| > Content file download failed. Reason: Error calling
| > [kernel32.dll]:CreateDirectory(d:\WSUS\WsusContent\81} Source File:
| > Destination file:
| > Any help! thanks