Category
Versão do produto
Tópico
Subtópico
Enterprise Reporter Network Traffic impact assessment (4374146)
is there a whitepaper or technical document that details the application communications for AD discoveries?<br>Needed to estimate the cumulative network load Enterprise reporter exerts on the network .
Non Trusted Domain Discovery Alternate Port (4368720)
Can we use secure port 636 instead?
We want to create a custom view in the SQL database with db reporter (4369052)
We want to create a custom view in the SQL database with db reporter, will we still be supported if we create and use manually? ... Any change on the database not performed by the product itself or advised by Quest software will leave you out of support for the product in questions for obvious reasons we can't support changes that were made outside of our control.
What permissions are required for an SQL Discovery? (4217085)
What permissions and rights does the account the node is running as (or alternate credentials if supplied) need to perform an SQL discovery? ... The node account (or alternate credentials if supplied) will need to be a member of the local Administrators group on each SQL server you are targeting as well as have the SysAdmin role on each SQL server.
Active Directory Discovery Hangs On Creating Discovery Task Executor Step. (4314879)
When running an Active Directory Discovery to collect group and members and domain controller data it seems to get stuck and hangs at "Creating Discovery Task Executor" step seen in the discovery Activity:
How to subscribe to RSS Feeds/Product Notifications (4316478)
How to subscribe to RSS Feeds/Product Notifications to opt into support notifications to receive emails about the latest software patches, version releases, and updates to our Knowledge Base. ... (Really Simple Syndication)
When the discovery job has finished, we get this 1 error: "One or more errors occurred" (4378682)
When the discovery job has finished, we get this 1 error: "One or more errors occurred" ... Added the Global Reader, whitch was missing. ... But still get the same error. ... Created a new Discovery without adding any scope and we still get the same kind of error.
Computer Discovery fails with error: System.TimeoutException: The operation has timed out. (4376710)
When running a computer discovery the following error is seen:<br><br>System.TimeoutException: The operation has timed out.<br><br><img alt="image.png" src="https://questsoftware.file.force.com/servlet/rtaImage?eid=ka0RP0000006eZ3&feoid=00N6R00000J0qH7&refid=0EMRP0000083fA6"></img><br><br><br><br>Also, if you look at the node logs you may find the same error:<br><br><le ts="2024-05-23T13:35:25.1505318Z" l="ERROR" s="Quest.Reporter.Core.Node.JobManagement.TaskExecutionQueueEntry" t="5779cd94-2e05-47d0-99f1-11720ee810df"><m>ReportException(5779cd94-2e05-47d0-99f1-11720ee810df) called. ObjectName:<br>ErrorDescription: System.TimeoutException: The operation has timed out.<br>ErrorMessageID: Collection being cancelled. Target computer became unresponsive.<br>ErrorMessageStack:<br></m></le> Increase the timeout settings on the <strong>MaxComputerDiscoveryTimeInMS </strong>from the <strong>ReporterNode.exe.Config</strong> file on each of the nodes. You may try to increase this value to 5400000.<br><br><img alt="image.png" src="https://questsoftware.file.force.com/servlet/rtaImage?eid=ka0RP0000006eZ3&feoid=00N6R00000J0qH8&refid=0EMRP0000083j2Q"></img><br><br>If issue persists, you may try increasing more this value to a higher number.<br><br><strong>IMPORTANT:</strong><br>Please note that to increase the above timeout settings, you must follow the procedure outlined under resolution steps from KB article listed below, which includes an example as well.<br><br><a href="https://support.quest.com/enterprise-reporter/kb/4317087/computer-discovery-is-taking-an-unusually-long-time-to-process-hotfixes-on-some-machines" target="_blank">https://support.quest.com/enterprise-reporter/kb/4317087/computer-discovery-is-taking-an-unusually-long-time-to-process-hotfixes-on-some-machines</a><br><br>
Not collecting all instances on SQL Server while running SQL discovery (4378662)
If the SQL server has multiple instances running the SQL discovery against that SQL server, discovery will not collect all instances. ... A bug has been logged. ... Workaround: ... Please follow the steps below to set the correct configuration:
Long timeout when SQL server cannot be found during SQL discovery (4378659)
While running the SQL discovery, if SQL server was not found it will add about 40+ minutes or more time for SQL discovery to complete. ... We have logged a bug for this issue. ... This will be triaged to a future release.
Not able to add a tenant (4378655)
Not able to add a tenant in the Configuration Manager. ... We can access the .json file using https://login.windows.net/.onmicrosoft.com/.well-known/openid-configuration ... We can connect to the tenant using tenant id in PowerShell.
Not correctly collecting from SQL Server Virtual Clusters (4378661)
If the SQL server has many virtual cluster of SQL DB instances, those are not collected by SQL discovery correctly. ... It will show the error during discovery: "A network-related or instance-specific error occurred while establishing a connection to SQL Server"
Azure Active Directory Discovery Error (4378590)
Azure Active Directory/ Entra ID discovery completes with the following error message, even though Global Reader and Report Reader are assigned to the Azure credentials: ... ErrorMessageID: Unable to retrieve password sync status
Account Authentication Failed When Deploying Node. (4314090)
Service account entered into Credential Manager in FQDN Format fail to authenticate when deploying a node in a server that exist in the same domain in which Enterprise Reporter exists. ... Instead of adding service account in FQDN format, add it in DOMAIN\userid format under Credential Manager.
Computer discovery is taking an unusually long time to process hotfixes on some machines (4317087)
Discovery time is taking an unusually long time to process due to the high number of hotfixes on some of the machines. ... Some computers within the Computer discovery are timing out after an hour.
Required runtime version (4378555)
Visual C++ 2013 Redistributable (64bit) ... Visual C++ 2015-2022 Redistributable (32bit and 64bit) ... Are those necessary or can be uninstalled? ... they are both needed for the current ER version
How to manually update the discovery status from database using query (4378508)
Sometimes, discovery is stuck in processing state and options to cancel and delete are greyed out, seems stuck somehow. ... In this case, please try restarting the "Quest Enterprise Reporter Server" service and then see if it lets you make the changes to the affected discovery.
Is it possible to collect database instance level permissions for SQL Server? (4378408)
Is it possible to collect database instance level permissions for SQL Server? ... The enhancement ID 496348 has been logged to consider collecting database instance level permissions in a future release of the product.
How to move the Enterprise Reporter database to a new SQL Server (4269823)
Need to move the Enterprise Reporter database to a new SQL server <p class="MsoNormal" style="margin: 0in 0in 10pt;">These instructions assume that you have the necessary SQL permissions to access SQL Server Management Studio on both the current and new SQL Server to backup and detach the database, as well as the appropriate Windows account permissions to copy the database files from one server to another, and to stop and start services on the Enterprise Reporter server.</p>
SQL Server Role Membership by Account report doesn't show role membership information (4378466)
<p>SQL Server Role Membership by Account report doesn't show role membership information</p> <p>Enhancement ID 542009 has been logged to consider include a new version of the SQL Server Role Membership by Account report in a future release of the product. </p>
Discoveries are stuck in the "Pending" or "Processing" status (4370356)
Some discoveries are stuck in the "Pending" or "Processing" status and they cannot be modified or deleted. ... There could be a lot of reasons why sometimes a discovery gets stuck in the "Pending" or "Processing" status.
Ports used by Quest Enterprise Reporter (4247206)
<p>This will outline the ports needed for each type of discovery, as well as server and node communication.
NTFS Discovery performance - Best Practices (4291009)
The NTFS discovery is taking a very long time to complete (days, weeks) or the NTFS reports take a very long time to complete. ... This article outlines some best practices to ensure the discovery and reports are running optimally.
Minimum permissions to perform a Active Directory Discovery (4216607)
What are the minimum permissions to perform an AD Discovery? <p>An Active Directory Discovery can be performed with any active account of the domain as the AD Discovery needs only READ permissions on the domain structure i.e any account member of 'Domain Users'.</p>
How to reconnect Enterprise Reporter to the database? (4220759)
Click Next ... Provide the SQL server name and the name of the database, click Next and complete the rest of the wizard
Associação de novos produtos
- Ferramentas de autoatendimento
- Base de conhecimento
- Notificações e alertas
- Suporte a produtos
- Downloads de software
- Documentação técnica
- Fóruns de usuário
- Tutorial em vídeo
- Feed RSS
- Fale conosco
- Suporte técnico
- Visualizar tudo