Turning on Axess Smart Printer logging
Note: Users must have write/modify permission to the Program Files\Axess AG\Axess AG AxCoding folder to gather AXCoding logs.
To enable AX Coding logging (typically used to troubleshoot encoding issues), add the following tag to an Axess Smart Printer layout, sell the item and print/encode.
<logging>1</logging>
0 is off, 1 is on
Note: It is not a verbosity level of 1-5 as it is for Siriusware logging…
This logging does not add anything to the Sales32c_log.txt, but does create a full set of information here:
• C:\Program Files\Axess AG\Axess AG AxCoding
Or for 64-bit computers, here:
• C:\Program Files (x86)\Axess AG\Axess AG AxCoding
There are many files located in this directory, but the relevant files for troubleshooting all end with .log*.
There are two scripts that can be used to globally add or remove the logging tags from all Axess Smart Printer layouts in Siriusware.
Note: these update statements assume the Axess layout is:
• in t1_layout
• To turn logging on for all Axess ticket types:
update items set t1_layout = '<Logging>1</Logging>' + cast(t1_layout as varchar(4000))
where prn_tkt1 = 4
and datalength(t1_layout) > 0
and t1_layout not like '%<Logging>1</Logging>%'
-- To turn Logging Off for all Axess Ticket Types
update items set t1_layout = replace(cast(t1_layout as varchar(4000)), '<Logging>1</Logging>', '')
where prn_tkt1 = 4
and datalength(t1_layout) > 0
and t1_layout like '%<Logging>1</Logging>%'
Additionally, logging can be forced “on” by using the following Sales32c.INI settings (this can be used as an alternative to turning logging on within the Axess Smart Printer layouts):
[Preferences]
VerbosityLevel=4
AxessLogging=TRUE