#Windows testview on restart code#
#Windows testview on restart windows#

#Windows testview on restart windows#

I'm not sure if dumprep.exe is part of Watson or not, but it's the standard dialog from windows to submit a dump. Is this the type of information you're looking for?įor more information, see Help and Support Center at. (I see the other reply with a phone number different than the one I'm trying. After a while, we gave up for a while to see if someone in our server group had a better number to call. I was trying to create a support incident a couple of times earlier today, but while being transferred the phone is being disconnected.

#Windows testview on restart code#

Any insight into how this might be related to source code control? I don't know why this would be related to opening the Test Results window unless you were doing an action (like publishing results, or opening results from the TFS server that were already published). Does it only happen with a certain solution/project? Based on your report, this corresponds to the being connected to a TFS server. Is that via Watson? Can you look at your event log to find a report of the submission and reply with data in the body of that event? It will help us pinpoint the info you submitted so we can attach that to this investigation.Īlso, if you can provide anecdotal data to help us narrow the repro. I see you mention you are submitting the dumps. We are likely going to need help from customers like you who are experiencing this to get some debug info. I'm really sorry for the trouble this is causing you and I don't want VS to be causing you to be frustrated. Although we've not been able to reproduce this internally, we've opened a bug for it and are actively trying to investigate it. We've recently heard a few other folks report this problem. Restarting the services is getting really old, so an even better question is 'Does anyone know of a way to fix or stop this behavior in the first place?' Has anyone else encountered this error? I've searched google and the news groups but haven't come across anything similar. (Restarting the TFS service does not fix the test results window by itself. However, we will usually lose access to source control sometime after the behavior starts, and restarting the service allows source control operations to work again.)

Generally, we have the server folks restart IIS and the TFS service before the behavior goes away. When this happens, it is for every developer connection to the same TFS server. (I'm not sure how many dumps I've sent after using end task, but there have been more than a few.) In a nutshell, every few days displaying the test results window hangs VS.NET and requires the user to close VS.NET before being able to use it again. We are running vs.net 2005 with service pack 1, and are having a massive problem with the Test Results window.