Article ID: 267264 - View products that this article applies to.
This article was previously published under Q267264
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57962 (SQLBUG_70)
When a subscription for a transaction publication expires, this error message should occur:
However, if a subscription to the publication is created with @sync_type='none', and then if the subscription is marked as inactive, the error message does not occur. Instead, the distribution agent displays the following error message although there may be transactions that are coming into the publisher database for the articles:
The subscription has expired and must be reinitialized at the publisher.
The distribution..MSsubscriptions table entry for the given subscriber will have a status of zero when subscriptions have expired.
no replicated transactions
When you encounter this situation, the subscription is already marked as expired and it may not be possible to specify the time when the subscription expired. Therefore, the solution is to reinitialize the subscription and resynchronize the databases.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799For more information, contact your primary support provider.
(https://support.microsoft.com/kb/274799/ )INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0