Inconsistent LSNs after Full/Diff backup?

Hi all,

On SQL Server 2008 R2-SP2 we have 10 databases. For one of them I realized that I'm unable to restore log backups if in the middle we have full or diff backup. The error was related to LSN chain (..backup is too early to apply...).

I used RESTORE HEADERONLY to investigate LSNs:

restore headeronly from disk='...\Log_Backup01.bak'

restore headeronly from disk='...\Log_Backup02.bak'

restore headeronly from disk='...\DIFF_Backup03.bak'

restore headeronly from disk='...\Log_Backup04.bak'

restore headeronly from disk='...\Log_Backup05.bak'

The result was:

First LSNLast LSN

19249690000017003000011924970000000581700001

19249730000004539001381924973000000697700001

19249770000000041000011925604000008223800001

19256040000082238000011925604000008271200001

As you see, the second and fourth log backups have inconsistent LSNs. I tried RESTORE HEADERONLY for many backups of this database and the LSN chain was lost after full or diff backup.

Also this database is in transnational replication. I'm suspicious about log reader agent. But another database on this server has transnational replication too, but this issue doesn't happen.

Any help would be greatly appreciated.

Leila