Overview
In case you have issues with replication, there are specific logs that can be enabled to provide more information about the issue.
Solution
You can enable logs with these server-side registry settings:
[HKEY_LOCAL_MACHINE\SOFTWARE\Motive\M-Files\<ersion>\Server\MFServer\Logging]
"Enabled"=dword:00000001
"EnableVerboseLogging"=dword:00000002
"LogDir"="%TEMP%\MFilesLogs"
"FlushIntervalInSeconds"=dword:0000000a
"LogCategories"=dword:00080000
By default, the location of log files is %TEMP%\MFilesLogs. (In test environment: C:\Windows\Temp\MFilesLogs)
Enabled and EnableVerboseLogging are set to 0 by default, change the values 1 to enable logging. No need to restart M-Files Server services.
In some cases, e.g. if you have connection issues related to replication, MFReplicationTransport logs could be also useful, those can be enabled by adding the following registry settings:
[HKEY_LOCAL_MACHINE\SOFTWARE\Motive\M-Files\<version>\Server\MFReplicationTransport\Logging]
"Enabled"=dword:00000001
"LogDir"="%TEMP%\MFilesLogs"
"FlushIntervalInSeconds"=dword:0000000a
"EnableVerboseLogging"=dword:00000002
"LogCategories"=dword:ffffffff
"TotalMaxSizeInMB"=dword:000000c8
"DeleteLogsOfOtherInstancesAfterDays"=dword:00000015
"PreserveAtLeastDays"=dword:00000000
Please reproduce the issue with the registry keys set and send those logs to M-Files Support by following these instructions: /article/How-to-Send-Files-via-CryptShare-Portal
After the needed logs are gathered, Enabled should be set to 0.
