Plugin log files

From 360Works Product Documentation Wiki
Jump to: navigation, search

Contents

Log Locations

FileMaker Client

OS X

/Users/userName/Library/Logs/360Plugin Logs/360Plugins_XXXXX.log

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.

Windows

XP or S2003: C:\Documents and Settings\<userName>\360Works\360Plugins_XXXXX.log
Vista and Later:  C:\Users\<username>\360Works\360Plugins_XXXXX.log

Our plugins also write 360temp.log. This log should have an entry with the location of the plugin log file

Windows:

C:\Windows\Temp\360temp.log

Mac:

/tmp/360temp.log

FileMaker Server

OS X

/Library/FileMaker Server/Logs/360Plugin Logs/360Plugins_XXXXX.log

Windows

** 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)

Crash Logs

OS X

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

Windows

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.

On Windows:

C:\Users\yourUserName\My Documents\nameOfPlugin.log
C:\Users\yourUserName\AppData\Local\Temp\nameOfPlugin.log
C:\Users\yourUserName\AppData\Local\Temp\360temp.log

Logging Level

By default our plugins will log the information that we need to diagnose most issues. If for some reason you need to decrease the logging level or want more logging details you can change the logging level by following this process.

1. Determine what version of Java that you are using. You can do this by looking at the top of the logs for a line that says "Java home dir was dynamically read:" and it will list the path to the Java version you are using. If you are Mac it should be Java 6

2. Go to /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib (Mac) or C:\Program Files\Java\JAVAVERSION\lib and look for the file called "logging.properties" (Mac) or "logging" (Windows)

NOTE: This file may require certain permissions so if you run into issues, copy the file to the desktop, open , modify , save and then replace the old one with the one you modified.

3. Open the logging.properties file with a good text editor (not textEdit or notepad) and look for the section that says "Global Properties". The last line of this section says .level=INFO under this line type com.prosc.level= OFF. This will turn off all Java logging. The downside to this is if you ever have anything go wrong we might not be able to help until logging is turned back up because the logs are usually the first thing that we look at. Alternatively, instead of OFF you can vary the logging level by using SEVERE (highest value, least logging), WARNING, INFO, CONFIG,FINE,FINER, FINEST (lowest value, most logging).

4.Save the file and restart the FileMaker Script engine. You can do this by either restarting the machine or by typing the command "fmsadmin restart fmse -y" in Terminal or in cmd . On Windows, you will need to change directories to ...\FileMaker Server\Database Server

Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox