*the Japanese part means “Cannot open database ‘rtcshared’ requested by the login. Even if there is “something” to do with BE, it can be failed over very soon, there should be no problem.ĪND, since all there events (32163, 32170, and 32173) are related to Fabric service, I checked Windows Fabric event logs and found this event, saying Windows Fabric cannot connect a database called rtcshared. It doesn’t mention that BE should also be up as well. , “If the number of servers running falls below the functional level as shown in this table, the remaining servers in the pool go into survivability mode, and…”īUT, for a 2-FE pool, Number of servers that must be running for pool to be functional is 1, which means even if 1 server downs, the rest one should continue serving without issue. Hose events look familiar? Yes, just as described here, #32173: Server is being shutdown because fabric pool manager could not be initialized More Information #32170: Pool Manager failed to connect to Fabric Pool Manager #32163: Local Pool Manager has been disconnected from Pool Fabric Manager. If one FE and the Principal BE fail, even if you fail over BE to Mirroring BE a.s.a.p., the other FE’s Front End Service will stop in several minutes.Īnd these key events showed in event log: (Single-server-failure test passed in any case, and physical-host #2-failure test passed as well) When testing HA, the following issue occurs: Service can continue if any single physical host downs (#1 or #2) Issue Service can continue if any single server downs (FE or BE) More considerations, a 3rd FE costs another Lync Server license and more resource, yet Microsoft hasn’t clearly mentioned that it could cause the following unexpected issue.īE mirroring, BE01 as Principal, BE02 as Mirroring Then why I still chose to deploy such a topology? In a word, the decision-maker made this choice. Microsoft has clearly said that 2 FE topology is supported, but not recommended.

Microsoft lync 2013 issues