Return
-
Title
Issue after upgrading ARS without removing replication -
Description
When attempting to upgrade ARS without removing replication, the upgrade process fails (as expected) due to the replication still being in place. This leaves a temp database, as well as leaves the existing configuration database in single-user mode which doesn't allow any more connection to it. -
Resolution
1.- Remove replication in the primary ARS server via the SQL Management studio.2.- Run the following SQL Query to kill the connection and set it back to multi-user state:
DECLARE @DatabaseName nvarchar(50);SET @DatabaseName = N'' DECLARE @SQL varchar(max)SET @SQL = ''SELECT @SQL = @SQL + 'Kill ' + Convert(varchar, SPId) + ';'FROM MASTER..SysProcessesWHERE DBId = DB_ID(@DatabaseName) AND SPId <> @@SPIdEXEC(@SQL)SET @SQL = 'ALTER DATABASE ' + @DatabaseName + ' SET MULTI_USER'EXEC(@SQL)
3.- Configure the registry to set the Configuration Center to not configured.4.- Ran configuration center and configured it to create a new database, ActiveRoles73.5.- Ran configuration import from source DB (ActiveRoles72) to new database (ActiveRoles73).6.- Once configuration is imported to the primary server, launch the ARS Console and configure replication.7.- Run Management history import wizard.