At times, when the Geo SCADA server crashes and the DB logs indicate a failure in creating minidump files, there could be several reasons for this.
Here are the possible causes for the failure to generate dump files:
1- Disk Space: Frequent failures in saving dump files may be attributed to insufficient disk space. In this scenario, it is advisable to increase your disk size to ensure that the Geo SCADA server has enough space to generate dump files. Another option is to inspect the Server Configuration, specifically the 'System Configuration | Logging | Exception dumps Location settings' and the associated disk space. It's possible that the installation is using all the default settings of location and, for example, some locations should not be on the C drive. Note that you can also verify the available disk space in your system by examining the DBSnapshots.
2- Memory: Another factor that may cause a failure in creating a minidump file is the machine running out of memory. Typically, the server crashes when generating DBSnapshots as they use a lot of memory. In such instances, it is recommended to inspect the DBSnapshot and check the available physical memory. This can help identify if memory constraints are contributing to the minidump file creation failure. In this situation, we suggest adding more RAM to your system to address the low memory issue. This should help improve system performance and resolve the issue with generating minidumps.
3- Full dump files are configured: Modifying the dump file type from normal to full in Server Configuration | System Configuration | Logging | Exception dumps can result in very large dump files that take up a lot of time and memory to generate.
If none of the previously mentioned reasons are responsible for the failure to generate the dump files, please contact the Schneider Electric support team for further investigation.
