Issue metadata
Sign in to add a comment
|
Install via .msi produces side by side error
Reported by
qartman...@gmail.com,
Feb 6 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 Steps to reproduce the problem: 1. Deployed package to multiple computers using msi installer 2. Users received side-by-side error when launching chrome 3. Installed local using .msi (interactive) to remediate issue 4. Installed using following syntax: msiexec /i "\\<fileserver01>\RMS-Deploy-Share\GoogleChromeStandaloneEnterprise64.msi" /qn /l* C:\Temp\chromeinstall.log What is the expected behavior? We've pushed out Chrome many times before using exact method and not had an issue. Expected behaviour is that Chrome would launch without error after update via .msi What went wrong? Not sure - the install log shows success. - event viewer logs below Activation context generation failed for "\\pc101\c$\Program Files (x86)\Google\Chrome\Application\chrome.exe". Dependent Assembly 64.0.3282.140,language="*",type="win32",version="64.0.3282.140" could not be found. Please use sxstrace.exe for detailed diagnosis. Did this work before? Yes 63x Chrome version: 64.0.3282.140 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 28.0 r0 This exact deployment method has worked numerous times and we have not received this sidebyside error... To remediate the .msi had to be run interactively...
,
Feb 7 2018
Thanks for filing the issue! This issue seems to be out of scope for triaging from ET end, as this is related to Enterprise. Adding label TE-NeedsTriageFromHYD for further triaging. @Inhouse: Could someone from TE-Hyd team look into this.
,
Feb 7 2018
Hi. Could you please provide C:\Windows\Temp\chrome_installer.log from one of the affected machines? Thanks.
,
Feb 12 2018
,
Feb 28 2018
Is this still an issue for you with the latest stable installer?
,
Oct 29
No answer from bug filer so closing archived |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Feb 6 2018