The logs will be located as follow

The Avatax Addon logs: C:\log 

The Avatax WebUI logs: C:/logs/AvataxWebAPI_    

The Avatax Event Service (AES) logs: The logs will be within the folder where the service was installed.

Important:

• By default, the log files of the AvaTax addon are stored in C:\log, as defined in the log4net.config file. This configuration applies both to the addon and to the AES. The addon will attempt to save logs in this default folder using the filename specified in that configuration.See below.

The log is a local file created on the PC where the AvaTax addon is running and it cannot be used by multiple processes at the same time. For example, if 10 users are connected remotely to the same server, only the first addon process started will write to the log file. Other addon sessions will not be able to write into the same file.

• If you prefer to generate a separate log file for each process, you can edit the log4net.config file:comment line 4 and uncomment line 5 as shown below.

This will instruct the system to create an individual log file per process. Each file name will include the process ID. You can then identify the corresponding process and user in the Windows Task Manager (the AvaTax process will show with its process ID).

• Another common scenario occurs when both the Test and Production environments share the same log file. This happens because the log4net.config file uses the same default log name for both databases.

If you want to separate them, simply update the log file name in the configuration. For example: AvataxLogTest and AvataxLogProd

This way, each environment will generate its own dedicated log file.