In case anyone else experiences this issue we have discovered that it appears to happen when transaction import can no longer read the import file (in our case the import files are on a mapped network drive and for whatever reason the mapped drive was no longer available). It appears that when this occurs transaction import simply stops without writing and error (although that may also be because the log file is on the same mapped drive).
↧