error retrieving data using RTC and MS visual studio
Hi,
in our development team we have often a weird situation. After some time of inactivity in RTC, we are being disconnected, and after we reconnect again, we got a message about error retrieving data.
After doing refresh, we are prompted to reload projects, where we sometimes loose our changes which were in local repository.
Did anyone else have this problem?
in our development team we have often a weird situation. After some time of inactivity in RTC, we are being disconnected, and after we reconnect again, we got a message about error retrieving data.
After doing refresh, we are prompted to reload projects, where we sometimes loose our changes which were in local repository.
Did anyone else have this problem?
2 answers
Hi Ralph/Milan,
I'm not sure that this is the same problem as that being tracked by the RTC silently logging off issue. For one, users there never reconnected - Milan says they reconnect after being disconnected - does that mean you log on again, Milan? For another, no one so far has complained that they are prompted to reload and then eventually lose their changes.
What I'd like is to have a look at the error logs. So if you would set your RTC trace level to Info ( via Team Concert->Windows->Team Concert Log) , and reproduce this problem, that would be super. You can then use the Save Log Files button in that same view to save the log files. Please create a work item describing this problem and attach the logs.
Cheers
--Rupa
I'm not sure that this is the same problem as that being tracked by the RTC silently logging off issue. For one, users there never reconnected - Milan says they reconnect after being disconnected - does that mean you log on again, Milan? For another, no one so far has complained that they are prompted to reload and then eventually lose their changes.
What I'd like is to have a look at the error logs. So if you would set your RTC trace level to Info ( via Team Concert->Windows->Team Concert Log) , and reproduce this problem, that would be super. You can then use the Save Log Files button in that same view to save the log files. Please create a work item describing this problem and attach the logs.
Cheers
--Rupa