Article ID: 971607 - Last Review: June 16, 2009 - Revision: 1.0

FIX: The synchronization operation fails when you run the Merge Agent to synchronize a merge publication that uses Web synchronization in SQL Server 2005

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005, you configure a merge publication that uses Web synchronization. For example, you add a schema article such as a view, a stored procedure, or a function, to the merge publication. The Merge Agent uses an account that does not have permission to access the snapshot shared folder. When you run the Merge Agent to synchronize data, the operation fails and you receive the following error messages:

Date Time OLE DB Subscriber 'SUBSCRIBER': sp_MSacquiresnapshotdeliverysessionlock
Date Time OLE DB Subscriber 'SUBSCRIBER': sp_MStrypurgingoldsnapshotdeliveryprogress
Date Time OLE DB Subscriber 'SUBSCRIBER': sp_MSissnapshotitemapplied @snapshot_session_token = N'Path', @snapshot_progress_token = N'FileName'
Date Time OLE DB Subscriber 'SUBSCRIBER': sp_MSreleasesnapshotdeliverysessionlock
Date Time The schema script 'FileName' could not be propagated to the subscriber.
Date Time Percent Complete: 0
Date Time The schema script 'FileName' could not be propagated to the subscriber.
Date Time Percent Complete: 0
Date Time Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'FileName' could not be propagated to the subscriber.
Date Time Percent Complete: 0
Date Time Category:AGENT
Source: ServerName
Number: 0
Message: The process could not read file 'FileName' due to OS error 53.
Date Time Percent Complete: 0
Date Time Category:OS
Source:
Number: 53
Message: The network path was not found.
Back to the top

RESOLUTION

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
970279   (http://support.microsoft.com/kb/970279 /LN/ ) Cumulative update package 4 for SQL Server 2005 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 2005 fix release. Microsoft recommends 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:
960598  (http://support.microsoft.com/kb/960598/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top

WORKAROUND

To work around this issue, add a dummy table to the publication when you add the schema article.
Back to the top

STATUS

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

REFERENCES

For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
960598  (http://support.microsoft.com/kb/960598/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/935897/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
913089  (http://support.microsoft.com/kb/913089/ ) How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the new improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=131442 (http://go.microsoft.com/fwlink/?LinkId=131442)
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499  (http://support.microsoft.com/kb/822499/ ) New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Workgroup Edition
Back to the top
Keywords: 
kbsurveynew kbfix kbqfe kbexpertiseadvanced KB971607
Back to the top