BatchPatch Forums Home › Forums › BatchPatch Support Forum › Issue with "Update not downloaded/cached"
- This topic has 8 replies, 3 voices, and was last updated 6 years, 10 months ago by doug.
-
AuthorPosts
-
January 9, 2018 at 4:41 am #8890mrechterParticipant
I am having an issue with just a handful of servers completing their Important updates (all other servers finish completely).
The updates appear to be copied into the Windows update cache but then the installer can not see them?
For example, the file in the local server BatchPatch Cache is “ndp40-kb2972215-x64_e6cab4d934d4c425745a5862d50a17e55a7a9659.exe” and then I can see a “e6cab4d934d4c425745a5862d50a17e55a7a9659” named file in the Windows Update Software Distribution Download folder after the Update execution on the remote server(I assume this is what it is supposed to do?)
Any ideas on what I can try next?
I have tried the Override cached files setting, and wiping the Windows Updates Download folder.
Here is the remote agent log:
SERVER 01/09/2018 15:22:19
::Begin online search – Server Selection: Default
The search query “ImportantOnly” returned 10 update(s):
1> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972215) (25 MB) (2014-09-09) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/2972215
2> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972106) (3 MB) (2014-10-14) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/2972106
3> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2978125) (2 MB) (2014-11-11) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/2978125
4> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2894842) (10 MB) (2015-04-14) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/2894842
5> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3037578) (10 MB) (2015-04-14) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/3037578
6> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3023221) (4 MB) (2015-05-12) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/3023221
7> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3032662) (2 MB) (2015-05-12) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/3032662
8> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3074547) (2 MB) (2015-09-08) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/3074547
9> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3098778) (9 MB) (2015-11-10) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/3098778
10> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3097994) (2 MB) (2015-11-10) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/3097994
::End search
::Begin filtering collection
adding> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972215)
adding> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972106)
adding> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2978125)
adding> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2894842)
adding> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3037578)
adding> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3023221)
adding> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3032662)
adding> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3074547)
adding> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3098778)
adding> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3097994)
::End filtering collection
::Begin copying files to Windows Update cache
1> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972215)
1> Deleting C:Program FilesBatchPatchcachemsipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Succeeded
2> Deleting C:Program FilesBatchPatchcachendp40-kb2972215-x64_e6cab4d934d4c425745a5862d50a17e55a7a9659.exe :: Copy To Cache: Succeeded
2> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972106)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Skipped – File previously cached
2> Deleting C:Program FilesBatchPatchcachendp40-kb2972106-x64_4631da8d6454b5680c0159b5254c15d54a8184e1.exe :: Copy To Cache: Succeeded
3> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2978125)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb2978125-x64_e1fcbbd130e6cf4e7bf2694b8463d040f73578aa.exe :: Copy To Cache: Succeeded
4> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2894842)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb2894842-v2-x64_c28bc92e42f9969656b57da03d7665ac78bff2de.exe :: Copy To Cache: Succeeded
5> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3037578)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb3037578-x64_1e83d8a769ac9284f19ddde85871a50a1b159577.exe :: Copy To Cache: Succeeded
6> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3023221)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb3023221-x64_ac6d5bdc6fa3c550abbed7f4ae8e75c3298e2e9f.exe :: Copy To Cache: Succeeded
7> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3032662)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb3032662-x64_43081b43f1e729d2f514e242a03aa7b47605eb1a.exe :: Copy To Cache: Succeeded
8> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3074547)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb3074547-x64_906872fe520815f5d1317a0a245beaf82bbe59ac.exe :: Copy To Cache: Succeeded
9> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3098778)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb3098778-x64_f88fc40c19e91a7c1e86db2bacbe1d2c28251fc4.exe :: Copy To Cache: Succeeded
10> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3097994)
1> msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
2> Deleting C:Program FilesBatchPatchcachendp40-kb3097994-x64_82412f8c4d509a3e20ef430bc9407fca69910b32.exe :: Copy To Cache: Succeeded
::End copying files to Windows Update cache
::Begin adding downloaded items to installer collection
skipped> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972215) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2972106) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2978125) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB2894842) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3037578) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3023221) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3032662) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3074547) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3098778) – Reason: Update not downloaded/cached
skipped> Security Update for Microsoft .NET Framework 4 on Windows Vista, Windows 7, Server 2008, Server 2008 R2 x64 (KB3097994) – Reason: Update not downloaded/cached
::End adding downloaded items to installer collection
There are no updates available for installation
SERVER 01/09/2018 15:23:37
January 9, 2018 at 5:10 am #10264dougModeratorThis is peculiar. Considering all of the entries that state the following…
msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe :: Copy To Cache: Failed. HRESULT: -2147024894
…it seems that these .NET updates all utilize the same file (in conjunction with a secondary file that is specific to the particular update and not shared). The -2147024894 means ‘ERROR_FILE_NOT_FOUND’. This is happening because the file is there for the first update, but then BatchPatch deletes it from the target computer temp folder after it successfully caches the file for the first update in the list, and then BP is not able to cache that file for the rest of the updates because it has been deleted. BP does not expect that two updates would have the same filename, so BP deletes the files as it caches them, but apparently there are cases where two updates will utilize the same exact file.
I would suggest trying the following:
1. Delete the files in your cache directory on the BatchPatch computer. Or you can temporarily point the cache location to an empty folder so that when you attempt again BatchPatch will download the update files anew. The goal here is just to make sure you get fresh files in case one or more of the files that currently exist in your BatchPatch cache are corrupt in any way that is preventing them from installing.
2. Check the box ‘Tools > Settings > Windows Updates > Recopy/overwrite updates that have already been cached on target hosts’ You should leave the box checked until all of these updates have been installed and the problem has been resolved.
3. With the above box checked, use BatchPatch filtering to install just a single .NET update at a time. Use ‘Actions > Windows Updates > Filter which updates are included/excluded’ to include just one of the .NET updates at a time. I suspect if you use filtering to install just one update at a time you won’t have any problems, though I can’t say for sure because I have never seen this type of situation before.
-Doug
January 9, 2018 at 7:25 am #10265mrechterParticipantThanks Doug.
Just filtering to the a single update did work as you suggested.
Doing this one at a time for each .Net security update (some servers need 14…) would be tedious, so I have now just gone to a much newer .Net framework version on each server instead (by Deployment 😀 ) so I don’t have to apply each of these older updates.
Matt
January 9, 2018 at 5:37 pm #10266dougModeratorThanks, Matt. Good to know the one-at-a-time method worked. However, I agree it was probably a good idea to just update the framework altogether, so I’m glad you got it all worked out.
-Doug
January 17, 2018 at 7:24 pm #10247huibwParticipantHi Doug,
Is it possible to reconsider a workaround for this issue? We’ve run into the same issue and it’s not an option for us to go to a newer/different .NET framework. Doing them all one by one for many images in many datacenters is not an really a workable option either.
Thanks,
Huib
January 17, 2018 at 7:39 pm #10248dougModeratorTo be clear, you would not have to do them one by one for each target. You could apply one update to ALL targets at the same time. Then apply the next update to ALL targets at the same time. And so on. It really should not take very long. Also, this would only occur when using BatchPatch in cached mode, so if your computers have internet access or access to WSUS, then you could disable cached mode and apply these updates in one action with the standard Windows Update methods in BatchPatch.
In the case that Matt described he was applying updates that go back more than 3 years. This was only an issue for him because of being so out of date. If you are staying relatively up to date, then it’s never going to be an issue. Huib, are you also applying updates from as far back as 3+ years ago?
Another option for deployment is to download the desired/needed .MSU (or .MSI or .MSP etc) update files from the Windows Update catalog from Microsoft. Then you can deploy those all at one time using the ‘Deployment’ feature in BatchPatch, as described in this tutorial:
Remotely Install Multiple .MSU Files (or .MSI and .MSP files) to Numerous Computers
In a future version of BP we will plan to update the behavior so that instead of deleting files individually as we cache them we will delete them after all updates have been cached, which will prevent this issue from occurring. However, for the time being it’s a very rare issue that as far as we know only affects you if you are trying to apply numerous old .NET security updates at the same time. This posting is the first time we have ever heard of this happening to anyone. Most users will not be 3+ years behind on applying security updates.
January 17, 2018 at 8:19 pm #10237huibwParticipantHi Doug,
Thank you for your response!
Yes, blush, we have images that are 3+ years behind. Primarily because we didn’t use to update .NET framework because of other dependencies but now we do. Okay, we’ll have to use the “deploy” function. Is there a way to export deployments? I do see I have 12 .NET updates and to recreate 12 deployments in 15 datacenters I also a lot of work.
Thanks
January 17, 2018 at 8:28 pm #10239dougModeratorTools > Export
Tools > Import
January 17, 2018 at 8:30 pm #10240huibwParticipantThat was too simple 🙂 Many thanks!
-
AuthorPosts
- You must be logged in to reply to this topic.