Follow the instructions below to obtain the Umango application logs. You can configure various log types using the Advanced Configuration screen, depending on the required information.
logging.server
option must be enabled for other logging types to function.logging.trace
option must never be enabled unless explicitly asked to do so by Umango support staff. Serious system degradation and consequences can occur if not used carefully.logging.server
- General server logs that appear in Windows Event Viewer.
Options: error
, warn
, info
, false
, none
logging.device
- Logs for device-side operations (not fully implemented on all brands). Supported on Ricoh, Toshiba, HP, FUJIFILM, Epson, and Xerox (partially). For Konica Minolta devices, refer to the specific logging option below. Logs may also be available within the device's own logs, depending on the brand.
Options: error
, warn
, info
, false
, none
KonicaMinolta.OpenAPI.Log.Level
- Specific logging for Konica Minolta devices.
Log Location: C:\ProgramData\Umango\logs\OpenAPISDK1.log
Recommended Option: OpenAPIMessageOnly
Options: All
, Debug
, Error
, Fatal
, Info
, None
, OpenAPIMessageOnly
, Operational
, Warm
logging.ftp
- Logs for FTP activity, which appear in Windows Event Viewer.
Options: true
, false
logging.abbyy
- Detailed logs for ABBYY activities.
Log Location: C:\ProgramData\Umango\logs\abbyy.log
Options: true
, false
logging.trace
- Logs for details thread tracing activity, which appear in Windows Event Viewer. These logs should never be enabled without explicit instructions from Umango support staff.
Options: true
, false
Link to this article https://umango.com/KB?article=140