If you can provide the error state, then it would be much easier to troubleshoot. check the below link.

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

Do you mean the space within the database or the space on the drive where the database resides?

First, You should take the necessary precautions to see that the transaction log disk pace is never full.

You should either put the database in simple recovery mode or should have...

Check the following Link. It may be of use to you.

http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/31bb8ff3-03be-4dfd-95a1-c06fe4e7c993/

You may use the tablediff utility to compare tables .

http://msdn.microsoft.com/en-us/library/ms162843.aspx

The below link may help you.

http://msdn.microsoft.com/en-us/library/ms176029.aspx

Replace your code in sp_add_jobschedule with the following. I think it would work.

...

sp_change_users_login does not work for Windows Logins. As suggested in the earlier posts Drop and recreate the user or you can use the below command.

ALTER USER [username] WITH LOGIN...