1

Closed

Errors with wall-e

description

On loading of the new wall-e release of VSLab, a dialog that says "Error loading the Code Window context menu item" appears. After pressing the "OK" button on the dialog, Visual Studio loads, but the below errors occur in the F# interactive window.
 
Microsoft F# Interactive, (c) Microsoft Corporation, All Rights Reserved
F# Version 1.9.6.16, compiling for .NET Framework Version v2.0.50727
 
Please send bug reports to fsbugs@microsoft.com For help type #help;;
 
 
val ___VS_PID : int = 8872
 

 
--> Added 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies' to library include path
 

--> Referenced 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies\EnvDTE.dll'
 
 
--> Referenced 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies\EnvDTE80.dll'
 
 
--> Referenced 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies\EnvDTE90.dll'
 
 
--> Referenced 'C:\Program Files (x86)\University of Pisa\VSLab\vslabfsicore.dll'
 
Binding session to 'C:\Program Files (x86)\University of Pisa\VSLab\VSLabFSICore.dll'...
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Closed Feb 13, 2011 at 4:19 PM by cisterni
Closed because of VS2010 new implementation

comments

cisterni wrote Jun 20, 2009 at 10:26 AM

This is an issue with the COM server. Sometimes COM interop does not react in a timely fashion. Usually this is when the workload on the machine is high. Check the state of the machine and let me know. We are still trying to find a better fix other than retry...

v_atta wrote Jun 25, 2009 at 10:44 AM

Sorry .. but this problem is general .. I try more platform and not working wall-e nowhere .. why ?? please help or fix it or do something .. thx :)

wrote Feb 13, 2011 at 4:19 PM

wrote Feb 13, 2013 at 11:48 PM

wrote May 16, 2013 at 4:19 AM