| Event Id | 104 |
| Source | ESE |
| Description | %1 (%2) %3The database engine stopped the instance (%4) with error (%5). |
| Event Information | According to Microsoft : Cause : This Error event first occurs when there are no log file names remaining. The affected storage group will not start until you resolve the problem. The maximum number of transaction log files that can be generated in a single sequence is 2,147,486,647 (0x7FFFFFFF). Typically, it will take dozens to hundreds of years of operation before this many log files will be generated. The transaction log file names resemble E0100012345.log, E01000ABCDE.log, E01000FFF00.log. The last eight characters of each log file name is the number of the log in the sequence. ESE has reached the last usable log generation number (0x7FFFFFEC), which is 16 logs before the maximum (0x7FFFFFFF) and all databases in the storage group have stopped with the errorJet_errLogSequenceEndStopping this error before the end of the sequence enables more than enough additional logs for the database to be returned to a Clean Shutdown state. Resolution : To recover from this problem, you must reset the log file sequence. To do this requires removing all existing transaction logs. After you do this, a new sequence of log files, starting with 0x00000001 will be generated. Before removing transaction logs, you must verify that all databases in the storage group are in a Clean Shutdown state. |
| Reference Links | Event ID 104 From Source ESE |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.