Troubleshooting Communication Issues with the PTC Server
Occasionally there are issues with the PTC Server connection connecting to or communicating with the PTC Server. When this happens, you can generate a set of log files to troubleshoot the issue.
Follow these steps to generate the log files:
1. On the PTC Server, add the following parameters to the PTC_SERVER_Install\codebase\wt.properties file to enable verbose logging:
◦ wt.method.verboseServer=true
◦ wt.method.serverMethodTiming=true
◦ wt.method.clientMethodTiming=true
◦ wt.httpgw.verboseServer=true
◦ com.ptc.core.logging.defaultLevel=debug
This step generates Method Server logs in the PTC_SERVER_Install\Windchill\logs folder.
2. On the PTC Server connection client, set the following environment variables to enable logging:
◦ PTC_LOG_DIR=path_to_folder
Set this variable to the path where you want to store the log files.
|
|
Do not use $PTC_LOG_DIR or %PTC_LOG_DIR% in subsequent variable definitions.
|
◦ APTBURSTLOG=path_to_folder\burst.log
◦ PTC_LOG_CONFIG=path_to_folder\logging.cfg
Create a logging.cfg file on your system. Set this environment variable to point to this file. Use the following content for the logging.cfg file:
verbose_level DEBUG
enable CIPSOAP DEBUG
enable UWGMCLNT_PDM_ACTIONS DEBUG
enable UWGMCLNT_CAD_ACTIONS DEBUG
enable PROWT_PDM_ACTIONS DEBUG
enable UWGM_COMM DEBUG
enable Communication DEBUG
enable ContentPlugin DEBUG
enable CurrentLogger DISABLED
enable DBObjectIBA DEBUG
enable Download DEBUG
enable HTTPDownload DEBUG
enable LocalCache DEBUG
enable Merge DEBUG
enable PartIBA DEBUG
enable Persistance DEBUG
enable Profile DEBUG
enable RefTable DISABLED
enable ServerCache DEBUG
enable ServerDownload DEBUG
enable ServerProfile DEBUG
enable ThreadQueue DEBUG
enable ToDo DISABLED
enable Upload DEBUG
enable WorkspaceCache DEBUG
enable WfImport DEBUG
enable DetailActionInfo DISABLED
enable Wildfire DEBUG
enable UWGMLIB_CONTENT_MANAGER DEBUG
enable UWGMLIB_PREFERENCES DEBUG
enable UWGMCLNT_PREFERENCES DEBUG
enable UWGM_CADADAPTER_TRL DEBUG
enable WINHTTP_STREAM DEBUG
◦ PTC_LOG_ACTIVATE=t
◦ UWGM_PRINT_XML_FILES=t
◦ UWGM_LOG_ACTIONS=t
◦ UWGM_LOG_DOWNLOAD=t
◦ UWGM_LOG_TASK_QUEUES=t
This step generates a series of request_ and response_ files and a applog.log file in the specified folder.
3. On the PTC Server connection client, set the following parameter in the Arbortext-path\adapters\com.ptc.arbortext\userprefs.xml file:
Set the file parameter value to a directory path and base file name for the log to enable logging. The path must be for a directory that already exists. Arbortext Editor uses this value to create a log file containing its unique process ID (PID). The log file name takes the form filename-PID.ext, where the file name and file extension are specified by the parameter setting, and PID is the process ID for the active Arbortext Editor executable. For example, if you set the parameter to the following value:
C:\temp\ptcServer.log
The PTC Server connection might create a log file such as the following:
C:\temp\ptcServer-1332.log
Each log file is cumulative for its unique process ID.
Use the log files to troubleshoot your communication issues. If you need to open a case with PTC technical support, attach the log files to your case.
