It's all about the answers!

Ask a question

Where can one find exact error mesage in RTC VS plugin


Karthik Krishnan (8899122164) | asked Aug 16 '12, 5:16 a.m.
edited Aug 16 '12, 5:16 a.m.
Our users are using VS 2010 with RTC 3.0.1 plugin. Randomly they are facing errors while loading the sandbox. The logs are around 100 MB

My question is how and in which file can I find the exact error message?

For example, trace-*.txt does not contain any valuable information.

One answer



permanent link
Prabodh Mairh (3812) | answered Aug 17 '12, 2:26 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
The messages in the file trace-xxxxxxxxx.txt file may depend on the level of logging, which can be set from  "Team Concert Log" window in the client.
There are some .daemontrace files under "trace" folder, they also contain information which can help us debug.

What is the error message that you see on screen. Does it contain any details?

Comments
Karthik Krishnan commented Aug 17 '12, 11:07 a.m.

When a colleague loaded his sandbox he received 1. First time "File system daemon for D:\xxxxx has not been started correctly" 2. second time he got error "Notification thread already started"

There are not a lot information we can get from the saved logs


Sreerupa Sen commented Aug 21 '12, 12:55 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

To set the trace level across sessions, please have a look at https://jazz.net/library/article/601#How_Turn_On_Tracing. Setting the trace level via the log view sets it just for the current session.

Once you've set the trace level, you could choose the 'Save Log Files' option in the Log View - this zips up the VS trace files and also the daemon logs. If you create a work item on jazz.net and attach the zip, we could have a look at what might have happened.

Trace level should be set to Info or Verbose.

You could also post the error message including the stack trace in the forum - at the Info trace level.

Cheers --Rupa

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.