Product and version: FileMaker Pro 220.127.116.113
OS and version: Windows 2012 r2
Hardware: Amazon virtual machine
Description: We run a robot in FileMaker Pro. The robot file is hosted in FileMaker Server 18.104.22.1684. The robot runs a timer every 5 minutes. The timer checks a table, a printing queue, to see if there are any records in it. If so, the timer performs printing operations for each record. At some point in time, we receive customer complaints that requested reports stop appearing in the solution. Windows displays a message saying "FileMaker Pro stopped working". We are forced to restart FileMaker Pro. FileMaker Pro then clears the queue and performs normally until the next customer complaint, which could be hours or days away.
How to replicate: We do not know what the trigger is. The same FileMaker file was working fine in FileMaker Pro Advanced 15.0.1, 15.0.2 and15.0.3 under Windows 2008 in a VMWare virtual machine with a robot file hosted by FileMaker Server 15. We tried using FileMaker Pro 16 under Windows 2008 in a VMWare virtual machine a few months ago. We encountered the same issue back then so we reverted to FileMaker Pro Advanced 15. We also did not report the issue at the time.
Workaround (if any): None. We are forced to restart FileMaker Pro. We have no notification of the crash. We find out when our customers complain about missing reports. At that point, the printing queue can be quite long.
Other notes: We searched for similar issues using Google and found nothing that matched our description. We did notice one thread where an engineer asked if any plugin was in use. We use two plugins: CC Pivot 2 (2.034); MBS Plug-In (22.214.171.124).