Diagnosing "New ADC" (Automated Data Collection) issues (aka X3Services)

You have implemented "New ADC" (Sage X3 Services) following the online help located at https://online-help.sageerpx3.com/erp/12/public/getting-started_Sage-X3-Services-installation.html

When trying to use ADC you are experiencing some issues and need to know how to get additional information about the cause of the problem.

CAUTION: Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst.

You may find that enabling debug level logging will provide additional information to be able to trace the root cause of your issue. To do this, :

• In your X3 services "xtrem-config.yml" file (located in the "INSTALLATION BASE" directory, such as "D:\Sage\x3services") add the log entry as below.

storage:
    managedExternal: true
deploymentMode: development
logs:
    disabledForTestsx: false
    domains:
        sage/xtrem-x3-gateway/storage:
            level: verbose
        sage/xtrem-x3-gateway/web-service:
            level: verbose
        sage/xtrem-x3-sql-manager/sql:
            level: debug
        sage/xtrem-service/service:
            level: debug
        sage/xtrem-service/http:
            level: verbose
        sage/xtrem-core/graphql: 
            level: verbose
        sage/xtrem-x3-gateway/api-helper: 
            level: verbose


NOTE: The spacing is essential, so should look like below (4 spaces for each indent)

• Restart X3Service windows service to ensure the change is picked up and this also cycles the X3 services log file
• Reproduce the issue, then review the x3service log file "xtrem.server-XXX.log" (located in the "INSTALLATION BASE\logs" directory, such as "D:\Sage\x3services\logs") and also the Syracuse logs 
• Once diagnostics are completed, revert the changes and restart the X3Services windows service