All affected clients. From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, July 19, 2016 9:28 AM To: [email protected] Subject: RE: [mssms] Adobe Updates Always Fail
Does this need to be done on all clients or just the server? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Tuesday, July 19, 2016 7:49 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Adobe Updates Always Fail John, I had this problem. I went through all the normal troubleshooting procedures – packet captures, procmon logs, verbose installer logs, you name it. Source files were accessible via a browser, but MSI fallback was getting 401 Unauthorized. It turned out to be a change in functionality after a security update to Windows Installer in 2014 (yeah, that long ago): https://support.microsoft.com/en-us/kb/2918614 Read under the “Known Issues” portion, specifically point 2. You can either whitelist the MSI product ID for affected applications, or you can just blanket whitelist the behavior altered by the security update (DWORD, SecureRepairPolicy = 1). Regards, Andrew From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Friday, July 15, 2016 2:56 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Adobe Updates Always Fail google-fu says status code 404 is "not found", and status code 401 is "unauthorized. So if *you* can get to that source, as your user creds, is it that SYSTEM can't get to that ? maybe a proxy thing? or maybe IIS settings? (I don't know, just thinking as I type). On Fri, Jul 15, 2016 at 11:48 AM, Marcum, John <[email protected]<mailto:[email protected]>> wrote: But I can get to the source files from a browser: From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Sherry Kissinger Sent: Friday, July 15, 2016 10:10 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Adobe Updates Always Fail Drat, I thought for sure that was it. Well, then my next thing is just for t-shooting. You'll want to temporarily enable "log everything windows installer does" using the voicewarmup regkey: https://support.microsoft.com/en-us/kb/223300 Once that's enabled, re-run the scup install, and I think you get some randomly-named .log file in 1 of the temp folders, or might be in %windir% somewhere. I always forget (I so rarely do that). Maybe the full, verbose log instead of just the short brief message in windowsupdate.log will tell you more about what the .msp is whining about. Of course, you'll want to yank that regkey once you're done t-shooting; otherwise you get log files all the time; taking up space... On Fri, Jul 15, 2016 at 8:47 AM, Marcum, John <[email protected]<mailto:[email protected]>> wrote: Did not work: Product {AC76BA86-7AD7-1033-7B44-AB0000000001} is installed for user SrcUpdateMgr 7/15/2016 8:33:55 AM 5128 (0x1408) Adding 1 local DPs and 0 remote DPs for product {AC76BA86-7AD7-1033-7B44-AB0000000001} SrcUpdateMgr 7/15/2016 8:33:55 AM 5128 (0x1408) Adding install source C:\_SMSTaskSequence\Packages\PS1000B3\ to source list for product {AC76BA86-7AD7-1033-7B44-AB0000000001} SrcUpdateMgr 7/15/2016 8:33:55 AM 5128 (0x1408) UpdateURLWithTransportSettings(): OLD URL - http://bhmcfgmgr01.bradleyarant.com/sms_dp_smspkg$/ps1000b3 SrcUpdateMgr 7/15/2016 8:33:55 AM 5128 (0x1408) UpdateURLWithTransportSettings(): NEW URL - http://bhmcfgmgr01.bradleyarant.com:80/sms_dp_smspkg$/ps1000b3 SrcUpdateMgr 7/15/2016 8:33:55 AM 5128 (0x1408) Added source http://bhmcfgmgr01.bradleyarant.com/sms_dp_smspkg$/ps1000b3 from local dps to source list for product {AC76BA86-7AD7-1033-7B44-AB0000000001} SrcUpdateMgr 7/15/2016 8:33:55 AM 5128 (0x1408) Successfully updated source list for product {AC76BA86-7AD7-1033-7B44-AB0000000001} SrcUpdateMgr 7/15/2016 8:33:55 AM 5128 (0x1408) 2016-07-15 08:43:02:881 344 150c Agent ** START ** Agent: Installing updates [CallerId = CcmExec] 2016-07-15 08:43:02:881 344 150c Agent ********* 2016-07-15 08:43:02:881 344 150c Agent * Updates to install = 1 2016-07-15 08:43:02:882 344 150c Agent * Title = Reader 11.0.17 Update 2016-07-15 08:43:02:882 344 150c Agent * UpdateId = {6E7C1776-48B5-4147-8B46-22920C094841}.1 2016-07-15 08:43:02:893 344 150c Agent WARNING: failed to calculate prior restore point time with error 0x80070002; setting restore point 2016-07-15 08:43:02:894 344 150c Agent WARNING: Failed SRSetRestorePoint call with win32 error 1260 2016-07-15 08:43:02:912 344 150c DnldMgr Preparing update for install, updateId = {6E7C1776-48B5-4147-8B46-22920C094841}.1. 2016-07-15 08:43:02:913 5360 ab4 Misc =========== Logging initialized (build: 7.6.7601.23453, tz: -0500) =========== 2016-07-15 08:43:02:913 5360 ab4 Misc = Process: C:\WINDOWS\system32\wuauclt.exe 2016-07-15 08:43:02:913 5360 ab4 Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2016-07-15 08:43:02:912 5360 ab4 Handler ::::::::::::: 2016-07-15 08:43:02:913 5360 ab4 Handler :: START :: Handler: MSI Install 2016-07-15 08:43:02:913 5360 ab4 Handler ::::::::: 2016-07-15 08:43:02:913 5360 ab4 Handler : Updates to install = 1 2016-07-15 08:43:02:914 5360 ab4 Handler Extracting MSP file stored in CAB AdbeRdrUpd11017.cab 2016-07-15 08:43:03:103 5360 ab4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch 2016-07-15 08:43:03:103 5360 ab4 Handler : Batch installing 1 updates 2016-07-15 08:43:03:113 5360 ab4 Handler List of MSPs in transaction: 2016-07-15 08:43:03:113 5360 ab4 Handler C:\WINDOWS\SoftwareDistribution\Download\13318319deea6796737e8d027b0bf945\img\AdbeRdrUpd11017.MSP 2016-07-15 08:43:03:113 5360 ab4 Handler MSP final command line: REBOOT=REALLYSUPPRESS MSIRESTARTMANAGERCONTROL=Disable 2016-07-15 08:43:05:369 5360 9e4 Handler WARNING: ResolveSource hit during binary-delta related action. 2016-07-15 08:43:06:517 5360 ab4 Handler MSP Error List: 2016-07-15 08:43:06:517 5360 ab4 Handler No messages in the MSP error list. 2016-07-15 08:43:06:517 5360 ab4 Handler : MSI transaction completed. MSI: 0x80070643, Handler: 0x8024200b, Source: Fallback, Reboot: 0 2016-07-15 08:43:06:517 5360 ab4 Handler : WARNING: First failure for update {6E7C1776-48B5-4147-8B46-22920C094841}, transaction error = 0x8024200b, MSI result = 0x80070643, MSI action = InstallFiles 2016-07-15 08:43:06:517 5360 ab4 Handler : WARNING: Operation failed at update 0, Exit code = 0x8024200B 2016-07-15 08:43:06:517 5360 ab4 Handler ::::::::: 2016-07-15 08:43:06:517 5360 ab4 Handler :: END :: Handler: MSI Install 2016-07-15 08:43:06:517 5360 ab4 Handler ::::::::::::: 2016-07-15 08:43:06:522 344 150c Agent LogHistory called. idUpdate={6E7C1776-48B5-4147-8B46-22920C094841}.1, resultMapped=8024002D, resultUnMapped=80070643 2016-07-15 08:43:06:524 344 150c Agent ********* 2016-07-15 08:43:06:524 344 e40 AU Can not perform non-interactive scan if AU is interactive-only 2016-07-15 08:43:06:524 344 150c Agent ** END ** Agent: Installing updates [CallerId = CcmExec] 2016-07-15 08:43:06:524 344 150c Agent ************* 2016-07-15 08:43:06:524 3744 16c8 COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = CcmExec] 2016-07-15 08:43:06:524 3744 16c8 COMAPI - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0) 2016-07-15 08:43:06:524 3744 16c8 COMAPI - Reboot required = No 2016-07-15 08:43:06:524 3744 16c8 COMAPI - WARNING: Exit code = 0x00000000; Call error code = 0x80240022 2016-07-15 08:43:06:524 3744 16c8 COMAPI --------- 2016-07-15 08:43:06:524 3744 16c8 COMAPI -- END -- COMAPI: Install [ClientId = CcmExec] From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Sherry Kissinger Sent: Friday, July 15, 2016 7:41 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Adobe Updates Always Fail Here's my "guess". "ResolveSource hit during binary-delta related action" Those are .MSP installs... and as such they expect to be able to find the source for whatever it is they are patching. For whatever that's patching, can you make a package (package, not an app, just because a package is easier to explain quick in email), where the source of that package is the original .msi for whatever that's patching. for the program (the program doesn't have to DO anything, just call it "do nothing" with a cmd /c or something) and on the Windows Installer tab, select the .msi for SourceList control. send the package to your DPs, and wait a bit for that policy to propagate, and on that client, policy refreshes and the windows installer sourcelist action; and watch the srcupdatemgr.log; make sure that test client gets it's sourcelist updated for that product. Then try the patch again--see if that made a difference. If so, it's just your sourcelist for the adobe products needs managing. the easiest way is to use CM to do that of course; but there are other scripts and ways to get it done. On Fri, Jul 15, 2016 at 7:18 AM, Marcum, John <[email protected]<mailto:[email protected]>> wrote: I’ve never been able to get the updates from the Adobe SCUP catalog to work. Has anyone else seen anything like this? Failed on every PC I have. 6964 1d10 Handler :: START :: Handler: MSI Install 6964 1d10 Handler ::::::::: 6964 1d10 Handler : Updates to install = 1 6964 1d10 Handler Extracting MSP file stored in CAB AdbeRdrUpd11017.cab 6964 1d10 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch 6964 1d10 Handler : Batch installing 1 updates 6964 1d10 Handler List of MSPs in transaction: 6964 1d10 Handler C:\WINDOWS\SoftwareDistribution\Download\13318319deea6796737e8d027b0bf945\img\AdbeRdrUpd11017.MSP 6964 1d10 Handler MSP final command line: REBOOT=REALLYSUPPRESS MSIRESTARTMANAGERCONTROL=Disable 6964 1188 Handler WARNING: ResolveSource hit during binary-delta related action. 6964 1d10 Handler MSP Error List: 6964 1d10 Handler No messages in the MSP error list. 6964 1d10 Handler : MSI transaction completed. MSI: 0x80070643, Handler: 0x8024200b, Source: Fallback, Reboot: 0 6964 1d10 Handler : WARNING: First failure for update {6E7C1776-48B5-4147-8B46-22920C094841}, transaction error = 0x8024200b, MSI result = 0x80070643, MSI action = InstallFiles 6964 1d10 Handler : WARNING: Operation failed at update 0, Exit code = 0x8024200B 6964 1d10 Handler ::::::::: 6964 1d10 Handler :: END :: Handler: MSI Install ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org ________________________________ This e-mail is intended only for the person or entity to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the original message and all copies from your system. Statements and representations made in this message are not necessarily that of the Company. ________________________________ This e-mail is intended only for the person or entity to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the original message and all copies from your system. Statements and representations made in this message are not necessarily that of the Company.
