Re: Network application closes unexpectedly
From: Ryan Hanisco (rhanisco_at_flagshipis.com)
Date: 01/03/05
- Next message: Daniel: "Re: Domain Trust between w2k und 2003 domain"
- Previous message: Ryan Hanisco: "Re: Domain Trust between w2k und 2003 domain"
- In reply to: Dominique Deleris: "Network application closes unexpectedly"
- Next in thread: Phillip Windell: "Re: Network application closes unexpectedly"
- Reply: Phillip Windell: "Re: Network application closes unexpectedly"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 3 Jan 2005 11:01:26 -0600
Dominique,
I have a few questions...
1. Are you running WINS? (I have seen this happen before; we needed WINS to
make applications on a NT4 server work reliably even with DNS working
perfectly.)
2. Are you SURE there isn't an intermittent network problem dropping
connection? Try a program like WhatsUP or ADRem (I prefer Adrem) to verify
that you have a consistent connection to the network. Maybe you have a
flaky switchport, or a ProxyARP problem... or a bad network cable.
3. Is DNS a problem? Try a line in LMHOSTS to make sure. If that fixes it,
fix your DNS.
4. Does this happen to everyone? At the same time?
5. Are you out of concurrent licenses? Or the maximum threshold set on the
share?
I know those aren't in any good order, but work your way up the OSI model.
Check the physical connections, then your network path, then your naming,
then your server, then your share, then the app..
-- Ryan Hanisco MCSE, MCDBA Flagship Integration Services "Dominique Deleris" <ddeleris@mitsa.ch> wrote in message news:%233pCqNb8EHA.1524@TK2MSFTNGP09.phx.gbl... > 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 > >
- Next message: Daniel: "Re: Domain Trust between w2k und 2003 domain"
- Previous message: Ryan Hanisco: "Re: Domain Trust between w2k und 2003 domain"
- In reply to: Dominique Deleris: "Network application closes unexpectedly"
- Next in thread: Phillip Windell: "Re: Network application closes unexpectedly"
- Reply: Phillip Windell: "Re: Network application closes unexpectedly"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|