Re: MSDE does not react any more

From: Wayne Snyder (wayne.nospam.snyder_at_mariner-usa.com)
Date: 02/16/05 

Date: Wed, 16 Feb 2005 08:45:26 -0500

If it never hangs up except when Exchange is running, then you have your
answer... Both are big memory users, and the error is a memory type
error...I have successfully run SQL Enterprise and Exchange server on a
single box while teaching a SQL Class with no problem other than reduced
performance, but perhaps I had more memory on the box than you have. 

-- 
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Frank Esser" <Mistral@nurfuerspam.de> wrote in message 
news:%23zJS0YBFFHA.2156@TK2MSFTNGP10.phx.gbl...
> 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
>

Relevant Pages

  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • RE: The store.exe process is allocating more memory than usual.
    ... Welcome to SBS nesgroup. ... I understand that after install SBS SP1, your SBS got memory allocates ... It is an expected error after apply the Exchange ... For the Small Business Server 2003, Microsoft has release a specific update ...
    (microsoft.public.windows.server.sbs)
  • Re: FTS Performance in SQL 2005
    ... I don't think you have left enough memory for the OS and MSSearch. ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ...
    (microsoft.public.sqlserver.fulltext)
  • RE: Insufficient memory Available
    ... Insufficient memory available. ... within the scope of SQL Server. ... "MemToLeave" area. ...
    (microsoft.public.sqlserver.server)
  • RE: server problems
    ... This newsgroup only focuses on SBS technical issues. ... >Thread-Topic: server problems ... >> web proxy service or SQL Server will normally use large memory. ...
    (microsoft.public.windows.server.sbs)