SQL Server: Invalid Log Scan Number (...) passed to log scan in database (...) is not valid
With the help of an outside source, the issue was nailed down to a corrupted transaction log and was fixed by reinitializing replication from scratch.

It was strongly recommended that we evaluate our I/O subsystems that house the log file to make sure there isn't a problem there which caused it.