I really don't know what it means, sorry. The only thing I can find that i similar is this post, which is for SQL 2008, and doesn't really offer a solution except to suggest it's a bug in SQL Server. Are you sure there's no possibility of connection problems to the snapshot folder, either by the publisher or subscriber?

You can trace the error further though, using the MSrepl_commands table and sp_browsereplcmds procedure to find out what the command is doing that generates the error. Use the xact_seqno and command_id to get the record from MSrepl_commands then use the publisher_database_id, xact_seqno and article_id values from there to feed to the sp_browsereplcmds procedure. If nothing else, you'll get to learn more about the underlying workings of replication :hehe:. But you may get something else to google*

Duncan

*(other search providers are available)