Error 1611: -106

[jldwyer]

I have one Win2012 R2 – HyperV host server getting this error when searching for MS Updates:

Windows Update: -106G: Update search completed with errors: -2145123271

I don’t see any info on the -2145123271 error result. Any ideas?

[doug]

Please have a look at this posting

[doug]

For the following error:

Windows Update: Error 1620: -106. Failure

Windows Update: -106G: Update search completed with errors: -2145123271

---

In the case where this error occurs when using a local WSUS (as opposed to using ‘Windows Update’ or ‘Microsoft Update’ public servers), one possible solution is described below:

The problem appears to be:

WARNING: The server returned HTTP status code ‘413 (0x19D)’ with text ‘Request Entity Too Large’.

WARNING: MapToSusHResult mapped Nws error 0x803d0000 to 0x80240439

The solution described at the following link suggests:

https://social.technet.microsoft.com/Forums/en-US/df4db9d0-9620-4af1-b514-6767951b2f18/http-413-request-entity-too-large-during-update-scan?forum=configmanagersecurity

After increasing IIS setting uploadReadAheadSize on WSUS server from 49152 to 491521 the missing updates (KB3213986, KB3214628) is installing properly on 1607 client.

Launch “Internet Information Services (IIS) Manager”

Expand the Server field

Expand Sites

Select the site you want to make the modification for. (WSUS Administration)

In the Features section, double click “Configuration Editor”

Under “Section” select: system.webServer -> serverRuntime

Modify the “uploadReadAheadSize” section (This value should be in Bytes)

Click Apply

Do an IIS Reset

[doug]

In the next version of BP we have modified the code so that BP is able to successfully ignore this particular error ( -2145123271 ) and continue, at least in certain instances. Release date TBD, but it should be not too far off.

-Doug

[stevenfoo]

Hi Doug,

We also encounter this in our 2 x 2012 R2 servers.

These are Citrix Server. I am trying to understand how to I set uploadReadAheadSize from 49152 to 491521.

These 2 are not WSUS servers, only Citrix.

Please advice.

In these servers in the IIS, it only contain the sites

AGServices

aspnet_client

Citrix

Director

RDWeb

Please advice.

BTW: I am running on version 2018.3.28.16.13

[doug]

The uploadReadAheadSize adjustment is to be made on the WSUS server, not on the target servers, even though you only see the error on particular target servers. If you are not using WSUS but instead are getting updates directly from Windows Update or Microsoft Update, then this potential fix does not apply to you.

-Doug

[stevenfoo]

Hi Doug,

So how do I overcome it, since my setup is direct update from Windows/Microsoft update?

The error is still there.

Thank you.

[doug]

I don’t have a solution for you to overcome it in the current version of BP. In the next version of BP, BP attempts to ignore this particular error (Windows Update: -106G: Update search completed with errors: -2145123271) and continue. However, that’s not a guarantee that it will always be able to successfully ignore it, but it might solve the issue in your case.

-Doug

[stevenfoo]

Hi Doug,

I am able to by pass the issue with offline mode using the downloaded Microsoft offline scan file.

I selected both cache + offline mode and it was working again.

The Microsoft offline scan file was downloaded automatically by BatchPatch into the cache folder for the first time, how about in the future. For example, we want to update the entire server again once in a month, will the new Microsoft offline scan file be downloaded automatically and replace existing one? Or do we need to manually download it into the cache folder ?

[doug]

If BatchPatch detects that there is a new WsusScn2.cab file available from Microsoft, it will download it and replace the previous one.

[Author]

Posts