Where to find logs
Plugin Log Locations
NOTE: This Library directory is hidden and can be accessed directly by navigating to "~/Library/" using the Go/Go To Folder... menu item or the ⇧⌘G hotkey.
Our plugins also write logs to the temp directory. These are helpful for troubleshooting startup errors. These logs will be named after the plugin and will have 4 random characters appended. For example, Scribe will have temp logs that are named something like:
Note:Plugins released after May 2017 will write to a log file called 360Plug-ins_Server.log or 360Plug-ins.Web64.log if you are looking for web publishing plugin logs. The location is the same as below.
/Library/FileMaker Server/Logs/360Plugin Logs/360Plugins_XXXXX.log
** Logs are appended to where ever FileMaker Server is installed.** **By default or if no FMS is found they are located here C:/Program Files/FileMaker/FileMakerServer** XP or S2003: C:\Documents and Settings\Default User\My Documents\360Plugin Logs\360Plugins_XXXXX.log Vista or S2008: C:\Users\Default User\Documents\360Plugin Logs\360Plugins_XXXXX.log Windows 7/2008R2 C:\Program Files (x86)\FileMaker\FileMaker Server\Logs Plugins released after 5/9/2017 C:\Program Files\FileMaker\FileMaker Server\Logs\360Plugin Logs\360Plugins_Server.log
(Note: The 64 bit version of Windows 7/Windows 2008 R2 runs a 32 bit architecture on top of the 64 bit architecture, and system files that need to run in 32 bit compatibility mode are stored in C:\Windows\SysWoW64 instead of C:\Windows\System32)
If the problem involves a crash, we may also need you to send us a crash log. On Macintosh, the crash file is located here:
FileMaker 7: /Users/yourName/Library/Logs/CrashReporter/FileMaker.crash.log FileMaker 8/9: /Users/yourName/Library/Logs/CrashReporter/FileMaker Pro.crash.log
On Windows, after a crash, sometimes there will be a Java crashlog file on your desktop called hs_err_pidXXXX.log, where the XXXX is a random number.
Windows crash log locations:
C:\Users\[Some User]\Microsoft\Windows\WER\ReportArchive or C:\ProgramData\Microsoft\Windows\WER\ReportArchive
Old plugin log locations
Older builds of 360Works plugins (usually from before 2013) may write log files separately and to different locations than listed above.
On OS X, the logs are normally in the same directories as those listed above, but separated into plugin-specific logs.
C:\Users\yourUserName\My Documents\nameOfPlugin.log C:\Users\yourUserName\AppData\Local\Temp\nameOfPlugin.log C:\Users\yourUserName\AppData\Local\Temp\360temp.log
Often the best way to send us logs for a web application is to use the browser interface to send the logs. If this feature is not working you may need to send the logs manually. Web Applications that run in the 360Works Service will write logs to the same location (with the exception of SuperContainer) unless you select otherwise during installation. Applications should keep several running days of logs and will have the name of your instance(called the product name like Zulu or MirrorSync by default) and a date in the name of the log file. We will often ask you to send us logs that correspond with the date when the issue last occurred. Default log locations are as follows:
If you need to get the logs for the SuperContainer Companion plugin, please see the instructions for plugins above. If you need to get the logs for the server component of SuperContainer, they will found at the same level as the "Files" folder. Default locations: