Hello Everyone,
We have an application nearly a year in production. Recently, we have
deployed it to a Terminal Services farm for some of our users. For the most
part, everything is running fine; however every once in a while an odd error
occurs. We have not been able to replicate these issues on our local
workstations, either production mode or in debug mode.
When the error occurs, the application exits out and the user must restart
the app. Since we don't capture state data up until the crash occurs, this
is the desired activity. Once the user restarts the application, they do
not encounter the issue performing the same actions.
The issues do not occur all that often, perhaps once or twice a day for only
one or two users.
This is primarily a data entry based application connecting to a SQL server.
There is some use of reflection but that is really as extravegant as we get.
Since the issues only occur on the terminal servers, we were hoping that we
haven't accounted for some compatibility issue. The application is
installed locally on each terminal server, all sessions on a server run the
exe from the same directory.
Please flood me with suggestions on how to resolve the issue.
VB2005, XP/W2K3 TS
Thanks.
