Recently my gulp live reload broke like so:
ws://x.x.x.x:8080/LiveReload' failed: Error during WebSocket handshake: Unexpected response code: 200
Even though nothing changed, I noted patches had been installed over the weekend. After looking through which files were updated, I noticed that KB 3109103 patched Wshrm.dll. I was unable to find much useful information on this DLL, but after looking into the description it appeared to have a lot to do with sockets: Windows Sockets Helper DLL for PGM.
After removing the update & rebooting my web sockets started working again.
Monday, December 14, 2015
Wednesday, December 2, 2015
MSI Installation Failure - 1328. Error applying patch.
Wow this one killed me. After attempting to determine why I simply could not install Adobe DC with our package from enterprise (though only on certain machines) I really had to dig into this one. The package would first fail with a generic:
Product: Adobe Acrobat DC - Update 'Adobe Acrobat DC (15.006.30060)' could not be installed. Error code 1603.
Knowing that this is a very generic error code, I began digging through a "l*v" generated log to determine the true source of the failure.
MSI (s) (84:88) [14:36:07:292]: Product: Adobe Acrobat DC -- Error 1328.Error applying patch to file C:\Config.Msi\PT2AFE.tmp. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor. System Error: -1072807676
Error 1328.Error applying patch to file C:\Config.Msi\PT2AFE.tmp. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor. System Error: -1072807676
Aha, so it appeared that for some reason the MSP packaged with the MSI was failing to be applied. Scrolling up through the log I was able to identify the actual failing file itself:
MSI (s) (84:88) [14:36:07:292]: Executing op: CacheBaselineFile(Baseline=0,FileKey=adobe_caps.dll,FilePath=C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\adobe_caps.dll,,Existing=0)
MSI (s) (84:88) [14:36:07:292]: Executing op: PatchApply(PatchName=adobe_caps.dll,TargetName=C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\adobe_caps.dll,PatchSize=81904,TargetSize=552632,PerTick=0,,FileAttributes=16384,PatchAttributes=0,CheckCRC=0)
MSI (s) (84:88) [14:36:07:292]: Patch for file 'C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\adobe_caps.dll' is redirected to patch 'C:\Config.Msi\PT2AFE.tmp' instead.
At this point I needed to dig deeper--I know that the package installed perfectly on other machines, so why not this one? Firing up Procmon, I was able to see that msiexec.exe was hitting the "adobe_caps.dll" file here:
C:\Windows\Installer\$PatchCache$\Managed\68AB67CA3301FFFF7706E0F060571500\15.6.30033
Being unfamiliar with the "$PatchCache$" folder, I did a little research and found that files can be cached here (and only cached ONCE) for any MSP file installed on your machine. Since the installer was being pulled across the network, it looks like a network hiccup occurred and a corrupt version of the "adobe_caps.dll" (showing as 0 KB) was stored in cache.
To resolve the error, all that needed to be done was to remove the entire "68AB67CA3301FFFF7706E0F060571500" folder & reinstall! Bam!!
Product: Adobe Acrobat DC - Update 'Adobe Acrobat DC (15.006.30060)' could not be installed. Error code 1603.
Knowing that this is a very generic error code, I began digging through a "l*v" generated log to determine the true source of the failure.
MSI (s) (84:88) [14:36:07:292]: Product: Adobe Acrobat DC -- Error 1328.Error applying patch to file C:\Config.Msi\PT2AFE.tmp. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor. System Error: -1072807676
Error 1328.Error applying patch to file C:\Config.Msi\PT2AFE.tmp. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor. System Error: -1072807676
Aha, so it appeared that for some reason the MSP packaged with the MSI was failing to be applied. Scrolling up through the log I was able to identify the actual failing file itself:
MSI (s) (84:88) [14:36:07:292]: Executing op: CacheBaselineFile(Baseline=0,FileKey=adobe_caps.dll,FilePath=C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\adobe_caps.dll,,Existing=0)
MSI (s) (84:88) [14:36:07:292]: Executing op: PatchApply(PatchName=adobe_caps.dll,TargetName=C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\adobe_caps.dll,PatchSize=81904,TargetSize=552632,PerTick=0,,FileAttributes=16384,PatchAttributes=0,CheckCRC=0)
MSI (s) (84:88) [14:36:07:292]: Patch for file 'C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\adobe_caps.dll' is redirected to patch 'C:\Config.Msi\PT2AFE.tmp' instead.
At this point I needed to dig deeper--I know that the package installed perfectly on other machines, so why not this one? Firing up Procmon, I was able to see that msiexec.exe was hitting the "adobe_caps.dll" file here:
C:\Windows\Installer\$PatchCache$\Managed\68AB67CA3301FFFF7706E0F060571500\15.6.30033
Being unfamiliar with the "$PatchCache$" folder, I did a little research and found that files can be cached here (and only cached ONCE) for any MSP file installed on your machine. Since the installer was being pulled across the network, it looks like a network hiccup occurred and a corrupt version of the "adobe_caps.dll" (showing as 0 KB) was stored in cache.
To resolve the error, all that needed to be done was to remove the entire "68AB67CA3301FFFF7706E0F060571500" folder & reinstall! Bam!!
Subscribe to:
Posts (Atom)