App blows out Terminal Server

[mlee1steph]

Hi Everyone,
We are having a problem with Win2003k server and terminal server. The admin just setup a Terminal Server and installed an app I wrote in VB.Net (Version 1.1 of the .Nte Framework). After the install is complete, if we try and start the app. The app will not load. The screen flickered a little bit. We can't seem to run anything else, and if we try and restart the server, it won't load back up. The admin waited for a good hour and nothing. So they re-installed the server and today we tried again:

Today, I had them install my .Net app then run it (without terminal sever installed) and everything worked great. They installed Terminal Server again, then my app, and tried to run again. We got the same problem. Has anyone seen this issue before with any app, or an .Net Framework 1.1 app. Thanks for any help.
Michael

 

[NortonES2]

It sounds as if the App isn't Terminal Server compatible.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[mlee1steph]

Hi NortonES2,
Is there a good article that covers the compatiable issues for Terminal Server(TS). I do have something that writes out to a file, but it never does it during startup (Only when data is saved), so this one could not have caused the problem, as it freezes at startup and displays no screens from the app.
Is there a better way to write this code to work better with TS.
Public Sub appLogger(ByVal sDesc As String, ByVal sFrom As String)
Dim FileNum As Short
try
FileNum = FreeFile
FileOpen(FileNum, VB6.GetPath & "\App.log", OpenMode.Append)
WriteLine(FileNum, sDesc, sFrom, Now)
FileClose(FileNum)
Catch ex As Exception
msgbox(ex.Message )
End Try
End Sub

Thanks again for your reply.
Michael

 

[NortonES2]

beyond my knowledge, I only know that some software companies have 2 versions of their apps, a standard version and a TS version.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[mlee1steph]

Hi Again,
We did some more testint this morning on the servers. They started out testing my app on Windows 2000 Server with Terminal Services started and it worked fine. Now, with Windows 2003, without Terminal Server running, the apps work fine. I asked the Admin to install Word, a Hello World app I wrote and reinstall the main app. With Terminal Server running on 2003 Word and the Hello World works fine. But as soon as they start my app, it locks up the server.
There are no errors in the System Logs that relate to the installtion or running of this app, so I can't give you any errors to go by. All I can say is that the server gets hosed up. Nothing will open, the Start button don't even work. we can move the Mouse around, but thats about it. If we do a hard reboot into Safe mode. We can get into the System logs, the app works in Safe mode also. But we can't uninstall any apps (I think because of safe mode). I'm not sure what else to do.
In the next few days I will be breaking down the app to see if there is a feature that's breaking Terminal Server.
BTW..... I do have ComponentOne True Grid and combos in the app. Could it be something is over writing a TS file during the install. Thanks again for any help that you all can provide.
Michael

 

[NortonES2]

Just one thought when you install the App do you place the Terminal Server into Install mode first?

Go to the command prompt and run:-

change user /install

the after you've installed the App

change user /execute



-------------------------------

If it doesn't leak oil it must be empty!!

 

[mlee1steph]

Hi NortonES2,
Thanks for the reply. The way we have been installing the program so far is to use the Add/Remove Programs feature from the control panel. Does this not put it into the install mode? Thanks
Michael

 

[EnochL]

Add/Remove Programs does place the TS into install mode...