Your Console Manager Console Is in Read Only While This Site Completes

There are actually valid reasons for the panel being in read-but style such as the ones listed below:-

* You connect to a primary site before it completes the Configuration Manager site installation.
*Yous connect to a primary site that has intersite replication problems.
* Yous connect to a primary site during a site restoration of that site.
* You connect to a master site when that site is initializing global data.

in this case information technology ended up being an effect with my principal server and specifically with the SQL Broker Service. To observe out how I adamant what was the crusade read on.

Read-Only mode.

Afterward powering  on one of my CM12 labs and logging on to the principal site P01 I noticed the following window popup when i started the Admin Console:

Your Configuration Managing director console is in read-only manner while this site completes tasks related to maintenance mode. After these tasks are consummate you must reconnect your Configuration Manager console before you can edit or create new objects.

(Tin can y'all spot the missing 'r' in the bulletin below ?)

Later you click OK y'all become to run across the panel but look at the title bar, Continued to READ-ONLY is clearly visible.

Looking at my Site Hierarchy I tin can see that the Global Data Replication Status is Unknown between CAS and my Primary site P01 (and vice versa) and in addition the Site Data Replication status is unknown.

Looking further into this select Database Replication in the Monitoring workspace to go Database replication status, it was listed equally Unknown

and finally opening the rcmctrl.log file in D:\Plan Files\Microsoft Configuration Manager\Logs\rcmctrl.log reveals that the current site status is ReplicationMaintenance. In improver it states that the site is NOT active, so not  calling the DrsActivation Procedures.

Equally I hadn't powered on these virtual machines (1 of my CM12 Labs) in a while, this was understandable, so it seemed that all I had to do was look until information technology was consummate. I waited over an hr and  the site was still the aforementioned according to the rcmctrl.log on P01.

Troubleshooting on CAS using the Replication Link Analyzer.

To troubleshoot further, I logged on to the CAS server and after reviewing the Database Replication status on that server, I could see information technology  showed a different story, start of all the Administrator console opened with no problem on CAS and secondly Database replication was listed  as existence Active on CAS but the link has failed betwixt it and the primary kid site. This was not good, link status can be in one of three states.

• Link is active
• Link is degraded
• Link has failed

Now was a good a time as any to run the Replication Link Analyzer. I clicked on it and answered yeah to the UAC prompt.  The replication link analyzer started.

after a while information technology presented me with the post-obit screen, which wanted to reset queued replication messages (or skip this dominion)

I selected reset.

which produced a new message, namely that the timeout had expired while attempting to launch the Replication Link analyzer engine on P01, however it did provide me with a ReplicationLinkAnalysis.log file saved  on my Desktop.

Opening ReplicationLinkAnalysis.log with CMTrace revealed the following:-

ReplicationLinkAnalysis Error: 1 : Timeout Expired. The timeout period elapsed prior to completion or the server is not responding.

So basically the log file above is telling us that it stopped running tests due to the failure of one of the Replication Link Analyzer rules. These rules are listed in the ReplicationLinkAnalysis.xml file. The following rules are checked:

• SMS service is running
  SMS Replication Configuration Monitor component is running
  Ports required for SQL replication is enabled
  SQL version is supported
  Network is bachelor betwixt the two sites
  In that location's enough space for SQL Database
  SQL Server Banker service configuration exist
  SQL Server Banker service document exist
  Any know errors in SQL log files
  Are the replication queues disabled
  Fourth dimension is in sync
  Is the manual of data stuck
  Does Key Conflict exist

Looking at the ReplicationLinkAnalysis.XML file placed on the desktop nosotros have more info  about the testing washed past the replication link analyzer including where it failed, namely during the DoesBrokerConfigurationExist on P01.

Now we know our issue is related to the SQL Broker Service, and so we should check out the error log for SQL to come across what information technology says, that error log is located at D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\ErrorLog and that revealed SQL fault 3961 which is:

Snapshot isolation transaction failed in database '%.*ls' considering the object accessed by the statement has been modified by a DDL argument in another concurrent transaction since the beginning of this transaction. Information technology is disallowed because the metadata is not versioned.

Ok at this point it looks like the SQL database on P01 is confused,  probably due to server load at the time of booting upwardly the server, and due to the fact that the SQL server itself was sitting on the same PID since the fourth of July along with more than  two weeks of the virtual motorcar being in a saved country. I could await some more or try restarting the SMS Executive service or a reboot of the server. As this is my LAB I had enough of the troubleshooting and did a reboot.

Afterward the reboot (of P01)  I ran the Replication Link Analyzer again (on CAS) and this time the SQL Broker Service on P01 was working notwithstanding the site was withal replicating, a few minutes later in rcmctrl.log  I could run across that the Electric current Site Status had finally changed to ReplicationActive.

And that means that I can start the console again, without it beingness READ-Simply !

Hopefully this postal service volition assistance you in troubleshooting site to site replication problems should they occur, to conclude please take note of the following:-

To replicate data between ConfigMgr sites, Configuration Manager uses Database Replication Service(DRS). DRS uses SQL Server Service Broker (SSB) to replicate data betwixt the sites.

Configuration Manager database replication uses SQL Server to transfer data and merge changes that are made in a site database with the information stored in the database at other sites in the hierarchy. This enables all sites to share the aforementioned information. Database replication is automatically configured by all Configuration Manager sites. When yous install a site to a bureaucracy, database replication automatically configures between the new site and its designated parent site. When the site installation finishes, database replication automatically starts.

• For more details about Database Replication Service – Technet
• For more details about SQL Server Service Broker – MSDN
• Service Banker Troubleshooting – MSSQLTips

Tips for troubleshooting SC 2012 Configuration Managing director Information Replication Service (DRS) – MSDN Blogs.

until next fourth dimension, thanks

niall

villegastwourt1954.blogspot.com

Source: https://www.niallbrady.com/2012/07/23/why-is-my-system-center-2012-configuration-manager-console-in-read-only-mode/

Share this post