Cannot execute .NET code on Terminal Services 1

[wolfie78uk]

Hi,

I am trying to deploy a .NET Windows Forms App on a Terminal Server. The App does not write to the registry although, because it is a test harness for a web service, it does make a connection to a web service.

Unfortunately, the application will not run for a non-administrator user. It doesn't appear to even get as far as my own form load code - it appears to start but then nothing happens.

Looking at the task manager, Dr Watson kicks in almost immediately when the .NET app is started - Dr Watson reports an Ordinal 71 error - and ends the process.

The application will run fine if the user is an administrator but as this is a live server, I can't make all end users administrators!!

Has anybody got any ideas?

Thanks,

Simon

 

[ThatRickGuy]

try adding an event logger at the entry point of the app, that way you sohuld be able to tell if the app is loading and hitting an error. If not, then I would say we'll have to look at the install. Is the app installed locally? Is TS fully patched? Are you using .Net 1.0 or 1.1? When the app was installed was the "Just Me/Evereyone" switch set correctly?

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[wolfie78uk]

Hi Rick,

Thanks for your reply. I added an event log as early as possible in the code (although the call to the base class constructor has to come first) :

'Windows Form App :

Public Sub New()
MyBase.New()

Dim EventLog1 As New EventLog
If Not EventLog.SourceExists("JSTestApp") Then
EventLog.CreateEventSource("JSTestApp",Application")
End If
EventLog1.Source = "JSTestApp"
EventLog1.WriteEntry("The base constructor has been called!")

...
End Sub

I ran this on my local machine to check that it logged correctly and it did. However, any attempt to run it on the Terminal Server resulted in nothing being logged to the event log.

The Terminal Server is definately running Framework 1.1 (although not Service Pack 1).

When I installed the App, I set the "Just Me/Everyone" switch to "Everyone". It was installed as administrator.

I don't know if the server is fully patched....the guy I need to ask has gone home! (I would imagine so though given the importance of its function)

The actual problem that I am trying to solve is an old VB6 app using an Interop Module written in VB.NET - when it came to load the interop module I got "Error 70 : access denied" so I tried to run this test app instead. My logic is that if I can solve the problem with the test app (which is easier to debug), my problems with the interop should also be solved.

Interestingly I tried running a .NET "Hello World" console app and, after opening the console window, that application also aborted.

Thanks,

Simon

 

[ThatRickGuy]

Patch the framework first. There is a known issue with 1.0 and unpatched 1.1 that non-admin accounts can not run .Net apps on Win 2k TS (sp4).

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[wolfie78uk]

Cheers Rick. That solved it.

 

[ThatRickGuy]

On a side note, even if you are runing frame work v1.0, and have it fully patched, the problem will continue untill you install and patch framework v1.1.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.