Return
-
Title
The PADataCollectionWebSvc_log.txt file has grown to a very large size -
Description
The PADataCollectionWeb_Svc_log.txt file has grown to a very large size
The contents of the file may show:
ThreadID: 12 ScriptLogic.PrivilegeAuthority.PADataCollectionWebSvc DataCollection Will now try to log this node in as a DataError in the databaseThreadID: 17 ScriptLogic.PrivilegeAuthority.PADataCollectionWebSvc DataCollection Caught exception while trying to add DataError to database:Could not allocate space for object 'dbo.DataError'.'PK_DataError' in database 'PAReporting' 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.ThreadID: 17 ScriptLogic.PrivilegeAuthority.PADataCollectionWebSvc DataCollection Please verify that the service account of the ScriptLogic PA Reporting Service has access to the databaseThreadID: 17 ScriptLogic.PrivilegeAuthority.PADataCollectionWebSvc DataCollection This will now cause the web service to throw an exception back to the client so that it will know that the db could not be contacted, and will need to try again. -
Cause
The PAReporting database may have reached its maximum size limit.
Check the size of the PAReporting.mdf file.
Review to see if it has reached its maximum size limit for the SQL instance being used.
MSDE has a maximum size limit of 2 GB.
SQL 2008 and 2005 have a maximum size limit of 4 GB.
SQL 2008R2 and 2012 have a maximum size limit of 10GB.
-
Resolution
To resolve this issue, you may either upgrade to a newer version of SQL, or migrate the PAReporting database to another SQL instance.
If the database is migrated, the Manager will need to be configured for this new SQL instance.This may be set by using the Privilege Manager Server Configuration Wizard.This configuration information may be found, starting on page 10 of the Quick Start Guide.