Configuring site database data for replication changes the objects to be replicated and may cause them to be out of date when the database tables are replicated. If this happens, you may see errors in the ddm.log and dataldr.log files similar to:

Microsoft SQL Server reported SQL message 2801, severity 16: [42000][2801][Microsoft][ODBC SQL Server Driver][SQL Server]The definition of object 'sp_GetPublicKeyForSMSID' has changed since it was compiled. : sp_GetPublicKeyForSMSID

Solution

After creating a SQL publication, the following stored procedure should be run on the SQL Server site database server computer (publisher) to ensure that objects to be replicated have been updated to the most current information.

Note
This procedure uses the sp_GetPublicKeyForSMSID object referenced in the issue log example. This procedure can be used for any replication article experiencing this error and referenced in ddm.log or dataldr.log files.

To update objects to be replicated on the SQL Server publisher computer

1. In the SQL Server 2005 SQL Server Management Studio console connected to the SQL Server hosting the site database replica, expand Databases, right click the site database name and click New Query.

2. In the query results pane, enter the following commands:

   EXEC sp_recompile GetPublicKeyForSMSID

3. Click Execute to begin reconfiguration.

4. Verify that the object to be replicated has been successfully marked for recompilation in the Messages pane.

When a management point is configured to access site data from a replicated SQL Server site database, and the replicated site database is not functioning properly, management point control manager (SMS_MP_CONTROL_MANAGER) will report error 500. Because management point control manager attempts to access management point information the same way clients do, it returns the same error that a client would when it fails to access management point information.

Solution

Concepts