I am not sure if this is the exact same issue, but I was getting the same error. In my organization, every time there is a schema change we deploy it on the production system by first bringing down P2P Transactional replication, then patching the main location, then pushing a backup of that DB to the other nodes, and adding them back into the P2P topology. Don't ask why - I've already fought that fight. Any time a new column was added to an existing table, we got the "Invalid Column Name" error. This was occurring even after replication was completely brought down, Distribution disabled, Distribution database dropped, and SP_Removedbreplication was run on the database. Apparently it was holding onto the old list of replicating columns, and not adding the new columns. The workaround I found was to rebuild the publication, with all the articles needed, then go into the Publication and drop all the articles, then, finally, go back in and re-add the articles. I am not sure where it was keeping the old column list, since the sysarticlecolumns didn't even exist on the database when I was patching the schema, but this method seems to work.