Hi,
It is possible that the error was related to the root emulator role that the offline management server was serving. In System Center 2012 R2 – Operations Manager, the root management server role was removed and all management servers are now peers. However, the RMS emulator role provides for backward compatibility for management packs targeting the RMS. If any management packs in your environment were targeting the root emulator, it is possible that the offline management server being the root emulator caused issues that affected the online management server.
It could also be related to resource pool design considerations. When two or more management servers are added to a management group, the management servers automatically become part of the three default resource pools and work is spread across the members of the pool. For custom-defined resource pools, members are manually added. When a member of the resource pool fails, other members in the resource pool will pick up that member’s workload. If the offline management server was a member of a custom-defined resource pool that the online management server was also a member of, then its failure could have affected the ability of the online management server to carry out its workload.
In summary, it is possible that various factors such as the root emulator role, resource pool design, or SSRS could have caused one management server being down to affect another one.