MSDE does not react any more
From: Frank Esser (Mistral_at_nurfuerspam.de)
Date: 02/16/05
- Next message: Carlos Selonke: "RE: SPN and SQL Server with multiple instance names"
- Previous message: David Portas: "Re: trigger to update count field - Request for criticism"
- Next in thread: Wayne Snyder: "Re: MSDE does not react any more"
- Reply: Wayne Snyder: "Re: MSDE does not react any more"
- Reply: Michael C#: "Re: MSDE does not react any more"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Feb 2005 11:56:41 +0100
Hi,
we have got an application that captures technical measurement data in a
local MSDE database. The system runs at many customers without any
performance problem.
Now we had an installation on a PC where also the Exchange Server runs and
from time to time our MSDE hangs up. That means it does not react any more.
We can even not open the OSQL access.
Sometimes, when I stop and restart the server service by service manager
then it refuses to start. In the event log I can see 3 errors, the first one
is:
19011: SiperSocket info: ConnectionListen(SharedMemory(LPC)): Error 5
The other two errors are 17... errors.
Can anybody imagine what goes wrong? Is it a sideeffect of the Exchange
Server or other applications running on the same machine? What can I do to
find the error and what can I do to fix the problem?
Thanks for sharing your know-how with a non-expert !
Best regards
Frank
- Next message: Carlos Selonke: "RE: SPN and SQL Server with multiple instance names"
- Previous message: David Portas: "Re: trigger to update count field - Request for criticism"
- Next in thread: Wayne Snyder: "Re: MSDE does not react any more"
- Reply: Wayne Snyder: "Re: MSDE does not react any more"
- Reply: Michael C#: "Re: MSDE does not react any more"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|