So I just ran into this same thing and did what Gail stated to do. But I am totally baffled as this database was NEVER involved in replication either on the old server (SQL 2008 R2) that it resided on or the new server (SQL 2016). Neither server was EVER setup for replication but all of a sudden at 2:18 am PDT this morning (11/4/17) I started receiving a flood of Severity 020 errors:
The log scan number (5423817:3214:0) passed to log scan in database '<DatabaseName>' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file(.mdf). If this error occurred during replication, re-create the publication.Otherwise, restore from backup if the problem results in a failure during startup.
SQL was not recycled, and unfortunately the error log got so bloated with over 2000 of these that it won't load in memory. I just wish I knew what triggered the database to think it was all of a sudden part of replication. FYI, CDC was/is not turned on for this DB.
Fixed (from Gail)
Set the server up for replication, create a publication in the DB in question. Publish any table (not important which one) and then completely remove replication again.