I had a client come to me with the strangest error today installing LF Windows Client 11.
Obviously this can not be true as it is a Windows app and Windows is going to include 64-bit support in most cases.
What could cause it to say such a thing?
I had a client come to me with the strangest error today installing LF Windows Client 11.
Obviously this can not be true as it is a Windows app and Windows is going to include 64-bit support in most cases.
What could cause it to say such a thing?
Chad, please run the installer from an elevated command prompt with logging enabled (setuplf.exe - log <path to log folder>) and open a support case.
The Laserfiche Client Suite applications (some of which are 32-bit) can be installed on x86-64 Windows operating systems and have been thousands of times.
Recall that SetupLf.exe launches underlying MSI installers. We checked the installer code and this error message being thrown suggests there are installation files missing from the installer directory. Specifically, it suggests one or more x64 install files are missing, so it's falling back to the x86 (32-bit) installer, and then throwing the error because the 32-bit installer isn't supposed to run on an x64 OS. Most likely (but not necessarily) the "CombinedARP*.msi" files:
You can check where it's going wrong by running SetupLf.exe with logging enabled:
".\SetupLF.exe" -log "C:\Logs\ServerInstall" (update with your own log path as desired)
However, rather than doing a bunch of work to figure out which files are missing, I'd recommend they simply get a fresh, intact copy of the installation package from the Laserfiche support site and try again with that. If they manually broke up the install package directories for any reason, don't do that this time and see if it works.
We had tried re-downloading the latest installer as well and got the same message.
Also they were running Windows 10 supporting both 32 and 64 bit applications. As far as I know it not an OS that requires 64 bit in any way, that would be news to me.
I will reach out about getting the log generated.
Gotcha. Yeah, as Miruna said, run it with logging enabled, get the log, and open a support case. It would also be useful to know if the error occurs on more than one machine and/or OS.
That error message is one that we wrote, not the installer surfacing a system-level error from Windows, and for some reason or another the code path that leads to it is getting tripped. The installer code is quite old and it's not the cleverest piece of software in existence - that's part of why we're introducing new ones for Laserfiche 12 soon. The logs will help identify where it's getting tripped up.