The log captures "ERROR" messages by default, but can be re-configured in the ETL section of the log4j.properties if you need to finer tune the logging to capture more information.  To start, I'd look for any "ERROR" type messages and provide the details here if you can.  Support however may ask you re-run the ETL with the log configured for "DEBUG" if there are no errors, or the errors do not reveal what the problem is.  It is also possible that exceptions are thrown in the application log (ie - rm.log, qm.log, etc...), which is why I thought the ISALite Data Collection would be helpful, although I certainly understand your policy may prohibit you from sharing the details.

Hi Rodney,

The best place to start looking is in the ETL logs.  These should be located in the server install directory in the logs folder (ie - C:\IBM\JazzTeamServer\server\logs). You should see the following logs:

ccm-etl.log for CCM
qm-et.log for QM
jts-etl.log for JTS and RM

You can also run the ISALite Data Collector and provide it in your PMR by going to C:\IBM\JazzTeamServer\support\ISALite and running "runISALite.bat" which will collect all the logs from the server as well as some other helpful information for support.  Hope it helps,