Main Menu
Open a Ticket
My Ticket History
Browse Knowledgebase
My Account

Register | Forgot Password?

Search by keywords:

Contact Us

We always recommend that you open a new ticket describing your problem and your environment. You will receive an automated reply with a request ID and shortly thereafter further communication from Open iT support.

You can also call the support hotline 1-866-OPEN-IT-S (+1-866-673-6487) or your local Open iT office during office hours for phone support.

Howto: Activate Logging (Windows)

Article ID: 000018
Rating: 5.0 / 5.0 (3 votes)
Views: 3273


How to activate logging on the Windows client, for the main service, and for individual applications.


For the main service, activating logging is a bit tricky.

A. First...

  • Go to the directory "[installdir]/Configuration/Components"
  • open log.xml (in an xml editor or a plain text editor.)

(More Info:

Notice how the file is structured as objects with sub-objects. At the top, there is the object named "log". It has several sub-objects, like "time", "rotation", "global", etc. Some of these in turn have sub-objects. We reference a specific sub-object somewhere down the line by using dot-notation. I.e. "log.rotation.scheme" refers to the "scheme" sub-object of "rotation", which in turn is a sub-object of "log", the main object in the file.

Logging is divided into two parts, debugging and informational/error logging. The two are independent, and can be configured independently.

B. Second, updating the file:

  • Go to ""
  • To include all possible informational/error messages, change the value of this object to "NOTICEOR
    • To only include warnings (and more serious messages, like error and fatal), change the value to "WARNING"
(Possible values are: "NOTICE", "WARNING", "ERROR", "CRITICAL", "FATAL", "NONE". )

  • Move to "".
  • To turn ON full debug, change the value of this object to "5".
(Note: You can specify 5 debug levels + zero for no debug.  To turn off all debug, change to "0".)

We have now set the global levels, but this won't provide any more log messages unless we also modify the values for the log output channel.

For debug, you want to change the "debug" channel settings.

  • Move to "log.channels.debug.severity"
  • Set this to "NOTICE"
This will ensure that this channel logs all possible informational/error messages.


  • Change "log.channels.debug.debug-level" to "5" (or whatever debug level you want).

To activate the changes:

You must restart the service. This you can do either by opening the service manger (found in "Control Panel -> Administrative Tools"), or you can run cmd, and type "net stop openitclient", followed by "net start openitclient" once the service has stopped.

To change debug level for individual applications:

edit the appropriate xml file. For example "licpoll.xml". (Located in the same directory as "log.xml".) You should find a "debug-level" object somewhere, like at "licpoll.log.debug-level". Change the value of this object to "5" for maximum debug.

For a program like licpoll, you can activate the configuration changes by entering "[installdir]bin", and executing "ConfBuilder.exe". Or, you can follow the same procedure as for the main service, by restarting it. The next time licpoll runs (or when the service starts again), it will run with the new debug settings.

<< back

Did you find this article helpful?

Related Articles
Howto: Feature-Mapping
Howto: Processing of FLEXlm Debug Logs
Howto: Setup Oracle Space Data Collection without Running as SYS/SYSTEM User
Howto: Complete Input Logging for Licpoll