Re: vb6 com+ out of memory issue

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"Out of memory" is a generic error with the plain text meaning "somethong
went wrong and we aren't going to give you any details that might help you".

First off, there were a couple of bugs in XP and W2K3 in iner-system COM+
marshalling that provoked this sort of problem when using complex data
structures. Ensure you have XP SP2 and W2K3 SP1 as they resolved many of
them. IIRC, there was also an issue that requires a post-W2K3 SP1 fix (it
was SP1 that broke the code). Do a KB search to find it. By the sound of it
though, you may be running W2K. AFAIK, the bugs have not been resolved in a
W2K service pack. Once you locate the W2K3 KB description, you will need to
contact your local MS office to obtain a W2K version of the fix (this may
involve payment of a fee).

<javigm@xxxxxxxxx> wrote in message
news:1178284987.631000.318340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Visual Basic 6
Microsoft Active Data Objects 2.8 version 2.82.1830.0
Component Services version 2001.12.4720.1830


Our application follows the standard Windows DNA architecture with
ActiveX dlls and Windows forms deployed on a client tier and activeX
dlls hosted in COM+ on remote server machines, all code is VB6. Our
client is experiencing out of memory errors on their production and
supporting environments which we have been unable to reproduce in any
of the environments within our company.

The out of memory error appears to be raised outside of our code when
the COM+ component (server side) has completed its work and is
attempting to return the results to the calling component (on the
client side). We have error logging within every method in our code
and the server component does not log any error, after adding tracing
to the code we could see that the server dll exits sucessfully and the
error is reported by the line of code in the client that calls the
server component.

The error does not happen constantly and works fine for a while but
once it has been raised it is continually reported on every subsequent
call to the same method until the application server is rebooted.
When the error occurrs different methods on the same server component
can still be called sucessfully

The error reported is "Out of Memory - Run time error 7". The error
is reported by the client callee code and is not logged on the server
machine. Our code has error handlers in every method and these are
logged to the application event log so it appears as though the error
is being raised when trying to return from the method via COM+ to the
calling code.

Rebooting the application servers clears the error for a number of
hours.

Having the COM+ dlls compiled with Unattended Execution and Retained
In Memory options selected, this has no affect on the issue.



.

Relevant Pages

  • Re: Memory usage and large number of pages
    ... The problem is the overhead of compiling these pages is huge - and because ... have also found that for each file that is compiled the memory increases. ... >> directory on the web server. ... >> returns the result of this page back to the client. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Named shared memory without synchronization
    ... memory address with a single machine instruction. ... Again, if I assume an x86/x64 architecture I think i can get away with this, ... when running on a 4-way server under heavy load. ... Server runs client. ...
    (microsoft.public.vc.language)
  • Possible bug in sockets
    ... Just point the ip address of the client at the server ... The client connects 200 sockets, sends some data with each continously, ... in this scenario memory increases forever. ...
    (microsoft.public.dotnet.framework)
  • RE: Exchange 2003 and timeout errors on XP machines
    ... After replacing 1 client computer's network cable, ... Are you able to open OWA to access the e-mails on the client or server? ... Store.exe will take as much memory as possible to provide better service ... Microsoft engineers can only focus on one issue per thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: Bi-directional ServerObj <--> ClientObj with SAO on same computer
    ... reach the listening client. ... remoting server component is hosted by a WinForm application, ...
    (microsoft.public.dotnet.framework.remoting)