DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2737161 - Last Review: October 16, 2012 - Revision: 3.0

Microsoft distributes Microsoft SQL Server 2008 Service Pack 3 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 3 fix release.

On This Page

Symptoms

Consider the following scenario:
  • You configure database mirroring on two instances of Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2.
  • You configure a transactional replication publication on a database that is the principal read-write database on a principal server in a database mirroring partnership. The replication initialization is finished, and then is synchronized with the subscriber.
  • The replicated database fails over from the principal server to the mirror server.

    Note When this occurs, the former mirror server switches roles, and the database comes online in read-write mode as the new principal database.
  • You add an article to the publication on the new principal instance. The replication initialization is finished, and then is synchronized with the subscriber.
  • You add another article to the publication.
In this scenario, you receive the following error messages.

Error message 1

A snapshot was not generated because no subscriptions needed initialization.

Error message 2

Msg 14058, Level 16, State 1, Procedure sp_MSrepl_addsubscription_article, Line 331

Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information

Note This issue still occurs if you fail over to the original principal instance, and then you add the same article.

Resolution

Cumulative update information

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2754552  (http://support.microsoft.com/kb/2754552/ ) Cumulative update package 3 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301  (http://support.microsoft.com/kb/2730301/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2756574  (http://support.microsoft.com/kb/2756574/ ) Cumulative update package 9 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616  (http://support.microsoft.com/kb/2567616/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 7 for SQL Server 2008 Service Pack 3. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
2738350  (http://support.microsoft.com/kb/2738350/ ) Cumulative update package 7 for SQL Server 2008 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 3 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2629969  (http://support.microsoft.com/kb/2629969/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information

For more information about how to configure replication and database mirroring, go to the following MSDN website:
How to configure replication and database mirroring (http://msdn.microsoft.com/en-us/library/ms151799(v=sql.100).aspx)
For more information about database mirroring, go to the following MSDN website:
General information about database mirroring (http://msdn.microsoft.com/en-us/library/bb934127(SQL.100).aspx)

Workaround

To work around this issue, determine whether the sys.servers.server_id column and the syssubscriptions.ssrvid column match on the active database instance before you add the article.

Notes
  • If the two columns do not match, you should add the article to the publication from the instance in which the columns match. You might have to schedule downtime to fail over the database to the partner instance.
  • If there are multiple srvid values in the syssubscriptions table, remove the article that has a different srvid value, fail over the database to the partner instance, and then add the article again.

Applies to
  • Microsoft SQL Server 2008 Service Pack 3
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2737161
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support