The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%1!s!'. Enabling this option after the article is created can cause replication to fail when the data in a FILESTREAM column exceeds 2GB and there is a conflict during replication. If you want FILESTREAM data to be replicated, drop and re-create the article, and specify the appropriate schema option when you re-create the article.
The schema change failed during execution of an internal replication procedure. For corrective action, see the other error ...
The schema definition of the destination table '%1'.'%2' in the subscription database does not match the schema definition ...
The schema for the article %1!s! was either not generated properly or was not applied properly during initial synchronization. ...
The schema of the custom DataSet object implemented in the business logic handler does not match the schema of the source ...
The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%1!s!'. ...
The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, ...
The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, ...
The schema script '%1' could not be propagated to the subscriber due to an error in creating index. A possible cause of this ...
The schema {0} does not have any corresponding user or role. Schema objects are not supported in the target database version, ...