Error: Windows could not start the Altiris Deployment Server DB management service on the local computer

book

Article ID: 221776

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

Recently upgraded five GSS servers to version 3.3 RU8 and all were successful.  After a short amount of time, one of the servers started having the following issue:

  • When trying to start the GSS console the following message is seen: "Windows could not start the Altiris Deployment Server DB management service on the local computer".
  • When trying to start the Altiris DB service the following message is seen: "Error 1067: The process terminated unexpectedly".

The dbmanager.log includes the following:

[Mon Aug 16 08:28:39 2021.845] Database initialized...
[Mon Aug 16 08:28:39 2021.850] Result : 1 ReadServerSessionKey: ha[qq}xIWfpR_eg^CjjE]OAAKEY`|FCRlsdwascUwsF|YbuyChWhHhMYBXdGBZdjm^[email protected]`hvwTwPz^Q{chZ{LtLUpg]UcYeSV^Jkap
[Mon Aug 16 08:28:39 2021.852] CMMProcessor::RegisterInDatabase(): Database error 'The transaction log for database 'GSS5' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
' reported

Environment

GSS 3.3 RU8

Resolution

Changed the SQL Recovery Model to Simple.

Some reference articles are:

https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-ver15

https://docs.microsoft.com/en-us/sql/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002?view=sql-server-ver15

https://docs.microsoft.com/en-us/answers/questions/159917/what-can-i-do-if-my-transaction-log-is-full-hot-is.html

https://www.sqlshack.com/sql-server-transaction-log-administration-best-practices/