Author Topic: Tracing the Windows Client  (Read 328 times)

Lars Bencze

  • Jr. Member
  • **
  • Posts: 56
    • View Profile
Tracing the Windows Client
« on: November 20, 2017, 04:39:48 AM »
Is there a "secret" way to activate trace logging for the Windows Client? Or at least more extensive logging to the Windows Event Log?
#Multiplatforms #PDFIndexing #TSM #DB2 #Customizing #Integration #UserExits

jsquizz

  • Full Member
  • ***
  • Posts: 219
    • View Profile
Re: Tracing the Windows Client
« Reply #1 on: November 20, 2017, 07:57:59 AM »
What kind of error are you getting?
#AIX #CMOD #DB2 #TSM #XENOS #AFP2PDF #MIGRATION #TROUBLESHOOT

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 1564
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Tracing the Windows Client
« Reply #2 on: November 20, 2017, 02:55:27 PM »
There's nothing in the documentation, but you could always try the /D, /V, /1 and /2 options ("D" for debug, "V" for verbose output, and the trace options from the other IBM CMOD tools.)

Of course, if you're having an issue, a PMR would be the best way forward.

I'll also throw this out there -- if you're trying to get SSL working, I've seen bad SSL certs hang/crash early versions of the clients.

Let us know what you're seeing so we can help.

-JD.

#Install, #Educate, #Repair, #Upgrade, #Migrate, #Enhance, #Optimize.

IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SA #Performance #Security #Audits #Customizing #Availability #HA #DR #Training