.Net application running in Windows 2000 Terminal Server

[Chung Ley]

Hi

I am having problem running an .net application on a Windows2000 Terminal Server. The application seems to work fine on user's desktop

The issues that I have with running the application on the Terminal Server are
1. When exiting the application, I got the following error dialog box
Title: .Net-BroadcastEventWindow.1.0.5000.0.5:MyExecutable.exe - Application Erro
Message: The instruction at "0x77f8910e" referenced memory at "0x00000324". The memory could not be "read"
I seemed to read other folks had similiar problems when they have .net 1.0 framework installed instead of the .net 1.1. However, I checked and my installation is 1.1

2. I was unable to install one instance of the application and have all users on the Terminal Server to share that instance UNLESS the user is given administrative privilege. My application does not use any registry settings, so do you happen to know if .Net automatically do something of that kind. I was going to do registry compare as the last resort, but if you happen to know something, maybe you can share that with me

If you know anything about the above 2 errors, please share it with me... Thanks a million..

--Chun

[Tian Min Huang]

Hello Chung,

Thanks for your post. As I understand, you are experiencing some problems
when running a .NET application under Windows 2000 Terminal Server. Please
correct me if there is any misunderstanding. Now I'd like to share the
following information with you:

1. Based on my experience, there is a known issue in .NET Framework 1.0 on
Windows 2000 Terminal Server.

Errors Occur When You Use a .NET Framework 1.0-Based Program on a Windows
2000 Service Pack 4-Based Terminal Server
http://support.microsoft.com/default.aspx?kbid=823485

As in this case, was your program built in VS .NET 2002?

I suggest to stop Terminal Server on your WIndows 2000 box and then check
if you can reproduce the problem?

Please also check the call stack when it crashes.

2. Could you please tell me the sympton of the problem when running your
application under the user without administrative privilege?

You can use Filemon and Regmon to monitor the File/registry access of your
program:

Filemon
http://www.sysinternals.com/ntw2k/source/filemon.shtml

Regmon
http://www.sysinternals.com/ntw2k/source/regmon.shtml

I look forward to your response.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Tian Min Huang]

Hello Chung,

Thanks for your post. As I understand, you are experiencing some problems
when running a .NET application under Windows 2000 Terminal Server. Please
correct me if there is any misunderstanding. Now I'd like to share the
following information with you:

1. Based on my experience, there is a known issue in .NET Framework 1.0 on
Windows 2000 Terminal Server.

Errors Occur When You Use a .NET Framework 1.0-Based Program on a Windows
2000 Service Pack 4-Based Terminal Server
http://support.microsoft.com/default.aspx?kbid=823485

As in this case, was your program built in VS .NET 2002?

I suggest to stop Terminal Server on your WIndows 2000 box and then check
if you can reproduce the problem?

Please also check the call stack when it crashes.

2. Could you please tell me the sympton of the problem when running your
application under the user without administrative privilege?

You can use Filemon and Regmon to monitor the File/registry access of your
program:

Filemon
http://www.sysinternals.com/ntw2k/source/filemon.shtml

Regmon
http://www.sysinternals.com/ntw2k/source/regmon.shtml

I look forward to your response.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Chung Ley]

Hi,

Thanks for your response.... I am using .Net 2003, so I believed it is
using .net framework 1.0.

As for the sympton of the problem, it will take me a little more time
with getting the symtom since we are getting into another problem with
Windows Installer on the terminal server box.

Thanks... Have a nice day too.

--Chung
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!