This error is occurring because the database LOG file is either too large for what has been allocated or the SQL server disk is full. Here are some important things that can be done to prevent and remove this error:
1. Add the "--" in the line "/* <-- Add a double dash ("--") at the beginning of this line to uncomment the code below " in the "Stored Procedure sp_EventAdminDeleteEventsOlderThan" of your database. it will shrink the database after the cleanup procedure is finished. (see attached Picture1.jpg, Picture2.jpg)
We recommend using Aelita Intrust for Events procedure for truncate the Transaction logs, for more details refer to KB Article # 673.
2. Or you can setup the database to automatically shrink itself. This is done in SQL Enterprise Manager by finding the database of interest, clicking with the right mouse button then selecting properties. Under the Options folder make sure you have selected "Truncate Log on CheckPoint", "Select into/bulk copy", and "Auto Shrink". These options will significantly help control the size of the database and log file. This will also compact the database on a daily basis. The appropriate options are shown below. Note that you may not be able to make these changes if your database is with a web hosting provider. In this case ask them to make the change for you. Note: After making these changes it may take minutes and possibly more than 1 hour for the server to recover from the problem and shrink the database (see attached Picture3.jpg).
1. Setup a routine maintenance plan to backup the database and log file. At minimum the database and log file should be backed up weekly. On high traffic sites this should be done daily. Normal the LOG file will not shrink until it has been backed up at which time SQL truncates the log and shrinks the file.
2. If number 1 is not the cause of your problem you should also check that the hard drive holding the databases on the SQL server is not full. A full hard drive has also been known to cause this problem. If this is the cause of the problem consider moving the database to another larger drive.
3. Lastly, the cause of the problem might be that your database size has been restricted and you are exceeding these restrictions. Increasing the database and log file size will fix the problem. Keep in mind they may charge you more money for the extra space. Allowing the database and log file to automatically grow will also resolve the problem. A sample of this is shown below for the database file. Because the database can grow without any restrictions this error will be prevented (see attached Picture4.jpg).