It was OK to change the account, just remember that the password for that login shoudn't expire, or SQL won't start next time you need it.

The Second error is because...

You shoudn't have any problem even they are not dbo tables.

When creating the publication, in EM, you can specify the tables you wan't to publish and it also shows you...

Was the source server a MAster Server?

Try defecting the destination server with msdb.dbo.sp_msx_defect. If the destination server is already a target server, be carefull because all the MSX jobs will...

Not necesarely, you can specify the full path of a script in the pre and post_snapshot_script parameters of the sp_addpublication sp for transactional replication, and the same parameter for merge...

After the data is copied you can create the index with a post snapshot sctipt.

Be sure to check the scripts right, before executing them...

The sintax looks good to me.. try using [] in [rowguid].

If the merge process created this column, see if the error is something about that this column is been referenced...

Do you have replication running in the server?

If no, it is much easier. After renaming the server, you can run, sp_addserver 'YourServer', 'Local', 'duplicate_ok'. To verify the server has been...

In the publication properties, right click over the publication.In the "Filter Columns" Tab, you can select the table you want to add a column and then click over the...

In sql you can add more log files but they are treated as one log. When one file fills up, then it changes to the other.

To avoid loosing the log...

Instead of running the snapshot, for me it is easier to run sp_addscriptexec, passing the script file that modifies the sp.

Then the next time the distribution agents, runs, the execution...

Check the sysjobs and sysjobsteps tables in msdb from both servers for that particular job, and check if there are any diferences.

If there are , you can script the job...

When we started to replication it was OK, to run the distributor on the publisher. In fact we are still doing it. But in a near future I will change...

You could check for a process running sp_MSget_repl_commands, that is an sp runned by the distribution agent.

You can use dbcc inputbuffer (spid) to find out.

sp_MSarticlecleanup will only drop tables created for the management of the replication, likes views, SPs, conflic tables...all used for replication.

This article MatrixCellDynamic is it a user Table?.

If it is a push subscription, check in the publisher with sp_who2 wich process id is running the agent.

It could be that someone fire the agent from the command line,...