EN
Español
English
Português
    Self-Diagnostic Agent

    This functionality allows a diagnosis of the ADM modules, required for the operation of the agent; includes communication tests to the ADM site, site and local communication ports, verification of permits and status of the services required in the equipment, for the operation of the modules. To perform the self-diagnosis process, perform the following steps:

    1. Download and save the package Aranda.Diagnostics.ADM.Agent.Cli.9.x.x.x.zip on a specific route, then unzip it. Once done, you will find two files: appsettings.json and Aranda.Diagnostics.ADM.Agent.Cli.9.x.x.x.exe.



    2. Modify the file appsettings.json on line two URI by the URL of the node, where the agent points or will point.


    3. Run the file as administrator Aranda.Diagnostics.ADM.Agent.Cli.exe; Once executed, the utility vehicle performs the tests of architecture, services, accesses, permits, communication ports.


    4. Once the diagnostic process is complete, close the window by pressing any key or manually closing the window. The test result is stored in the utility path, in the Reports, the file is saved diagnostics.json and you will be able to view it in an available text editor.

    Resulting file


    Viewing Results in the JSON File


    Utility execution results as administrator, administrator role, and WMI service status


    Admin$ resource access results, permissions, and status of location services



    WebSocket and HTTP Communication and Registration Test Results to the Outbound Remote Management Component

    ⚐ Note: Once the self-diagnostic tests are finished, it is recommended to delete the test record(s) created in the console, depending on the number of executions of the utility. If there are multiple records, you can delete them by filtering by status No inventory and agent 9.12.2110.106 and then go to More options > All and then Remove devices.


    TLS minimum version verification results and communication with MQTT


    Verification Results Inventory Loading on Server


    Common errors in running self-diagnostics

    When running the diagnostic, you may encounter different errors due to some local restriction in firewall, antivirus or network problems:

    1. Communication Error to Node Configured in File appsettings.json


    Cases of error are caused by a communication restriction to the URL being tested. Validate first if it has an Internet outbound and review the network restrictions configured at the firewall level and make the exception to the node URL.

    2. Error downloading agent profile or agent installer .EXE


    Las causas más comunes para este error pueden ser:

    • When pointing to a Conserver, they are presented by the absence of the resource in the Conserver’s file storage path, . You can run the self-test again so that it runs correctly. On the first failed run, the Server processes the task that requests the resource and then stores it.
    • Regardless of the node on which the test is performed, in the case of downloading the .EXE from the agent installer; The possible cause of the error is that the task in charge of downloading the resource has not been executed, for more information see Deploying Agents.
    • Check antivirus exceptions, as it may be blocking downloading from sources outside of those authorized by the company.

    3. WMI Service Query Failure

    This error is caused by a service failure Windows Management Instrumentation (Winmgmt); Check if the service is enabled and started or if it is not blocked by any domain policy.

    4. Failure in remote administration

    There are two situations for this failure:

    • LAN Remote Management:


    If you have the agent installed, check from the Network > Resource Monitor > Listening Ports that the Aranda.Agent.ACOREService.exe process is running on port 9025. Validate that in the Firewall Status say Allowed, not restricted; otherwise, confirm the firewall rules.


    • Remote administration by outbound connection:


    The most common causes for this error can be:

    • The lack of HTTPS configuration on the node that is being diagnosed. For more information, please consult the following links according to your infrastructure:
    • The lack of the WebSocket component in roles and features.

    5. Failure to verify minimum TLS.


    Verify that the server meets the minimum requirements, such as the minimum supported version of TLS (1.2). For more information, see the note Things to keep in mind Requirements.

    6. Failure in location services.


    The most common causes for this error can be:

    • The Geolocation Service (LFSVC) It is not enabled or has access restrictions by domain policy.
    • You have domain policies configured with location access restriction. If any of these registry keys are created with DWORD = 1, they must be deleted:
    • Registry Key: Software\Policies\Microsoft\Windows\LocationAndSensors\DisableLocation
    • Registry Key: Software\Policies\Microsoft\Windows\LocationAndSensors\DisableSensors
    • Registry Key: Software\Policies\Microsoft\Windows\LocationAndSensors\DisableWindowsLocationProvider

    7. Communication failure with the MQTT component


    Check the firewall rules for any restrictions on the IP or DNS configured for the MQTT component by port 1884 or validate that the MQTT service on the server is operational.

    8. In uploading inventories to the server.


    The most common causes for this error can be:

    • You don’t have a valid local file storage path or blob storage configured for the node you’re targeting. For more information, see Communications
    • You don’t have read and write permissions on the local file storage path or blob storage that you have configured for the node you’re targeting.

    In the following link you can find the executable of the self-diagnostic agent Self-Diagnostic Agent