Richie Nicholas
asked on
WSUS- Event id 364- Content file download failed, Reason: The connection was closed prematurely. Server 2016
I have setup a new server and am running WSUS 10.0.14393.0 on Windows Server 2016. Updates will download but will stop after a while.
Current WSUS status is
- Updates needing files : 5928
- Downloaded 45,683.32MB of 258,732.17MB.
It has been stuck at this for more than a week. I can see network activity occasionally which could range to a couple of gigs every 6-8 hours but the WSUS status does not change
On checking the Application event logs, i can see. Event id 364 Errors
" Content file download failed.
Reason: The connection was closed prematurely.
Source File: /msdownload/update/softwar
Destination File: D:\WSUS\WsusContent\82\433
Event id 10032 Errors
The server is failing to download some updates.
I have updated BITs to run in the foreground.
the server has been excluded from the internal Firewall, https inspection and Caching.
I have also tried removing and adding the WSUS role and WID database.
Has anyone come across something similar?
cheers
Current WSUS status is
- Updates needing files : 5928
- Downloaded 45,683.32MB of 258,732.17MB.
It has been stuck at this for more than a week. I can see network activity occasionally which could range to a couple of gigs every 6-8 hours but the WSUS status does not change
On checking the Application event logs, i can see. Event id 364 Errors
" Content file download failed.
Reason: The connection was closed prematurely.
Source File: /msdownload/update/softwar
Destination File: D:\WSUS\WsusContent\82\433
Event id 10032 Errors
The server is failing to download some updates.
I have updated BITs to run in the foreground.
the server has been excluded from the internal Firewall, https inspection and Caching.
I have also tried removing and adding the WSUS role and WID database.
Has anyone come across something similar?
cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Don
Run the reset first
ASKER
Hi Vitor,
Does it matter if I am not using SQL for WSUS and WID instead?
what does changing "AutoClose to False " actually do?
Does it matter if I am not using SQL for WSUS and WID instead?
what does changing "AutoClose to False " actually do?
Does it matter if I am not using SQL for WSUS and WID instead?Yes it matters. My solution only works for a SQL Server database. I don't know if WID have similar configuration, though.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The article link I posted covers both WID and SQL databases. So would the reset command, I assume, although I've never tried that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Many thanks to all for your recommendations.
I have tried them and finally managed to get WSUS working now.
Below are some of the things I performed
1. Set AutoClose to False
a. Install SQL Server Management Studio on the WSUS server.
b. Connect to the WSUS database, Enter \\.\pipe\MICROSOFT##WID\ts
c. Expand databases and right click the appropriate database, (in my case it was SUSDB) and select Properties
d. Select Options . On the right hand side of the window, scroll to find the Automatic section and set Auto Close to
False ( default is True)
2. Run wsusutil.exe reset
3. Some other things that were done (related to my environment)
a. Exclude server from https inspection.
b. exclude the server from caching.
c. exclude Policy-based forwarding.
d. Exclude server from any file blocking
Once again, many thanks to all.
I have tried them and finally managed to get WSUS working now.
Below are some of the things I performed
1. Set AutoClose to False
a. Install SQL Server Management Studio on the WSUS server.
b. Connect to the WSUS database, Enter \\.\pipe\MICROSOFT##WID\ts
c. Expand databases and right click the appropriate database, (in my case it was SUSDB) and select Propertiesd. Select Options . On the right hand side of the window, scroll to find the Automatic section and set Auto Close to
False ( default is True)
2. Run wsusutil.exe reset
3. Some other things that were done (related to my environment)
a. Exclude server from https inspection.
b. exclude the server from caching.
c. exclude Policy-based forwarding.
d. Exclude server from any file blocking
Once again, many thanks to all.
I'm glad that you've fixed the issue.
Please close this question by accepting the comment or comments that helped you reaching the solution so it can be used in the future by someone with a similar issue.
Cheers
Please close this question by accepting the comment or comments that helped you reaching the solution so it can be used in the future by someone with a similar issue.
Cheers