Just to add, I had a case where a job step of the replication job was running with a different credential, not with the login that was running the process....