Hi Henrik,
It appears the task and job names are combined to create an audit log entry, however the data is too log causing the insert to fail. When this happens the it must continue to try to log as this error appeared repeatedly until the machine ran out out of disk space due to log growth with this single error in it.
2/12/2019 4:42:01 PM Err InsertAuditLogItem->Exception: System.InvalidOperationException: Description : String truncation: max=500, len=616, value='User 'VisualCron Default Admin' (admin) updated Job 'JOB NAME REDACTED'. Task 'TASK NAME REDACTED' was updated. Task 'TASK NAME REDACTED' was updated. Task 'TASK NAME REDACTED' was updated. Task 'TASK NAME REDACTED' was updated. Trigger 'Every Monday,Tuesday,Wednesday,Thursday,Friday of the week at 12:42:00 PM since 12/11/2017' was updated.'.
at System.Data.SqlServerCe.SqlCeCommand.FillParameterDataBindings(Boolean verifyValue)
at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommand(CommandBehavior behavior, String method, ResultSetOptions options)
at System.Data.SqlServerCe.SqlCeCommand.ExecuteNonQuery()
at VisualCronService.DBLoggerClass.CBOFJICBGIJKFJKDKAAIEFMPKKLEBLHIMFLF(DBLogItemClass ) in C:\sourcefiles\code\VisualCronService\Log\clsDBLogger.vb:line 770
I think if this occurs logging the error once and not retrying would probably suffice. This seems like it would become more of an issue if you have jobs with many tasks (in our case the tasks names were overly descriptive and long). The work around is to turn off database logging.
Mike
Edited by moderator
2019-02-15T12:12:34Z
|
Reason: Not specified