Memory problems

Hi
I've been having a problem with SQL Server for the last couple of
weeks. I've been unable to resolve it. Or, indeed, work out exactly
what the problem is.
We're running MS SQL Server 2000, Service Pack 3; it's running on
Windows Server 2003, on a Dell PowerEdge 2500 with 2 gigs of RAM.
There are two problems that we're getting; I'm assuming they're
related, but I've not got enough SQL Server experience to be sure.
The first is that, from time to time, we'll stop being able to access
the server - in Enterprise Manager, when we open the server, we get an
SSL error (something about SECDoClientHandShake()).
The second is a CryptoAPI error - I've not been able to get the
details for this, because it's only happening when our developer
accesses the machine remotely; we can still use the server locally
with no problems.
The information I've found online says that there was a known problem
with SQL Server 2000 and Certificate Server, which caused a similar
problem, but that that problem was resolved in Service Pack 1. I've
tried what I can - we've doubled the memory from 1 gig to 2, and I've
tweaked the options as much as I dare - but nothing seems to have
helped.
If anyone has any suggestions as to what might be causing this, I'd be
very grateful to hear them.
Finally, we're also, from time to time, getting errors in SQL Server's
log along the lines of:
2003-11-13 09:15:24.48 spid53 WARNING: Failed to reserve contiguous
memory of Size= 65536.
2003-11-13 09:15:24.48 spid53 Query Memory Manager: Grants=0
Waiting=0 Maximum=103895 Available=103895
2003-11-13 09:15:24.48 spid53 Procedure Cache: TotalProcs=217
TotalPages=778 InUsePages=449
2003-11-13 09:15:24.48 spid53 Global Memory Objects: Resource=925
Locks=18 ...
2003-11-13 09:15:24.48 spid53 Dynamic Memory Manager: Stolen=1156 OS
Reserved=992 ...
2003-11-13 09:15:24.48 spid53 Buffer Distribution: Stolen=378
Free=10 Procedures=778...
2003-11-13 09:15:24.48 spid53 Buffer Counts: Commited=1810
Target=139175 Hashed=644...
though it doesn't seem to be happening at the same time as we're
getting the problems with accessing the database.
If there's any information I've missed, please let me know. I really
would appreciate any help on this.
AndrewAndrew,
KBID=818095
PH
AndrewS@.mortdieu.demon.co.uk (andrewsi) wrote in message news:<29ba971a.0311130527.7f9e7dae@.posting.google.com>...
> Hi
> I've been having a problem with SQL Server for the last couple of
> weeks. I've been unable to resolve it. Or, indeed, work out exactly
> what the problem is.
> We're running MS SQL Server 2000, Service Pack 3; it's running on
> Windows Server 2003, on a Dell PowerEdge 2500 with 2 gigs of RAM.
> There are two problems that we're getting; I'm assuming they're
> related, but I've not got enough SQL Server experience to be sure.
> The first is that, from time to time, we'll stop being able to access
> the server - in Enterprise Manager, when we open the server, we get an
> SSL error (something about SECDoClientHandShake()).
> The second is a CryptoAPI error - I've not been able to get the
> details for this, because it's only happening when our developer
> accesses the machine remotely; we can still use the server locally
> with no problems.
>
> The information I've found online says that there was a known problem
> with SQL Server 2000 and Certificate Server, which caused a similar
> problem, but that that problem was resolved in Service Pack 1. I've
> tried what I can - we've doubled the memory from 1 gig to 2, and I've
> tweaked the options as much as I dare - but nothing seems to have
> helped.
> If anyone has any suggestions as to what might be causing this, I'd be
> very grateful to hear them.
> Finally, we're also, from time to time, getting errors in SQL Server's
> log along the lines of:
> 2003-11-13 09:15:24.48 spid53 WARNING: Failed to reserve contiguous
> memory of Size= 65536.
> 2003-11-13 09:15:24.48 spid53 Query Memory Manager: Grants=0
> Waiting=0 Maximum=103895 Available=103895
> 2003-11-13 09:15:24.48 spid53 Procedure Cache: TotalProcs=217
> TotalPages=778 InUsePages=449
> 2003-11-13 09:15:24.48 spid53 Global Memory Objects: Resource=925
> Locks=18 ...
> 2003-11-13 09:15:24.48 spid53 Dynamic Memory Manager: Stolen=1156 OS
> Reserved=992 ...
> 2003-11-13 09:15:24.48 spid53 Buffer Distribution: Stolen=378
> Free=10 Procedures=778...
> 2003-11-13 09:15:24.48 spid53 Buffer Counts: Commited=1810
> Target=139175 Hashed=644...
> though it doesn't seem to be happening at the same time as we're
> getting the problems with accessing the database.
> If there's any information I've missed, please let me know. I really
> would appreciate any help on this.
>
> Andrew