Today, I stumbled upon an issue with the development environment having IISExpress crashing and no one was able to browse D365 F&O environment.
By default IISExpress starts automatically when opening visual studio (yes, I know we can change the default to IIS by modifying DynamicsDevConfig.xml) acting as the host of the D365 F&O application.

By checking Event Viewer logs and found that AxDB LOG file size has grown dramatically and the drive hosting it ran out of space.

Event Viewer
AX is shutting down due to an error. Error during initialization of Message Broker. Please verify that your AOS instance has connection to the AOS Database. Error messages follow: Could not execute operation against the SQL Database. The transaction log for database ‘AxDB’ is full due to ‘LOG_BACKUP’. Exception details: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> Microsoft.Dynamics.Ax.Xpp.Messaging.MessageBrokerStartupException: Could not execute operation against the SQL Database. —> System.Data.SqlClient.SqlException: The transaction log for database ‘AxDB’ is full due to ‘LOG_BACKUP’. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand
MSSQL Logs Drive:

Resolution
To clear up disk space we need to shrink DB Log size. This can be done in various ways:
- Stop AOS and IIS services
- Restart SQL Server Service
- Or Right Click the database name and choose: Tasks > Shrink > File
- Or Use of DBCC SHRINKFILE command (best option)
To get the temp log files names, run the following SQL select statement:
SELECT name, file_id, type_desc, size * 8 / 1024 [TempdbSizeInMB]
FROM tempdb.sys.database_files
WHERE type_desc = 'Log'
ORDER BY type_desc DESC, file_id
Using the output from the select statement, execute DBCC SHRINKFILE command for each file:
use tempdb
Go;
DBCC SHRINKFILE(templog, 10);
If the DBCC command is not decreasing the file size try clearing the plan cache:
DBCC FREEPROCCACHE