"tolgay" wrote:

> Sometimes we got an error (Not enough storage is available to complete
>  this
>  operation) from one of our servers which on win2000 sp 4 iis5.0 (all
>  hotfix
>  installed) sql server sp4. mdac 2.81. It occures random and we could not
>  find the error reason. When the error occured the server cpu or mem or I/O
>  usage is normal and I try to find out from internet and some says check
>  the
>  mdac verision registery size or oracle etc. they do not indicate our
>  problem.  we use adodb connection to connect sql server and all of them
>  close after the proccess also all recordset are close and set nothing. The
>  server transaction is kind of high but there are several indexes so it not
>  seems a problem there. When IIS restarts the problem solves but all users
>  sesions are closed. Have you ever met the error before or what can be
>  problem. Any advice would be helpful
>
>  There is nothing in to event log even a warning also temp db size quite
> large and the db transaction log is about 2 gbyte and %75 is free and there
>  is nothing also in sql server logs.
>
>
>
>

"tolgay" <t***@tgul.com> wrote in message
news:eMnkvGLrGHA.3380@TK2MSFTNGP04.phx.gbl...
> Sometimes we got an error (Not enough storage is available to complete
>  this
>  operation) from one of our servers which on win2000 sp 4 iis5.0 (all
>  hotfix
>  installed) sql server sp4. mdac 2.81. It occures random and we could not
>  find the error reason. When the error occured the server cpu or mem or
I/O
>  usage is normal and I try to find out from internet and some says check
>  the
>  mdac verision registery size or oracle etc. they do not indicate our
>  problem.  we use adodb connection to connect sql server and all of them
>  close after the proccess also all recordset are close and set nothing.
The
>  server transaction is kind of high but there are several indexes so it
not
>  seems a problem there. When IIS restarts the problem solves but all users
>  sesions are closed. Have you ever met the error before or what can be
>  problem. Any advice would be helpful
>
>  There is nothing in to event log even a warning also temp db size quite
> large and the db transaction log is about 2 gbyte and %75 is free and
there
>  is nothing also in sql server logs.
>
>
>

"tolgay" <t***@tgul.com> wrote in message
news:Ooro$iMrGHA.3680@TK2MSFTNGP02.phx.gbl...
> We use asp and asp.net in the same site and there are several servers work
> iis and sql together without any problem but as I as mentioned the server
> web traffic is higher than other. I aslo find an error in event viewer
> which
> is bellow and found some articles. We don't use any antivirus system on
> the
> server.
>
> Error: File //global.asa Line XX Out of memory. Unable to allocate
> required
> memory.. For additional information specific to this message please visit
> the Microsoft Online Support site located at
>
> Thanks,
>
>
> "tolgay" <t***@tgul.com> wrote in message
> news:eMnkvGLrGHA.3380@TK2MSFTNGP04.phx.gbl...
>> Sometimes we got an error (Not enough storage is available to complete
>>  this
>>  operation) from one of our servers which on win2000 sp 4 iis5.0 (all
>>  hotfix
>>  installed) sql server sp4. mdac 2.81. It occures random and we could not
>>  find the error reason. When the error occured the server cpu or mem or
> I/O
>>  usage is normal and I try to find out from internet and some says check
>>  the
>>  mdac verision registery size or oracle etc. they do not indicate our
>>  problem.  we use adodb connection to connect sql server and all of them
>>  close after the proccess also all recordset are close and set nothing.
> The
>>  server transaction is kind of high but there are several indexes so it
> not
>>  seems a problem there. When IIS restarts the problem solves but all
>> users
>>  sesions are closed. Have you ever met the error before or what can be
>>  problem. Any advice would be helpful
>>
>>  There is nothing in to event log even a warning also temp db size quite
>> large and the db transaction log is about 2 gbyte and %75 is free and
> there
>>  is nothing also in sql server logs.
>>
>>
>>
>
>