[Bug 45680] New: dotnet35(sp1) fails to install in a 64bit prefix
https://bugs.winehq.org/show_bug.cgi?id=45680 Bug ID: 45680 Summary: dotnet35(sp1) fails to install in a 64bit prefix Product: Wine Version: 3.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: farmboy0+winehq(a)googlemail.com Distribution: --- Created attachment 62103 --> https://bugs.winehq.org/attachment.cgi?id=62103 WINEDEBUG=-all,+msi,+msiexec Steps to reproduce: 1. create new 64bit wine prefix without mono 2. use winecfg to set windows version to Windows 2003 3. run ./dotnetfx35.exe /lang:ENU 4. accept EULA and press install button 5. wait for it to crash during installation The last errors will always be: 00b3:err:msiexec:custom_action_server Failed to read from custom action server pipe: 109 0097:err:msiexec:custom_action_server Failed to read from custom action server pipe: 109 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #1 from Hans Leidekker <hans(a)meelstraat.net> --- Is this still an issue in current Wine? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #2 from farmboy0+winehq(a)googlemail.com --- The error message has changed with wine 3.16: 002e:err:msi:ITERATE_Actions Execution halted, action L"CA_ScheduleCacheGACAssembly.3643236F_FC70_11D3_A536_0090278A1BB8" returned 1603 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #3 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to farmboy0+winehq from comment #0)
Created attachment 62103 [details] WINEDEBUG=-all,+msi,+msiexec
Steps to reproduce: 1. create new 64bit wine prefix without mono 2. use winecfg to set windows version to Windows 2003 3. run ./dotnetfx35.exe /lang:ENU 4. accept EULA and press install button 5. wait for it to crash during installation
On second thought, I don't think that recipe can work without setting a native override for mscoree before running the installer. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #4 from farmboy0+winehq(a)googlemail.com --- Ive set mscoree to n,b but the error persists. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #5 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to farmboy0+winehq from comment #4)
Ive set mscoree to n,b but the error persists.
It should be a native-only override, so mscoree=n. The important thing is that LoadLibrary("mscoree") fails until native mscoree is installed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #6 from farmboy0+winehq(a)googlemail.com --- I have set mscoree to native only now but the error still persists. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #7 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to farmboy0+winehq from comment #6)
I have set mscoree to native only now but the error still persists.
Can you attach a WINEDEBUG=+msi,+msiexec,+loaddll,+process,+seh trace? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #8 from farmboy0+winehq(a)googlemail.com --- I think this bug can be closed. The installation seems to have been successful with wine 3.17. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 Hans Leidekker <hans(a)meelstraat.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Hans Leidekker <hans(a)meelstraat.net> --- Reported fixed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #10 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Hans Leidekker from comment #9)
Reported fixed.
Just for the info: I can confirm the installation succeeds and reports success when following the recipe provided in this bugreport. I don`t know if everything is installed correctly and if it`s enough to run 64-bit .Net apps. Does anyone know that? Also: ``winetricks dotnet35sp1`` reports it doesn`t work, maybe time for an update as this seems to succeed now???? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #11 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to Louis Lenders from comment #10)
(In reply to Hans Leidekker from comment #9)
Reported fixed.
Just for the info: I can confirm the installation succeeds and reports success when following the recipe provided in this bugreport.
I don`t know if everything is installed correctly and if it`s enough to run 64-bit .Net apps. Does anyone know that?
Also: ``winetricks dotnet35sp1`` reports it doesn`t work, maybe time for an update as this seems to succeed now????
It probably needs native msxml3 as well because of bug 33450. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, Installer URL| |https://www.microsoft.com/e | |n-us/download/details.aspx? | |id=21 Summary|dotnet35(sp1) fails to |Microsoft .NET Framework |install in a 64bit prefix |3.5 (SP1) fails to install | |in 64-bit WINEPREFIX Hardware|x86 |x86-64 CC| |focht(a)gmx.net --- Comment #12 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, the issue is definitely a dupe of existing MSI bugs in between 3.14-3.17 (including regressions). But well ... let it be. To verify .NET Framework installation(s) in WINEPREFIX you can always use the .NET Framework Setup Verification Tool from Aaron Stebner (Microsoft) which checks for proper installation of .NET assemblies and registry entries. https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-ver... Select the .NET Framework you want to verify and evaluate the log file manually if verification failed. Additional manual checks... CLR bootstrapper (presence + bitness + size/date): --- snip --- $ find .wine/drive_c/ -iname "mscoree.dll" -exec file {} \; .wine/drive_c/windows/syswow64/mscoree.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows .wine/drive_c/windows/system32/mscoree.dll: PE32+ executable (DLL) (GUI) x86-64, for MS Windows $ find .wine/drive_c/ -iname "mscoree.dll" -exec ls -la {} \; -rw-rw-r--. 1 focht focht 282112 Oct 24 2007 .wine/drive_c/windows/syswow64/mscoree.dll -rw-rw-r--. 1 focht focht 448000 Oct 23 2007 .wine/drive_c/windows/system32/mscoree.dll --- snip --- Check if GAC update/refresh is properly working by running both, 32-bit and 64-bit NGEN. --- snip --- $ find .wine/drive_c/ -iname "ngen.exe" -exec file {} \; .wine/drive_c/windows/Microsoft.NET/Framework64/v2.0.50727/ngen.exe: PE32+ executable (console) x86-64, for MS Windows .wine/drive_c/windows/Microsoft.NET/Framework/v2.0.50727/ngen.exe: PE32 executable (console) Intel 80386, for MS Windows # 32-bit NGEN $ wine "c:\\windows\\Microsoft.NET\\Framework\\v2.0.50727\\ngen.exe" update /force # 64-bit NGEN $ wine "c:\\windows\\Microsoft.NET\\Framework64\\v2.0.50727\\ngen.exe" update /force --- snip --- @Louis: --- quote --- Also: ``winetricks dotnet35sp1`` reports it doesn`t work, maybe time for an update as this seems to succeed now???? --- quote --- Sure, some 'winetricks' .NET recipes could get some updates. While at it, the 'Windows 2003' setting in .NET Frameworks 4.5.x+ recipes after install is harmful nowadays. It should be reset to default ('Windows 7'). Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #13 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Anastasius Focht from comment #12)
Hello folks,
Sure, some 'winetricks' .NET recipes could get some updates. While at it, the 'Windows 2003' setting in .NET Frameworks 4.5.x+ recipes after install is harmful nowadays. It should be reset to default ('Windows 7').
Regards
Thanks for the info, I opened a ticket at winetricks: https://github.com/Winetricks/winetricks/issues/1111 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.18. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com --- Comment #15 from Austin English <austinenglish(a)gmail.com> --- (In reply to Louis Lenders from comment #13)
(In reply to Anastasius Focht from comment #12)
Hello folks,
Sure, some 'winetricks' .NET recipes could get some updates. While at it, the 'Windows 2003' setting in .NET Frameworks 4.5.x+ recipes after install is harmful nowadays. It should be reset to default ('Windows 7').
Regards
Thanks for the info, I opened a ticket at winetricks: https://github.com/Winetricks/winetricks/issues/1111
In what wine versions? Is there a bug/commit associated with that on the wine side? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #16 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Austin English from comment #15)
(In reply to Louis Lenders from comment #13)
Thanks for the info, I opened a ticket at winetricks: https://github.com/Winetricks/winetricks/issues/1111
In what wine versions? Is there a bug/commit associated with that on the wine side?
Hi austin, not sure what you exactly mean, if you mean what commit fixed it, I don`t know. At least the installation was reported successfull (following recipe in comment 1 _and_ comment 5) in wine-3.17; -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45680 --- Comment #17 from Austin English <austinenglish(a)gmail.com> --- (In reply to Louis Lenders from comment #16)
(In reply to Austin English from comment #15)
(In reply to Louis Lenders from comment #13)
Thanks for the info, I opened a ticket at winetricks: https://github.com/Winetricks/winetricks/issues/1111
In what wine versions? Is there a bug/commit associated with that on the wine side?
Hi austin, not sure what you exactly mean, if you mean what commit fixed it, I don`t know. At least the installation was reported successfull (following recipe in comment 1 _and_ comment 5) in wine-3.17;
I was wanting to know in what wine versions that wine should report Windows 7, and when it should report win2k3. Presumably older wine versions should keep using win2k3, but it's not clear to me what changed, or when. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org