https://bugs.documentfoundation.org/show_bug.cgi?id=155408
Mike Kaganski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #29 from Adam Clarke ---
Hi Mike
We don't have the ability to open a ticket with Microsoft with our schools
agreement type so this is not an option for us im afraid. I have imported the
latest VcRedist into SCCM using
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #28 from Adam Clarke ---
Hi Mike
I am currently wrestling with trying to get the 2015-2022 redist installed in a
task sequence and it just fails constantly with an error code so I will let you
know where I get with this
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #27 from Mike Kaganski ---
(In reply to Mike Kaganski from comment #26)
> change from Microsoft Visual C++ Redistributable
> for Visual Studio 2015-2019 version 14.28 to version 14.29
And this looks suspicious, reading the
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #26 from Mike Kaganski ---
(In reply to Adam Clarke from comment #25)
> Have just tried 7.3.0.3 and this also works
7.3.3.1 or 7.3.3.2 are interesting, I suspect that these would fail, while
7.3.2.* would still work.
This
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #25 from Adam Clarke ---
Hi Mike
Have just tried 7.3.0.3 and this also works
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #24 from Mike Kaganski ---
(In reply to Adam Clarke from comment #23)
And likely, 7.3.3 will fail?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #23 from Adam Clarke ---
Hi Mike
I have just tried 7.3.0.1 and it works. Does this mean it is a C runtime issue
then?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #22 from Adam Clarke ---
Hi Mike
I have just tried 7.3.0.1 and it works. Does this mean it is a C runtime issue
then?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #21 from Mike Kaganski ---
(In reply to Adam Clarke from comment #20)
> I have tried 7.2.7.2 and this also fails
Really great.
Could you please also test version 7.3.1, 7.3.2 and 7.3.3 (if you haven't
tested them yet)?
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #20 from Adam Clarke ---
Hi there
We're there any changes after 7.2.6 as I have tried 7.2.7.2 and this also fails
so it looks like the very next release is the issue
--
You are receiving this mail because:
You are the
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #19 from Adam Clarke ---
Hi Mike
As per your forum request I am slowly going through the archive and testing
versions to see what works and what does not so I will let you know ASAP.
Thanks again...
--
You are receiving
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #18 from Jussi Pakkanen ---
> do you have an idea what could be the reason of this SCCM change between 7.2
> and 7.4?
Sadly no. All the changes I have been a part of have dealt with the new WiX
installer and not the old
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #17 from Adam Clarke ---
I wonder if it could be the changes made to the WiX toolset? That would be my
guess?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #16 from Mike Kaganski ---
FTR: the changes mentioning "msi" after 7.2 branch-off are
https://gerrit.libreoffice.org/q/msi+branch:master+after:2021-06-07
--
You are receiving this mail because:
You are the assignee for the
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
Mike Kaganski changed:
What|Removed |Added
CC||jpakk...@gmail.com
--- Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #14 from Adam Clarke ---
I do appreciate your time looking at this for me though...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #13 from Adam Clarke ---
Hi Mike
Sorry, poor choice of words. It is definitely the same issue as pmaynard I am
having. When running in an SCCM task sequence it just hangs forever but if I
add /norestart it fails and does not
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #12 from Mike Kaganski ---
(In reply to Mike Kaganski from comment #11)
> FTR: I tested this scenario ('msiexec /i
> D:\Downloads\LibreOffice_7.5.3_Win_x86-64.msi /quiet' command line
Oh, of course, the command line was a
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #11 from Mike Kaganski ---
(In reply to Mike Kaganski from comment #10)
> When I used a normal,
> unelevated cmd.exe, it obviously silently failed (and Windows Event Viewer
> registered an error 10005, telling that current
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #10 from Mike Kaganski ---
(In reply to Adam Clarke from comment #9)
> It appears to be an elevation issue.
You do not describe the exact scenario you use, it seems to be a huge obstacle.
Are you trying to install/advertize
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #9 from Adam Clarke ---
Ok I think I am getting somewhere. It appears to be an elevation issue. The old
msi 7.2.6 seems to work fine without elevation as do all other MSI's I use for
other software however the new MSI's for
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #8 from Mike Kaganski ---
(In reply to Adam Clarke from comment #7)
> interestingly all are Windows 10 22H2
Mine too: Version 22H2 (OS Build 19045.2846).
--
You are receiving this mail because:
You are the assignee for the
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #7 from Adam Clarke ---
Ok thankyou for your help. I am finding it bizzare that the old 7.2.6 installer
works fine but same commands on the recent ones are not recognised. I have
tried on multiple different standalone
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #6 from Mike Kaganski ---
FTR: just now, I uninstalled LibreOffice from my Windows 10 box, opened cmd.exe
as Administrator, and run this exact command line:
> msiexec /i D:\Downloads\LibreOffice_7.5.3_Win_x86-64.msi /quiet
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #5 from Mike Kaganski ---
(In reply to Adam Clarke from comment #4)
> it also does not recognise the commands for logging appears to
> ignore any command used.
This is highly strange. The command line arguments are handled
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
Adam Clarke changed:
What|Removed |Added
Ever confirmed|1 |0
Status|NEEDINFO
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
V Stuart Foote changed:
What|Removed |Added
OS|All |Windows (All)
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #3 from Mike Kaganski ---
(In reply to Adam Clarke from comment #2)
Did you try to create logs, as explained in the FAQ [1]? No matter if the
installation completes; the log is being written from the first stage, and may
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
--- Comment #2 from Adam Clarke ---
Hi there. From what I can see the installation never begins so this is the
reason I cannot provide logs for the process. The issue seems to affect all
recent installers so I think there may be a
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
Mike Kaganski changed:
What|Removed |Added
URL||https://ask.libreoffice.org
https://bugs.documentfoundation.org/show_bug.cgi?id=155408
Roman Kuznetsov <79045_79...@mail.ru> changed:
What|Removed |Added
Blocks||113117
32 matches
Mail list logo
