Server 2016 servers Access Denied (0x80070005) after failed patching, unable to resolve issues using DISM.

P

PubstarHero

So we were having some serious network and disk IO issues at our place when we had patching, and it seems to have hosed our 2016 servers exclusively. All patches fail with Access Denied (unable to extract files from cab)

CBS erros from patching:

2018-06-19 14:06:20, Info DPX MoveFileExW failed, source: \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\inst\$dpx$.tmp\eccfbbf4a4045b418b65b469ef359b8c.tmp, destination: \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\inst\amd64_microsoft-windows-htmlhelp_31bf3856ad364e35_10.0.14393.2273_none_3e0ec265df529d5b\hh.exe, hr 0x80070005
2018-06-19 14:06:21, Info CBS DPX progress: 27
2018-06-19 14:06:22, Info CBS DPX progress: 27
2018-06-19 14:06:23, Info DPX DpxMoveFileExW failed, source: \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\inst\$dpx$.tmp\eccfbbf4a4045b418b65b469ef359b8c.tmp, destination: \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\inst\amd64_microsoft-windows-htmlhelp_31bf3856ad364e35_10.0.14393.2273_none_3e0ec265df529d5b\hh.exe, hr 0x80070005

____________________________________________________________________


2018-06-19 14:09:32, Info DPX File could not be expanded, Source=amd64_microsoft-windows-htmlhelp_31bf3856ad364e35_10.0.14393.2273_none_3e0ec265df529d5b\hh.exe, Target=(null), status=0x80070005
2018-06-19 14:09:32, Info DPX ProvideRequestedDataByFile failed, Response file Name: \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\inst\Cab_1_for_KB4284880.cab
2018-06-19 14:09:32, Info DPX Ended DPX phase: Apply Deltas Provided In File
2018-06-19 14:09:32, Info DPX DpxException hr=0x80070005 code=0x020102
2018-06-19 14:09:32, Info DPX Ended DPX phase: Resume and Download Job
2018-06-19 14:09:32, Info DPX DpxException hr=0x80070005 code=0x020217
2018-06-19 14:09:32, Info CBS Failed to Resume job in DpxThreadResumeJobProc [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Info CBS Failed to extract files from cabinet \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\inst\Cab_1_for_KB4284880.cab [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Info CBS Failed to extract all files from cabinet \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\inst\Cab_1_for_KB4284880.cab [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Info CBS Failed to extract payload from cabinets [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Info CBS Failed to extract all files from cabinet \\?\C:\Windows\SoftwareDistribution\Download\0fdb1b5a73b2d7cb4253fc7e9c65baa2\Windows10.0-KB4284880-x64.cab [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Info CBS Failed to add package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2312.1.14 [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Info CBS Failed to plan execution. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Error CBS Failed to process single phase execution. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-19 14:09:32, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2312.1.14, status: 0x80070005, failure source: CBS Other, start state: Absent, target state: Absent, client id: WindowsUpdateAgent
2018-06-19 14:09:32, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]



I did try to rename the softwaredistribution folder as suggested around here before, but that didn't work.

I ran a dism /online /cleanup-image /restorehealth /source:wim:d:\install.wim:1 /limitaccess (as these machines do not have internet access) using the WIM file I got off of our 2016 install media and I received the following information below.



___________________________________________________________________________

2018-06-21 10:40:59, Warning CBS Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-06-21 10:40:59, Info CSI 00000007@2018/6/21:17:40:59.546 Corruption detection complete. numCorruptions = 1, Disp = 1.
2018-06-21 10:41:00, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2018-06-21 10:41:01, Info CSI 00000008@2018/6/21:17:41:00.999 CSI Transaction @0x173a0a80220 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.30673277_1382187657:1/'

2018-06-21 10:41:01, Info CSI 00000009@2018/6/21:17:41:01.046 CSI Transaction @0x173a0a80220 destroyed
2018-06-21 10:41:01, Info CBS Repr: CSI Store check completes
2018-06-21 10:41:03, Info CBS Could not assert exclusive access to the file found in the sandbox [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-21 10:41:03, Error CBS Failed to look for file WinSxS\amd64_ram-site-fs_31bf3856ad364e35_10.0.14393.0_none_53f77862a9c86500\upload.aspx in some alternate sources [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-06-21 10:41:03, Info CBS Repr: Not able to find replacement file for component amd64_ram-site-fs_31bf3856ad364e35_10.0.14393.0_none_53f77862a9c86500, file upload.aspx from any local source
2018-06-21 10:41:03, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2018-06-21 10:41:03, Info CBS Exec: Clients specified using local source only.
2018-06-21 10:41:03, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.
2018-06-21 10:41:03, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-06-21 10:41:03, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-06-21 10:41:03, Info CBS Ensure CBS corruption flag is clear
2018-06-21 10:41:03, Info CBS
=================================
Checking System Update Readiness.
(p) CSI Payload Corrupt amd64_ram-site-fs_31bf3856ad364e35_10.0.14393.0_none_53f77862a9c86500\upload.aspx
Repair failed: Missing replacement payload.
Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 1
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 1
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
Total Operation Time: 4165 seconds.

2018-06-21 10:41:03, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x0 [S_OK]
2018-06-21 10:41:03, Info CBS Count of times corruption detected: 1
2018-06-21 10:41:03, Info CBS Seconds between initial corruption detections: -1
2018-06-21 10:41:03, Info CBS Seconds between corruption and repair: -1
2018-06-21 10:41:03, Info CBS IOCTL_STORAGE_QUERY_PROPERTY query failed
2018-06-21 10:41:03, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2018-06-21 10:41:03, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-06-21 10:41:04, Info CBS Reboot mark cleared
2018-06-21 10:41:04, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2018-06-21 10:41:04, Info CBS Winlogon: Deregistering for CreateSession notifications
2018-06-21 10:41:04, Info CBS Exec: Processing complete, session(Corruption Repairing): 30673277_1382187657 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-06-21 10:41:04, Error CBS Session: 30673277_1382187657 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-06-21 10:41:04, Info CBS Session: 30673277_1382187657 finalized. Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-06-21 10:41:04, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]

_______________________________________________________


I'm at a loss right now. I can revert most of our machines with a snapshot and resolve the issue, but if I cannot get this working, it means rebuilding 3 of our DC's and seeing if our weekly snapshot restores end up hosing our database servers.

Continue reading...
 
Back
Top Bottom