Transaction Log for database 'myDatabase' is full due to ACTIVE_TRANSACTION when creating a Non Clustered Index
We've changed over the log file disk location to a local disk and that has fixed the problem.

It is still not entirely clear why the transaction log was not expanding in the network location as there didn't seem to be a logical reason why it wouldn't but its something to bear in mind in the future