Hi guys,
During some WSUS optimization, I suspect that a SQL entry for an update was removed and as a result the application is failing expiry.
Unlike, https://patchmypc.net/forum/index.php?topic=2122.msg5603#msg5603, the files exist in the content share.
The error message in the logs related to an error verifying the signature of the update CAB file.
Would you have any advice for me as to how to remove this error?
An error occurred while expiring an update: Verification of file signature failed for file: \\<server_name>\UpdateServicesPackages\df9743c8-afda-413b-abb3-118686312b56\e46be2c6-a672-42d6-992d-8ccfbf2e2bfc_1.cab
Thanks in advance!
J
PS:
<3 PatchMyPC
Hey!
We will be making a video to resolve this issue soon and post it up to YouTube. This does seem to happen some when custom WSUS cleanups are run.
The easiest workaround is to manually create the folder it's looking for and copy a CAB from another folder and rename it to match the CAB it's looking for:
\\<server_name>\UpdateServicesPackages\
df9743c8-afda-413b-abb3-118686312b56\
e46be2c6-a672-42d6-992d-8ccfbf2e2bfc_1.cabLet me know if that makes sense? Once that's done the update should expire and you can remove the folder/cab you manually created to allow the update to expire.
If you want, we could jump on a call and walk through the process.
Thanks
- Justin
Quote from: v1_longj on August 13, 2018, 05:27:27 AM
Hi guys,
During some WSUS optimization, I suspect that a SQL entry for an update was removed and as a result the application is failing expiry.
Unlike, https://patchmypc.net/forum/index.php?topic=2122.msg5603#msg5603, the files exist in the content share.
The error message in the logs related to an error verifying the signature of the update CAB file.
Would you have any advice for me as to how to remove this error?
An error occurred while expiring an update: Verification of file signature failed for file: \\<server_name>\UpdateServicesPackages\df9743c8-afda-413b-abb3-118686312b56\e46be2c6-a672-42d6-992d-8ccfbf2e2bfc_1.cab
Thanks in advance!
J
PS:
<3 PatchMyPC
OK. Sorry Justin. Seems I was looking in the wrong path first time round.
Let's put it down to my early morning...
Followed your steps exactly, also as in the other thread, and all sorted now.