|Issue||Transaction Log on Archer Configuration Database is Full|
[A company] called in reporting that the job engine would not start, SSO wasn't working and they were getting prompted for credentials when accessing the Archer Control Panel.
We looked in the logs and found that the transaction log file on the Archer Config database was full. We decided to shrink the files on both the Config and Archer Instance databases to free up space.
You can do the same for the Instance database as well. As always, make sure their Recovery Model is set to simple instead of full to keep the logs from filling up so quickly.
|Legacy Article ID||a58418|