We found this to happen on a server running that hosted a huge file. Most of the time it happened when available RAM was low, and in particular when the large file was backed up and verified, so our problem occurred once a week. When we backed up without verify, the problem occurred far less oftem.
There seemed to be nothing we could do when this happened, and most of the time command line did not help. Moving to a "bigger" server with lots of RAM solved the problem, but we are still wary of verify on large files.
When I added schedule script after that I m getting this kind of error.Before this everything was working fine
We get this error as well for our interface file which is not large in MB but does contain 1700 scripts.
For us, if you wait a few seconds after receiving the error and click next, it will actually go to the next screen.
How to solve this?
As noted by Scott above, you may have to move to a server that has a larger RAM allocation, as well as disable "verify" on your backups if you have large backups.
Nobody here has any idea how complex, or how much data, your 5 scripts that run every 15 minutes are. If you have the scripts performing a lot of steps, and/or have a large amount of data being processed by the scripts, then you could be overloading your server, causing the error after continuous use of resources.
Do you have any resource monitoring software installed on your server to track what filemaker is using over time?