Overview
In some cases, if there are issues when installing or upgrading M-Files, troubleshooting them may require taking Windows installer logs. Here are the instructions for taking the logs.Solution
You can take the logs this way when running the installer manually:- Open Windows Command Prompt as administrator (e.g. search cmd.exe from Windows start menu, right click Command Prompt and select Run as administrator).
- Start installation by running following command in the Command Prompt:
msiexec /i C:\temp\<name of M-Files installer>.msi /l*vx C:\temp\mfileslog.txt
This assumes that M-Files installer package has been saved in C:\temp\ and the log file will be created there as mfileslog.txt. If the installer is in some other location on your computer or you want the log file to be created elsewhere, change the paths in the above command accordingly.
This assumes that M-Files installer package has been saved in C:\temp\ and the log file will be created there as mfileslog.txt. If the installer is in some other location on your computer or you want the log file to be created elsewhere, change the paths in the above command accordingly.
- Continue installation until it finishes or the issue under investigation occurs. Deliver the log file to M-Files Support if requested by them.
In case of automatic M-Files updates, the logs are enabled automatically. You can find the logs whose names begin with "Setup", "Activator", "MFClient" or "MFServer" from the locations mentioned below. Deliver these to M-Files Support if requested by them.
- System user's %TEMP%\MFilesLogs folder, which is usually C:\Windows\Temp\MFilesLogs
- And/or regular user's %TEMP%\MFilesLogs locations (e.g. C:\Users\<username>\AppData\Local\Temp\MFilesLogs)
