In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com




Additional Logs
For further troubleshooting, review the logs located in QXOsrvInstallDir \logs. The log naming convention for the various services is session- <numeric-instance-segment>-<service name> .log. For example, an event service named ES1 may have two agents, Inst001 and Inst002. The log files would be in 001-ES1.log and 002.ES1.log.
There are no subscriber logs. Troubleshooting subscriber problems should be done on the subscriber side.
To control log detail, you can edit your start-sess.sh or start-sess.bat file. Open the file in a text editor, locate the LOGLEVEL entry, and change the logging level as desired:
 
0
Only level 0 messages and one required level 1 message displays.
1
Level 0 and 1 messages display.
2
Level 0, 1, and 2 messages display.
By default this value is set to 0. This is the recommended setting. If you are having trouble debugging an issue, you can change the logging level to display additional errors and messages.
The AppServer broker and server logs, if set up as described during installation, will be named QXOSession.broker.log and QXOSession.server.log, respectively. Refer to Installation Guide: QAD QXtend.