The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a republishing Subscriber has run out of identity ranges to allocate to its own Subscribers or when an identity column data type does not support an additional identity range allocation. If a republishing Subscriber has run out of identity ranges, synchronize the republishing Subscriber to obtain more identity ranges before restarting the synchronization. If a Publisher runs out of identity ranges, verify that the size of the data type supports the needed identity ranges.
The Publish Database Wizard enables you to publish database and objects in a database to remote instances of SQL Server by ...
The published object {0} ({1}) is dependent on the unpublished object {2} ({3}), creation of the published object at the ...
The Publisher and Subscribers can update the published data independently after the Subscribers receive an initial snapshot ...
The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have ...
The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a ...
The publisher login must be a member of the 'db_owner' role at the publisher database when generating a regular snapshot. ...
The publisher login of the snapshot agent must be granted permission to create databases in order to generate a replication ...
The Publisher must use this password when it automatically connects to the Distributor to perform replication administrative ...
The publisher name of the contacted Oracle instance does not match the configured name for the publisher at this distributor. ...