When you log on to a Terminal server and run a Microsoft
.NET Framework-based program or Microsoft Visual Studio .NET, you experience
one or more of the following symptoms:
- When you create a new Windows Application project in Visual
Studio .NET, and then you try to edit it by using the design editor, you
receive the following error message:
Microsoft Development Environment
There is no editor available for 'C:\Documents and
Settings\TestUser\My Documents\Visual Studio
Projects\WindowsApplication2\Form1.vb'.
Make sure the application for
the file type (.vb) is installed.
- When you open a project, and then you quit Visual Studio
.NET, you receive the following error message:
The
instruction at "0x791bad3a" referenced memory at :0x00000050". The memory could
not be "read".
Click on OK to terminate the program
Click on
CANCEL to debug the program
If you click Cancel, you
receive the following error message:Microsoft Visual
Studio Debugger has encountered a problem and needs to close. We are sorry for
the inconvenience.
- When you try to run a .NET Framework-based managed program,
you receive one of or both of the following error messages:
ConsoleApplication1.exe - Fatal error
CLR error: 80070002.
The program will now
terminate.
-and-ConsoleApplication1.exe - Application
Error
The instruction at "0x791bad3a" referenced memory at
"0x00000050". The memory could not be "read".
Click on OK to terminate
the program
Click on CANCEL to debug the program
If you click
Cancel, you receive the following error message:Microsoft Visual Studio Debugger has encountered a problem and
needs to close. We are sorry for the inconvenience.
This problem occurs if all the following are true:
- You log on to the Terminal server as a limited user (a user
without administrator rights).
-and- - The Terminal server is running Microsoft Windows 2000
Service Pack 4 (SP4) and has the .NET Framework 1.0 Service Pack 2 (SP2) or
earlier installed.
-and- - You have not installed the .NET Framework 1.1 or later on
the Terminal server.
To work around this problem, install the Microsoft .NET
Framework 1.1 on the Windows 2000 SP4-based Terminal server. For additional
information about how to obtain the .NET Framework 1.1, visit the following
Microsoft Web site:
Microsoft has
confirmed that this is a problem in Microsoft Windows 2000 Service Pack 4.