Hi,
I did some research on this issue, but haven't come to a conclusion yet. If
you have several machines connecting to the same Team Foundation Server,
does this also happen on other machines? This will help us to narrow down
the issue, so that we can find if this is a server side problem or client
side one.
Kevin Yu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
piers7 - 22 Oct 2006 14:13 GMT
Ok, whilst this used to be pretty regular for me (reproducable on 100% of
check-ins), it hadn't happened for a while (a good two months or so). But it
happened again the other day.
What's more I have now seen this happen on another machine (but just the
once). We have a team of about 20+ developers checking stuff into this TFS
box all the time, so I'd be surprised if it was a server-side issue (I'd
expect to see it much more often).
Final versions of VSTS and VS2005 in use (not using beta service pack for
VS2005)
Kevin Yu [MSFT] - 23 Oct 2006 09:24 GMT
Hi,
Yes, as you can see, this is a Visual studio client error. Based on my
research, it is a known issue. Here is a KB article talking about this
issue.
http://support.microsoft.com/kb/922531
A hotfix is available now. You can contact Microsoft PSS to get the hotfix.
The link to the contact information is in the article.
HTH.
Kevin Yu
Microsoft Online Community Support
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)