1. Some older connections maybe missing a configuration property for Extended Events causing the Diagnostic Server to think Extended Events are turned off.
2. Some newer connections may have their XML configuration files with Extended Events parameters set to false no matter what you check in the GUI.
WORKAROUND 1:
For all the connections with the issue, please take the following steps:
2. Re-start the Diagnostic Server.
3. Check the extended events per connection with the issue.
WORKAROUND 2:
1. Go to C:\Program Files\Quest Software\Diagnostic Server\Agent\conf\Monitored_Entity.
2. Open with notepad the XML for the SQL Server connection with the issue.
3. Do a search for "UseExtendedEvents" and it will come up with several but look for entries within the "property" tag as shown in the two examples below:
e.g. A. property dataType="BOOLEAN" description="Specify whether to use Extended Events for the SQL Server connection" displayName="Use Extended Events" editedAt="1529595755519" editedByUser="Unknown" encryptStyle="NONE" hidden="false" name="UseExtendedEvents" false /property
e.g. B property dataType="STRING" description="UseExtendedEvents" displayName="Useextendedevents" editedAt="1526687813896" editedByUser="PROD\jlin" encryptStyle="NONE" hidden="false" name="UseExtendedEvents" false /property
4. Edit the end of the script by changing "false" to "true".
STATUS:
A fix is available in Spotlight 12.3.1 and higher. To download the latest version of Spotlight on SQL Server Enterprise, click here.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center