-
Title
This Administration Service cannot respond due to configuration changes in progress -
Description
When attempting to connect to an ActiveRoles Administration Service that has just been added to replication you may receive the following error in the Web Interface or MMC Console:
This Administration Service cannot respond due to configuration changes in progress. Use a different Administration Service, or try to connect to this Administration Service in a few minutes.
Details: The replication role of the database server is being changed for this Administration Service. The Administration Service is unavailable until after the replication role of its database server has been changed and the Service restart has been completed.
In addition to this, replication errors may be seen in SQL similar to the following:
Data validation failed for one or more articles. When troubleshooting, check the output log files for any errors that may be preventing data from being synchronized properly. Note that when error compensation or delete tracking functionalities are disabled for an article, non-convergence can occur. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200953)
Article 'ScriptModules' failed data validation (rowcount only). Rowcount actual: 6, expected: 7. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200953)Article 'tblReplication' failed data validation (rowcount only). Rowcount actual: 6, expected: 7. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200953)
-
Cause
CAUSE 1
Once an ActiveRoles Administration Service has been added to replication as a subscriber, it will be unavailable until the initial replica is copied from the publisher. This behaviour is by design and cannot be changed.
CAUSE 2
SQL replication failure.
Access to native SQL tools will be necessary to investigate further.
-
Resolution
WORKAROUND 1
Wait for the initial replica to be created. Depending on the environment, it might take up to several hours.
Note: In some rare cases, with slow connections, hardware issues and huge amount of data (over 10 GB), it might take a few days to complete.WORKAROUND 2
Engage your DBA team or Microsoft for assistance with troubleshooting Microsoft SQL functionality.
If all else fails, break and then reestablish replication.