5.8.1 Application Error when closing

Hi,

If you close the application without connecting to an RDP session, do you get the error ? Also, when you close, all your session are closed ?

I only get the error if I have opened an RDP session. If I open RDM and then close it immediately without launching an RDP session, the error does not appear.

All RDP sessions are closed when I shut down RDM. If I open RDM, launch an RDP connection to a server, then close the RDP session and then close RDM, I get the error.

I'm running MSTSC.EXE version 6.1.7600.16385 on Windows XP Professional SP3

FWIW, I'm running 5.8.1.1 beta, Win7 32-bit with the version of MSTSC.exe that comes with it, and I'm not having an issue.

Hi,

I suggest that you should try to upgrade to the latest RDP version (7.0):

http://support.microsoft.com/kb/969084

That's the version that I'm running. Even though it's called version 7.0 the file version is as shown in my earlier post.

I have the same problem.

RDP version 7

RDM Version 5.8.2

Sorry, also

OS: Windows XP SP3

Hi,

I will try to setup and Windows XP SP3 and do some test, it appear that this OS is causing the problem.

edited by dhervieux on 8/12/2010

Hi,

Can you try a small test, Open RDM, open an RDP session, close the RDP session, go in the About box and close the application. Do you get the message.

Why go in the about box, this will trigger a garbage collect.

I tried what you suggested. Open RDM, Open RDP session, Close RDP session, Open Help About, Close Help About, Close RDM.

I still get the error message.

Is this the right About box?

I'm running XP SP3 as well.

I get the same error with 5.8.2.1. The interesting thing for me is that if I just open RDM, and not click on anything, I don't get an error if I close RDM. If I open RDM, select a connection (not launch anything just highlight one of the connections), I get the same error. I am running Windows XP SP2. We can't upgrade to SP3 due to corporate policy. I am currently evaluating this software for my company as a possible solution to connection management so hopefully this won't interfere with my testing (it doesn't seem to be so far).

Hi,

@rschwer: yes it's the right aboutbox. There is another thing you can try. Close you application and open the application configuration. Change the field "ForceRDP6"value in the file to true. Let me know.

The thing I don't understand is this error is not caught by RDM, this is Windows message. There is another thing I see, maybe you can try to create an xml data source, I saw many problem with the Access driver.

CAn you verify also if you see a entry in the event viewer, maybe we will find a clue?