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
|