(Continued from previous part...)

Replication agents are failing with the following error. What's wrong?

Too many arguments were supplied for procedure <A_System_Stored_Procedure_Name> (for example: sp_MSenumschemachange)
The most probable reason for this error could be, mismatched service pack versions between the SQL Servers participating in replication.
Make sure all the participating SQL Servers are running with the same service pack installed.

Replication monitor is showing errors (White X mark on a Red circle), though there are no errors on any agents. How to get rid of these X marks?

In most of the cases, just restarting your SQL Server service should solve this problem. If restarting the server is not an option for you, go ahead and delete the table MSreplication_agent_status in the tempdb database.

Setup Transactional replication with "Immediate Updating Subscribers". Changes on publisher get replicated to the subscriber, without any errors. But when try to UPDATE/INSERT data at the subscriber, the following error and not able to modify data at the subscriber:
Server: Msg 18456, Level 14, State 1, Line 3
Login failed for user 'sa'.
How to correct this problem?

Immediate Updating subscribers connect the publisher using dynamic RPC, and this is the default. Dynamic RPC defaults to using the sa login with blank password. This behavior can be changed at the Subscriber using sp_link_publication.

To get rid of this error, execute sp_link_publication on the subscribing database and specify the sa password for the publisher.

E.g:
sp_link_publication
@publisher = 'Your_Publishing_Server_Name',
@publisher_db = 'Your_Publishing_Database_Name',
@publication = 'Your_Publication_Name',
@security_mode = 0,
@login = 'sa',
@password = 'Your_Publisher_SA_Password'

The Snapshot and Logreader agents are failing with the following error:
The process could not connect to Publisher 'Publishing_Server_Name'.
Category: Data source
Source: Publishing_Server_Name
Number: 18456
Full error message: Login failed for user 'sa'
The Snapshot and Logreader agents are running on the same publishing/distributing server, but still they are not able to connect.
How to overcome this problem?

You may get into this situation, when you configure your replication agents to log into the publisher and/or subscriber using "SQL Server authentication" (where you specify a specific SQL Server login, to connect to the publisher and/or subscriber). It will work fine initially, but when you change that particular login's password, you get the above mentioned errors. To solve this problem, whenever you change that particular login's password, make sure you change the password in the enabled publisher's and/or enabled subscriber's properties on that distribution server.

To change the publisher's properties:
- Open Enterprise Manager
- Connect to the Distribution server
- Go to Tools -> Replication -> Configure Publishing, Subscribers, and Distribution...
- Go to Publishers tab
- Click on the properties button (...) against the publisher's name
- Enter the new password for the SQL Server login.

To change the subscriber's properties, repeat the same steps as above, but in step 3, go to Subscribers tab.
Restart your agents, and they should be able to connect to the publisher/subscriber without any errors.

(Continued on next part...)