Prior to downloading this Software, you must review the Software Transaction Agreement located here and confirm, by clicking the I agree check box below, that your organization accepts and is bound by the terms and conditions of the Software Transaction Agreement for this Software.
If you purchased the licenses for this Software by executing an order form with Quest or if you have an agreement with Quest that states that all purchases are governed by such agreement, then the terms and conditions of that agreement supersedes and takes precedence over the Software Transaction Agreement.
SQL Server connection errors can include the following:"Monitored Server - SQL Server Connection Failure Cannot connect to SQL Server instance '<instance_name>' : Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. : The wait operation timed out [0xFFFFFFFE]""Monitored Server - SQL Server Connection Failure ...
What account is used and required to execute PowerShell scripts in Alarm Actions? Diagnostic Server account owner or the account used in connection Properties window?What account is used and required to execute SQL scripts in Alarm Actions? Diagnostic Server owner account or the SQL Auth account used in connection Properties window?
In Azure SQL, its premium range has Read Only Replica, which you can connect with ApplicationIntent=Readonly.This can't be set this in Spotlight. In the proxy, you can only give the database name, to monitor a readonly replica. Spotlight needs to use a connection string with "ApplicationIntent=ReadOnly"
Spotlight has stopped monitoring a Windows connection. The following error is received:Monitored Server - Windows Collection Execution Failure: Collection 'Processors' failed : WMI query 'Win32_PerfRawData_PerfOS_Processor' failed : Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
Spotlight Diagnostic Server is installed on a host outside of the region of local machine used to login to the Spotlight Cloud Web UI. The timestamps of the application (alarms, collections etc.) reflect the local machine and not the Spotlight Diagnostic Server timezone.