![]() ![]() SafetyNet logs will follow the naming convention timestamp. If you are not able to access the SafetyNet page, you can manually send the logs. At the top right corner there is a link that says "Report a bug". To submit a bug report, go to the SafetyNet page in a browser. tmp the log files are called websvcmgr.log and wsmRequest.log.Ĭ:\WINDOWS\TEMP\websvcmgr.log and C:\WINDOWS\TEMP\wsmRequest.log Send the email to unless specified otherwise. ![]() Attach the logs to an email with a description of the issue and instructions on how to reproduce. You will need to manually submit your logs for Web Services Manager. So if the issue occurred on December 2nd 2019 then log needed would be called catalina.log If you need to send logs from the development or production server the locations for those are as follows:ģ60Deploy logs will follow the naming convention timestamp. If you need to send logs pertaining to the plugin, then please see the Plugins section above for instructions on sending those logs. Zulu logs will follow the naming convention so if you kept the default name of "Zulu" and the date the issue occurred was December 2nd 2019 then the log you would want to send would be called Zulu.logģ60Deploy has two components - a plugin and a web application. ![]() If you are not able to use the automated process, you can manually send the logs as an attachment to an email. In a browser, log into the Zulu Sync Admin and then click the link at the top that says " Email Log File ". Zulu has an automated way of sending a problem report. MirrorSync logs will follow the naming convention so if you kept the default name of "MirrorSync" and the date the issue occurred was December 2nd 2019 then the log you would want to send would be called MirrorSync.log. If there is a problem using that automated system for sending logs, can you manually retrieve the logs:Ĭ:\Program Files\360Works\Applications\logs To report a bug and send logs from MirrorSync, go to the MirrorSync launch page in your browser ( and click the link titled 'Send problem report and log files'. If you still did not, please call us and let us know and we can create a ticket for you. If you did not receive it, please send the logs again. If you do not receive this then make sure to check your junk folder in case it was put there automatically by your email client. Once our support system has processed your email, you will receive an automated response from us. Please be sure to include as many details as you can and the steps to reproduce the issue if possible. Attach the logs to an email and send it to. Please see the Plugin log files page for log locations. If you are seeing errors when executing plugins functions server side either via a schedule, perform script on server script step, or in web direct, you will need to submit your logs manually as there is no mechanism for sending a bug report. Please be sure to do this BEFORE any restarts of FileMaker as restarting will overwrite the logs Select the plugin from list (highlight the line).If you are using a plugin in FileMaker Pro, then you can use the Send Bug Report feature to send us the plugin logs and also create a ticket in our support system. If you need help submitting for non-plugin products (tools such as MirrorSync and Zulu), please see the bottom of this page. It is the same set of instructions for any plugin you use. These instructions are for submitting a bug for ALL plugins, including but not limited to: Scribe, Email, CloudMail, Plastic, FTPeek, JDBC, Charts, Web Assistant, ScriptMaster, and SuperContainer Companion Plugin. If using the automated process, you do not need to send an additional email as the automated process will create the ticket for you as well as attach the logs. If the automated process does not work you will need to send the logs manually. Some products have an automated way of sending the logs while others will require that you manually attach the logs to an email. ![]() This will vary depending on what product you are using. Sending these with your initial email will expedite the support process. Additionally, it is common for us to request logs in order to troubleshoot the issue. It will help if you include the operating system, version of FileMaker, the product and the version of it this issue pertains to and steps to reproduce the issue. If you are experiencing any issues with 360Works products, we may ask you to submit a ticket by sending an email to In the email, be sure to include as many details as possible. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |