| Event Id | 14049 |
| Source | ISA |
| Description | %1 was stopped because of a logging failure. For more information about this event, see ISA Server Help. |
| Event Information | Explanation
A service stops when an activity log stops responding. If you log to a file on your local file system, it is most likely that a logging failure was caused by insufficient disk space. If you log to a database, the failure is probably related to an error in configuration, insufficient disk space, or connectivity problems.
UserAction: If the failure is the result of insufficient disk space, move old files to another media or delete them manually and configure the system to delete old files in the future. To edit logging configuration, in the ISA Management console tree, click Servers and Arrays, click Name, click Monitoring Configuration, and then click Logs. If you log to a database, check the database configuration. To reconfigure disk space, select a shorter period for logging (for example, weekly or daily), click Location and then select the option to compress log files. |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.