Prev: Fail to run VB application on Terminal Server
Next: Application crashes...
From: sprit on 4 Jan 2007 12:21
I am using version 5.1.2600.2180 of mstscax.dll in a C# application. In this
application I am reusing the instance of AxMSTSCLib.AxMsRdpClient over and
over to access several different accounts on one terminal server.

Each time I make a connection, there seems to be one handle being leaked.
This continues until there have been a few thousand connection mades. At
this point the application is using several thousand handles and a variety of
exceptions are thrown including System.InvalidOperationException and
System.OutOfMemoryException.

Are there any known handle leak problems? Are there any properties that
need to be cleared out when I disconnect the client?

Thanks.
From: Vera Noest [MVP] on 4 Jan 2007 16:02
Disclaimer: I'm not a developer, so I could be totally off track
here, but check if this applies:

905888 - A memory leak occurs in the Wmiprvse.exe process when a
program calls an instance of the "CWin32
_TerminalService::ExecQuery" function in Windows Server 2003
http://support.microsoft.com/?kbid=905888
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?c3ByaXQ=?= <sprit(a)discussions.microsoft.com> wrote on 04
jan 2007 in microsoft.public.windows.terminal_services:

> I am using version 5.1.2600.2180 of mstscax.dll in a C#
> application. In this application I am reusing the instance of
> AxMSTSCLib.AxMsRdpClient over and over to access several
> different accounts on one terminal server.
>
> Each time I make a connection, there seems to be one handle
> being leaked. This continues until there have been a few
> thousand connection mades. At this point the application is
> using several thousand handles and a variety of exceptions are
> thrown including System.InvalidOperationException and
> System.OutOfMemoryException.
>
> Are there any known handle leak problems? Are there any
> properties that need to be cleared out when I disconnect the
> client?
>
> Thanks.
From: sprit on 4 Jan 2007 16:21
Thanks for your reply. I don't think this is related. My handle leak is on
the client side. Wmiprvse.exe is on the server side.

"Vera Noest [MVP]" wrote:

> Disclaimer: I'm not a developer, so I could be totally off track
> here, but check if this applies:
>
> 905888 - A memory leak occurs in the Wmiprvse.exe process when a
> program calls an instance of the "CWin32
> _TerminalService::ExecQuery" function in Windows Server 2003
> http://support.microsoft.com/?kbid=905888
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?c3ByaXQ=?= <sprit(a)discussions.microsoft.com> wrote on 04
> jan 2007 in microsoft.public.windows.terminal_services:
>
> > I am using version 5.1.2600.2180 of mstscax.dll in a C#
> > application. In this application I am reusing the instance of
> > AxMSTSCLib.AxMsRdpClient over and over to access several
> > different accounts on one terminal server.
> >
> > Each time I make a connection, there seems to be one handle
> > being leaked. This continues until there have been a few
> > thousand connection mades. At this point the application is
> > using several thousand handles and a variety of exceptions are
> > thrown including System.InvalidOperationException and
> > System.OutOfMemoryException.
> >
> > Are there any known handle leak problems? Are there any
> > properties that need to be cleared out when I disconnect the
> > client?
> >
> > Thanks.
>
 | 
Pages: 1
Prev: Fail to run VB application on Terminal Server
Next: Application crashes...