The subscription could not be initialized using an initial snapshot because one or more tables in the subscription belong to another publication, and therefore cannot be dropped. Consider initializing the subscription manually without using a snapshot.
The Subscriber partition information string may be truncated such that only the first %1!d! characters of the string will ...
The subscription '{0}' cannot be found. The subscription identifier that is provided to an operation cannot be located in ...
The subscription (Publisher=%1!s!, PublisherDb=%2!s!, Publication=%3!s!, Subscriber=%4!s!, SubscriberDb=%5!s!) is not accessible. ...
The subscription (Publisher=%1!s!, PublisherDb=%2!s!, Publication=%3!s!, Subscriber=%4!s!, SubscriberDb=%5!s!) is not active ...
The subscription could not be initialized using an initial snapshot because one or more tables in the subscription belong ...
The subscription database was successfully attached. The subscription will be visible the next time you run Windows Synchronization ...
The subscription has been marked as removed and will be absent from the list of subscriptions the next time you run Windows ...
The subscription has been marked for reinitialization. Reinitialization will occur the next time you synchronize this subscription. ...
The subscription has expired and is no longer available. Do you want to mark the subscription for reinitialization? Reinitialization ...