4 |
Click Apply. |
• |
• |
If your discovery fails for all tasks, it is possible that your shared data location is the problem. The shared data location may no longer exist, or the node may not have adequate access to it. Check the errors on the discovery task to investigate. For more information, see Viewing Errors and Error Suppressions . If this is the issue, ensure the shared data location belonging to the cluster exists and is properly permissioned. Shared data locations are not used for Active Directory, Exchange, or NTFS discoveries. |
• |
The node may not have access to that server. Check your credentials, and change them if necessary. For more information see Node Credential and Alternate Credential Details for On-Premises Discoveries and Modifying Node Credentials . |
• |
If you have used alternate credentials for the discovery, ensure that they are permissioned properly. For more information, see Node Credential and Alternate Credential Details for On-Premises Discoveries and Detailed Permissions for Enterprise Reporter Discoveries . |
• |
The task may have been rejected. If a task is rejected, it means that it is currently being collected by another discovery. Due to the way the Enterprise Reporter collects data, collecting from a SQL Server® in more than one discovery can result in data loss. You could only create one discovery for each SQL scope. |
• |
• |
Try running the discovery, and monitoring the Activity column in the Processing Tasks view, or looking at the history of the discovery. This may help you identify the specific activity that is causing performance or data collection issues with the discovery. For more information, see Viewing the Tasks for a Processing Discovery , and Viewing the History of a Discovery . |
There are several features in Enterprise Reporter to help you solve problems.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center