Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
Can Litespeed console recognize when an always on group listener is being used as a central repository?
Description
Can the Litespeed console recognize when an always on group listener is being used as a central repository? As long as the central database is on the primary sql server which is the original server, everything functions normally. But if you make a failover on the secondary, then the synchronization has gone, because LiteSpeed seems to work only with the original server name or instance, not with the always on availability group listener (or Virtual Network Name).
Steps to Reproduce:
Create an always on group and always on group listener for the central repository server. Use the always on group listener name in the instance configuration wizard. Open the LS console and note message displayed (“The instance is not reporting to the central repository”) when the always on group replica for the central repository is rolled over from primary to secondary.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.
Welcome to Quest Support
You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.
The Quest Software Portal no longer supports IE8, 9, & 10 and it is recommended to upgrade your browser to the latest version of Internet Explorer or Chrome.