While running applications from our workflow server, the end users were reporting that emails were not being sent as designed. We furhter noticed the following error messages:
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.3959, P3 45d6968e, P4 mscorlib, P5 22.214.171.124, P6 4a7cd8f7, P7 11eb, P8 18, P9 system.outofmemoryexception, P10 NIL.
An unhandled exception occurred and the process was terminated.
Application ID: /LM/W3SVC/1/Root/HardwareEquipmentRequestV4
Process ID: 1052
Message: Exception of type 'System.OutOfMemoryException' was thrown.
StackTrace: at System.Threading.ExecutionContext.CreateCopy()
at System.Threading._TimerCallback.PerformTimerCallback(Object state
We further noticed additional error messages from the specific project logs:
System.Data.SqlClient.SqlException: Could not allocate space for object 'dbo.Messages'.'PK_Messages' in database 'Ensemble' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
This was very frustrating to the end users. Research and troubleshooting determined that the SQL server was running low and finally had run out of disk space. Allocating more disk space provided the application the resources that it needed to complete its work. It is recommended that you also assure that each of the databases have appropriate SQL maintenance plans configured. This will allow the tables and databases to be cleaned up and disk space recovered as transactions get completed and posted to the database. It is also recommended that you allow appropriate database, log file, and TEMPDB growth so that no resources become unavailable to the application. If these are limited, please make sure that your system provides notification prior to running out of space.