Error Being Reported by Replication Monitor CCM 3.3(2c)
I have got a CCM 3.3(2c) clustered of two servers. All operations seems to be running fine. But when I go to Replication Monitor in SQL Server Enterprise Manager Subscriber it is reporting an error "subscriber marked inactive and must be re-initialised. No Sync".
When I forced a syncrhonization it doesn't seem to fix the problem.
Re: Error Being Reported by Replication Monitor CCM 3.3(2c)
Shutting down the publisher for any length of time (2hours or more) is a sure fire way of breaking the cluster replication.
The phones will appear to operate correctly with just the subscriber but there will be small problems that are tell tale signs. Things like you can not make any admin changes, extension mobility will not work and you can not set call forward.
Call manager works on the principal that the publisher is always there and ANY database writes go through the publisher, so if the publisher isn't available then the subscriber will operate with the last known database updates but nothing after that.
Try setting call froward on an extension and you will get a database error in the display.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...