D
Dominique Deleris
Hello,
We are facing the following problem:
We have an application, written in Delphi, which is available from an
"application server" through a shared folder. In this shared folder are
located the program executable itself, as well as all needed DLLs. From the
client workstations, the application is launched from the shared folder, and
DLLs are also downloaded as needed. Sometimes the application is launched
directly via \\server\share\app.exe, sometimes via a mapped drive X:\app.exe
(with X:\ mapped to \\server\share).
This has been working perfectly for years, using Windows NT 4.0 servers are
Windows NT 4.0 / 2000 Pro workstations.
We have now problems with XP Pro client workstations, where the application
will randomly abort without any error message (it simply disappears from the
screen). The event logs do not show any error message, and we could not get
any audit failures with the standard Windows auditing tools (Local security
policy, Local policies, Audit policy)
The only way we can reproduce it at will so far is to unplug the network
cable, or disconnect the share while in the application. Then, on next user
action (e.g. menu selection), the application will disappear...
So, we have very little information on what can possibly cause the
behaviour.
Our questions:
- Does it look like a known problem to anybody?
- Does anybody know how to identify the root cause of the problem? or how to
trace such problems in a simple manner?
Thanks in advance,
Kind regards,
And a happy new year to everybody
Dominique
We are facing the following problem:
We have an application, written in Delphi, which is available from an
"application server" through a shared folder. In this shared folder are
located the program executable itself, as well as all needed DLLs. From the
client workstations, the application is launched from the shared folder, and
DLLs are also downloaded as needed. Sometimes the application is launched
directly via \\server\share\app.exe, sometimes via a mapped drive X:\app.exe
(with X:\ mapped to \\server\share).
This has been working perfectly for years, using Windows NT 4.0 servers are
Windows NT 4.0 / 2000 Pro workstations.
We have now problems with XP Pro client workstations, where the application
will randomly abort without any error message (it simply disappears from the
screen). The event logs do not show any error message, and we could not get
any audit failures with the standard Windows auditing tools (Local security
policy, Local policies, Audit policy)
The only way we can reproduce it at will so far is to unplug the network
cable, or disconnect the share while in the application. Then, on next user
action (e.g. menu selection), the application will disappear...
So, we have very little information on what can possibly cause the
behaviour.
Our questions:
- Does it look like a known problem to anybody?
- Does anybody know how to identify the root cause of the problem? or how to
trace such problems in a simple manner?
Thanks in advance,
Kind regards,
And a happy new year to everybody
Dominique