Symantec Critical System Protection Agent does not upload logs to server because database is full

Article:TECH178213  |  Created: 2012-01-04  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH178213
Article Type
Technical Solution


Issue



Symantec Critical System Protection Agent does not upload logs to server because database is full


Error



In the Agent log file named SISIPSService.log you find the following (or similar) error.

SCSP Error when trying to send a log. Error Code  300 : Error Message : &quot1;SQL Code: 1105&amp1;crlf1;&amp1;crlf2;Could not allocate space for object 'dbo.CSPEVENT'.'PK__CSPEVENT__46E78A0C' in database 'SCSPDB' because the 'scspevents' filegroup is full. Create disk space by deleting unneeded files&amp1;sep1; dropping objects in the filegroup&amp1;sep1; adding additional files to the filegroup&amp1;sep1; or setting autogrowth on for existing files in the filegroup.&amp1;crlf2;&quot1;"

In the Server log sis.agent.0.log

63662 2011-12-15 11:00:35.085 [ERROR] Error Code: 1105
63663 2011-12-15 11:00:35.085 [ERROR] [SQL:1105] Could not allocate space for object 'dbo.CSPEVENT'.'PK__CSPEVENT__46E78A0C' in database 'SCSPDB' because the 'scspevents' 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.
java.sql.BatchUpdateException: Could not allocate space for object 'dbo.CSPEVENT'.'PK__CSPEVENT__46E78A0C' in database 'SCSPDB' because the 'scspevents' 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.

 


Environment



Symantec Critical System Protection
OS  Independent


Cause



The SQL  Server database cannot grow further and is full.

This problem appear when the MS  SQL  Server Express database is used in a production environment and the database size is approaching the 4GB  limit.

MS  SQL  Server Express  2005 has a limit of 4GB
MS  SQL  Server Express 2008 R2 has a limit of 10GB


Solution



Possible solutions include upgrading the Database to a commercial version or eliminating older logs from the server.

Often logs must be kept for system compliance, so the best solution is to upgrade the database to a commercial version able to store the amount of data required by the specific environment. This must be evaluated independently for each environment, depending on event logging policy, number of clients and how long logs have to be kept for compliance




Article URL http://www.symantec.com/docs/TECH178213


Terms of use for this information are found in Legal Notices