Diagnostics and log files
TO3000 can write detailed diagnostic logs when you need to investigate a problem or provide evidence to AIT Support.
Where TO3000 stores logs
Section titled “Where TO3000 stores logs”Start with this folder:
C:\ProgramData\AIT\Logs\TO3000\The local TO3000 API service uses the sibling folder:
C:\ProgramData\AIT\Logs\TO3000 API\TO3000 Setup also places installation diagnostics under the shared AIT log tree.
If the shared ProgramData folder cannot be used, TO3000 can fall back to its per-user Debug Logs location under %LOCALAPPDATA%\AIT\....
Enable logging
Section titled “Enable logging”TO3000 has two separate logging controls:
- Whether logging is enabled. Start TO3000 with the
-lcommand-line switch. - How much detail is recorded. The default level is
INFO. Supported levels includeDEBUG,INFO,WARN, andERROR.
Adding a log level by itself does not enable logging. The -l switch is still required unless support asks you to use a diagnostic override.
Enable detailed logging for one launch
Section titled “Enable detailed logging for one launch”For a temporary DEBUG session, open Command Prompt and run:
set PROJETEX_LOG_LEVEL=DEBUG"C:\path\to\TO3000.exe" -lThe environment variable affects only programs started from that Command Prompt. Closing the window returns later launches to their normal configuration.
This is preferable to a permanent registry change when you need one diagnostic run.
What to send to support
Section titled “What to send to support”- Start TO3000 with
-l. - If support requested detailed logging, set
PROJETEX_LOG_LEVEL=DEBUGbefore the launch. - Reproduce the problem once.
- Close TO3000.
- Collect the newest relevant files from:
C:\ProgramData\AIT\Logs\TO3000\C:\ProgramData\AIT\Logs\TO3000 API\, when the problem involves AI/API features.
- Send the requested files through your AIT Support case.
After troubleshooting, stop using the DEBUG override unless support asks you to keep it enabled.