Quote: The transaction log ... is full
my D drive is full
Could this be an reason for the issue?
If SQL Server doesn't have enough space in the transaction log to write the details of your transaction, you will get a "transaction log full"
error. Even if your transaction log doesn't have a fixed size, if the disk it's stored on has run out of space, the transaction log will be unable to grow, and won't be able to process any more transactions.
The Transaction Log (SQL Server) - SQL Server | Microsoft Learn
As Herman said, you need to find out why your transaction log is taking up so much space. There could be many reasons - for example, if your database recovery mode is set to "full" and you've never taken a transaction log backup.
Microsoft's documentation has a good explanation of the possible causes, and what you can do to try to fix them:
Troubleshoot full transaction log error 9002 - SQL Server | Microsoft Learn
reason suggests you have at least one long-running transaction which has never been committed or rolled-back. Query the sys.dm_tran_database_transactions
] dynamic view to see what transactions are active.