oldmangeorge
Programmer
Hello everyone.
We have a very large enterprise class application, written in VB6 and (as you can imagine) using any number of 3rd party components.
The application is usually deployed on an "application server", and accessed by users via Terminal Server. We do not have stringent requirements, and our customers are using Windows Server 2003, 2003 R2, and 2008.
Lately we have encountered a very strange problem that we initially thought to be application related. Extensive testing revealed... well I am not sure what it revealed... here is the scenario:
-- Application installed on "application server" (Windows Server 2003 R2)
-- Application is correctly installed and can be executed successfully on the "application server"
-- Application is accessed via RDP (most users have RDP client 6.0.6000). There is no load balancing involved: we KNOW that all users are accessing the application using the very same terminal server.
-- Workstation A and Workstation B are in the same physical office and on the same network. For all purposes, the workstations are identical.
-- User XYZ (Windows account XYZ) access the application from workstation A - Windows XP SP3 with RDP client 6.0.6000. The application works flawlessly.
-- User XYZ (Windows account XYZ) access the application from workstation B - Windows XP SP3 with RDP client 6.0.6000. The application crashes when executing a number of functions and/or when attempting to display certain forms.
Crash, in this case, is defined as: application suddenly disappearing from desktop. Our error trapping routines cannot be / are not invoked. The VB6 built in error trapping is not invoked. There is no entry in Windows event log.
In few words: a number of users experience crashes when working with the application BUT ONLY if working with CERTAIN workstations.
Given my understanding of Terminal Server and RDP... how is this even possible? How would I go about "debugging" this issue?
Thanks so much in advance for any help and for your suggestions.
We have a very large enterprise class application, written in VB6 and (as you can imagine) using any number of 3rd party components.
The application is usually deployed on an "application server", and accessed by users via Terminal Server. We do not have stringent requirements, and our customers are using Windows Server 2003, 2003 R2, and 2008.
Lately we have encountered a very strange problem that we initially thought to be application related. Extensive testing revealed... well I am not sure what it revealed... here is the scenario:
-- Application installed on "application server" (Windows Server 2003 R2)
-- Application is correctly installed and can be executed successfully on the "application server"
-- Application is accessed via RDP (most users have RDP client 6.0.6000). There is no load balancing involved: we KNOW that all users are accessing the application using the very same terminal server.
-- Workstation A and Workstation B are in the same physical office and on the same network. For all purposes, the workstations are identical.
-- User XYZ (Windows account XYZ) access the application from workstation A - Windows XP SP3 with RDP client 6.0.6000. The application works flawlessly.
-- User XYZ (Windows account XYZ) access the application from workstation B - Windows XP SP3 with RDP client 6.0.6000. The application crashes when executing a number of functions and/or when attempting to display certain forms.
Crash, in this case, is defined as: application suddenly disappearing from desktop. Our error trapping routines cannot be / are not invoked. The VB6 built in error trapping is not invoked. There is no entry in Windows event log.
In few words: a number of users experience crashes when working with the application BUT ONLY if working with CERTAIN workstations.
Given my understanding of Terminal Server and RDP... how is this even possible? How would I go about "debugging" this issue?
Thanks so much in advance for any help and for your suggestions.