Could not add new article to publication ХХХ because of active schema change activities or a snapshot is being generated.

[Orlandis]

Hello.
We use SQL Server transactional replication for Attynity. It was time for a technical replacement of the servers that previously ran SQL Server, where the databases were located, from which Attynity took information for DWH. We configured the new servers in the same way as the old ones, and performed the switchover (the old ones were turned off, and the new ones were started). During the switchover, all Attynity tasks were turned off, after starting the new servers, all Attynity tasks were started, the tasks seemed to start and publications were automatically created on the SQL Server side, which were filled with the necessary tables, but at the same time, there were many errors of type 

Capture functionalities could not be set. RetCode: SQL_ERROR  SqlState: 42000 NativeError: 21854 Message: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Could not add new article to publication 'AR_PUBLICATION_00007' because of active schema change activities or a snapshot is being generated. Line: 1 Column: -1

in the Attynity log

At the same time, all tasks were started and continued to work.
Is it worth checking anything on the Attynity side now, were there such errors and how can this be dangerous during such transitions?

[john_wang]

Hello @Orlandis ,

Thanks for reaching out to Qlik Community!

To make sure the Change Processing work fine I'd like suggest to drop the replication AR_PUBLICATION_00007 and recreate it , then reload the task. The article will be regenerated automatically.

Hope this help.

John.

[Orlandis]

Hello. Thanks for the recommendation. We did so and when we restarted the Attunity job we also got these errors in the Attunity log, while the Attunity session on the SQL server side was running and populating the publication on the SQL server side with all the tables that were in the job. In the end, we waited for the job launch process to complete and went into the normal workflow. I am interested in the nature of this error and its possible consequences, what else can cause such an error?