TFS, Team Foundation Server Explorer error on VS 2008 always disconnects
Blog Date:
Tuesday, May 20, 2008
Our network went down and when it finally was restored, I kept getting errors working with solutions bound to source control. I am running Visual Studio 2008, Team Foundation Server 2005, and Windows XP SP2. Here is what happened:
First I would open a solution and I would get this error:
"The solution you have opened is under source control but not currently configured for integrated source control in Visual Studio. Would you like to rebind this solution to source control now?"
Then I would get a dialog for
"Change Source Control"
The prompt above doesn’t work. So I manually have to select “change source control” and I get this…
"Change Source Control - MySolution.sln
The current solution is associated with source control but is offline. Would you like to completely disassociate the solution from source control?"
I click no. Nothing happens. I try it again, same message.
So I click yes. Nothing happens. But this time, I try it again and I get the same “Change Source Control” dialog and I can bind it again. So, now everything is working normally. SO IT SEEMS...
Problem is I close and re-open and I go through this whole charade again. Including having to “Add Existing Team Project” from TFS again. When I select the servers available for TFS, all the information remains. And it doesn't allow me to remove the TFS server.
- I tried repair / modify on Team Explorer. Nothing.
- I tried uninstalling Team Explorer, then re-installing. TFS Server information is still there. Nothing.
My solution:
I hate this kind of solution, but I uninstalled Team Explorer and VS2008 completely. I then re-installed it. It still saved my TFS server information and my problem was still there. BUT this time I was able to remove the TFS Server. I closed it down, re-added it and now it opens by default every time. And now my solutions are binding correctly and maintaining them.
I found also this on the web:
I had a similar problem, which I've now figured out, in Visual Studio 2008. (Also working with TFS, but I don't think the issue I had is specific to TFS source control): I said "yes" when the project asked if I wanted to open disconnected from source control. It turns out Visual Studio 2008 has a new feature that allows you to take your solution offline, then when you put it online again, it prompts to check out any files you've touched offline. The way to reconnect is to right click the solution file and choose the option to go back online.
I didn't know this, and instead tried to go back online the old way: tried opening File / SourceControl / ChangeSourceControl dialog. I got the following message and said yes, (which turned out to be a mistake):
"The current solution is associated with source control but is offline. Would you like to completely disassociate the solution from source control?".
After that, I was able to go again to File / SourceControl / ChangeSourceControl and Bind the projects to source control there (as described in the post above). --------- BUT --------- when I closed Visual Studio and reopened it, even if I was on the network, the same thing happened again - instead of defaulting to connected mode, it defaulted to disconnected mode, and the only way to connect was to go through the whole source control re-binding every time I open the solution.
I did not find a way to fix from that point, but once I deleted the whole project from my hard drive and did a new "Get Specific Version" from TFS with "overwrite files that are not checked out" checked, the newly downloaded project was okay (it did NOT work to just Get Specific Version without first deleting the project from my hard drive).
Also, in the Output window throughout all this, even when I was on the network, it said the following - which was correct in saying the solution was offline, but incorrect in saying the Team Foundation Server was offline:
This solution is offline. [Team Foundation Server: http://<myserver'sname>/]
The solution is offline because its associated Team Foundation Server is offline.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Tuesday, May 20, 2008 3:27:29 PM