How To Enable Debug Logging For The Connector ID Key Agent

Product: Stratusphere FIT/UX       

Product Version: N/A

Expires on: 365 days from publish date

Updated: August 16, 2016



Liquidware Labs Support requested that I turn on debug logging for the Connector ID Key agent.


Possible Resolution(s):

  1. Log into the Windows desktops that is experiencing issues using credentials that have administrative privileges.
  2. Navigate to the Control Panel and open the Connector ID applet.
  3. In the Connector ID applet, navigate to the Status tab. If the Connector ID services are running, click on the Stop Connector ID button to stop all Connector ID Key services.
  4. Using the Windows Start button, navigate to the Notepad application, right-click on it and select Run as Administrator.
  5. In Notepad, click on File > Open menu to browse to and open C:\Program Files\Liquidware Labs\Connector ID\logconfig file. Change the default LOGLEVEL: 1 line to LOGLEVEL: 6. Save the file. If you have not used Run as Administrator, Windows may NOT allow you to save the changes to the file.
  6. Using Windows Explorer, navigate to C:\Program Files\Liquidware Labs\Connector ID\ folder and delete only the following TXT files. These files will be recreated when the CID Key services are restarted.
    • a. tntgrd_log.txt,
    • b. tntupdsvc_log.txt,
    • c. tntuidsvc_log.txt, and
    • d. stats.txt.
  7. In the Connector ID control panel applet’s Status tab, click on Start Connector ID button to restart all CID Key services.
  8. Please wait for at least 1 or 2 callback intervals to collect enough logs. In most cases, the default callback interval is 60 minutes.
  9. After waiting for at least 1 callback interval, use the Connector ID control panel applet to stop CID Key services by clicking on the Stop Connector ID button again. Once stopped, please ZIP the following files and send them to your Liquidware Labs contact for analysis:
    • a. tntgrd_log.txt, 
    • b. tntupdsvc_log.txt,
    • c. tntuidsvc_log.txt,
    • d. SummaryReport.txt,
    • e. UpdateRequest.txt, and
    • f. stats.txt.

IMPORTANT NOTE: Be sure to change the logging value back to 1 and restart the services after testing period is over. The files will continue to grow rapidly if that value is not changed back to 1.

(PDF with detailed instructions attached)

*See this KB for scripts to enable DEBUG mode remotely on a larger scale:

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.