BUG: Replication Transactional Pull Subscriptions Fail with "Error 14262:The specified @job_id could not be found" Error Message (304091)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
  • Microsoft SQL Server 7.0
  • Microsoft SQL Server 7.0 Service Pack 1
  • Microsoft SQL Server 7.0 Service Pack 2
  • Microsoft SQL Server 7.0 Service Pack 3
This article was previously published under Q304091
BUG #: 354833 (SHILOH_BUGS)

SYMPTOMS

SQL Server 2000 has a new option to retain replication settings, while performing a RESTORE of a database, by specifying the KEEP_REPLICATION option. If you back up a Subscriber database (viz.Sub1) and then restore the database to the same server as a different database (viz.Sub2), the following error message may occur when you start the Distribution Agent for the subscription in Sub1:
Error 14262: The specified @job_id ='947352EE-72C7-4B06-AF9A-004BFE121C38 ' does not exist.
The actual value for the job_id will differ for your environment.

This problem is specific to environments where a subscribing database is backed up and restored as a different database on the same server.

CAUSE

When you back up and restore a Subscriber database on the same server (with a different database name) without the KEEP_REPLICATION option, all replication objects and replication jobs that belong to the restored database are removed. The RESTORE DATABASE command removes all of the replication objects and replication jobs from the restored database that cause the Distribution Agent job of the original database to be deleted because the Distribution Agent job_id is the same for both the original subscribing database and the restored database.

Executing the Pull Distribution Agent on the original database to synchronize data with the Publisher causes the agent to fail with the error message shown in the "Symptoms" section.

WORKAROUND

To work around this problem either:
  • Specify the KEEP_REPLICATION option with the RESTORE command. The KEEP_REPLICATION option does not remove replication objects from the restored database and does not delete the existing subscription jobs. This option does not exist for SQL Server 7.0.
  • Use Data Transformation Services (DTS) to transfer all the user objects and data instead of using the BACKUP and RESTORE commands.
  • Restore the Subscriber backup to a different server. When you restore the backup to a different server, you do not have to specify the KEEP_REPLICATION option unless you need to retain the replication settings.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.

Microsoft has confirmed this to be a problem in SQL Server 7.0.
Modification Type:MajorLast Reviewed:6/25/2004
Keywords:kbbug kbpending KB304091
©2004 Microsoft Corporation. All rights reserved.