43

Today I selected "Work Items" as I have a million times before but this time I was met with this error along the top of my "Team Explorer" tab:

"Page [some long GUID] not found."

This also happened for "Pending changes".

alan
  • 6,705
  • 9
  • 40
  • 70

6 Answers6

80

To fix the issue simply run the below command in an elevated command prompt as detailed here.

"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe" /setup

My understanding is this command forces the recreation (what Microsoft refers to as "merging") of current VS settings into what is apparently a corrupt settings cache. On the surface, this is similar to deleting the directory path C:\Users\username\AppData\Local\Microsoft\VisualStudio\version and allowing visual studio to recreate it at launch. However, I prefer to not to delete this outright and instead rely on re-merge approach.

Recently I found this sometimes occurs when I launch several solutions at once (i.e. I have 1 or more Visual Studio instances loading a solution at the same time). I also have ReSharper, SQL Prompt, VSCommands and TFS Power Tools installed which I'm sure contribute to some degree.

UPDATE:

This fix should work for all versions of Visual Studio, however you will need to execute the command in the directory appropriate to your version. For example with Visual Studio 2015 the path would be: 

"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe" /setup

Version mappings for Visual Studio (original version mapping answer here):

  • Visual Studio 2005 = 8
  • Visual Studio 2008 = 9.0
  • Visual Studio 2010 = 10.0
  • Visual Studio 2012 = 11.0
  • Visual Studio 2013 = 12.0
  • Visual Studio 2015 = 14.0
  • Visual Studio 2017 = Path has changed to: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE"
alan
  • 6,705
  • 9
  • 40
  • 70
  • 1
    Phew! This turned out to fix it. I was afraid it also resets my VS settings, but it didn't. Nice! – Ray Jul 07 '14 at 21:21
  • That would be nice to know exactly what this command is actually doing though... There is not much details "here"... – CTZStef Aug 21 '14 at 01:23
  • I just did this and it did indeed reset my VS settings. It did at least also fix the problem though. – Bob Horn Sep 02 '14 at 17:22
  • 1
    @Bob Horn It should not reset your settings. My understanding is this command forces the recreation (what Microsoft refers to as "merging") of current VS settings into what is apparently a corrupt settings cache. On the surface, this is similar to deleting the directory path C:\Users\\AppData\Local\Microsoft\VisualStudio\ and allowing visual studio to recreate it at launch. – alan Sep 02 '14 at 18:36
22

Deleting all files in ComponentModelCache folder worked for me

For Visual Studio 2013: "C:\Users\username\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache"

For Visual Studio 2015: "C:\Users\username\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache"

or

%userprofile%\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache

Rashad Valliyengal
  • 3,132
  • 1
  • 25
  • 39
  • In practice, this has been the swiss-army knife of solutions with Visual Studio. I prefer attacking the specific problem and so I find my solution to be more desirable. – alan Oct 22 '17 at 22:49
3

If you get this issue in VS2015 and running "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv" /setup doesn't fix you issue you can try the following:

  1. Close all instances of VS
  2. Delete all files in C:\Users\\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
  3. run "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv" /setup
Craig
  • 31
  • 1
2

This happend also with my installation of VS '13 when I installed VS '15. Removing the files at "C:\Users\username\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache"

did the job for me.

Robijntje007
  • 81
  • 5
0

I encounter the same problem with you, and resolved by run the VS as administrator

Haobo
  • 463
  • 4
  • 9
  • @Haodo Hopefully your suggestion will be of use to others; however, I encountered this error while running as Administrator. I have set Visual Studio to run as Administrator all of the time. – alan Apr 18 '14 at 12:29
  • @Haodo, I do still receive this error infrequently. When I do, the command I listed fixes it. – alan Mar 26 '15 at 13:11
0

Here are the steps I followed. Please make sure you follow them in correct sequence. These steps are for VS 2015. Use 12.0 (instead of 14.0) for VS 2013 and 10.0 for VS 2010

  1. Close all instances of VS
  2. Delete all files in C:\Users{UserName}\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
  3. Delete the folder C:\Users{UserName}\AppData\Roaming\Microsoft\VisualStudio\14.0
  4. run "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv" /setup in a command prompt as administrator
Libin M
  • 481
  • 1
  • 6
  • 16