I have been updating the software every month on average to try to remove the constant crash that occurs when you use embedded RDP connections - you disconnect or get disconnected from the rdp server, then try to reconnect to the same rdp machine - and this crashes.
I have tried using all of the available versions of RDP for connectivity within the settings - none of these seem to fix the issue - any other suggestions.
--
Second to this is a suddenly getting the following crash occurring seemingly randomly on v 9.4.13.0 - 32Bit.
System.IO.IOException: The handle is invalid.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.BeginWriteCore(Byte[] bytes, Int32 offset, Int32 numBytes, AsyncCallback userCallback, Object stateObject)
at System.IO.FileStream.FlushWrite(Boolean calledFromFinalizer)
at System.IO.FileStream.Dispose(Boolean disposing)
at System.IO.FileStream.Finalize()
I am not working in my RDM window when this occurs - and there has either been no connection or no actual usage when it occurs.
Regards,
Sam
Could you try the latest beta release. It's 9.9.4
David Hervieux
This is a wonderful example as to why people don't report bugs.
I would suggest that when you use a blanket response of 'try using the beta' you will lose customers.
One simple thing - Why should I use the beta - what has this got to do with my issues - why would I use this beta in my production environment?
edited by essaym on 9/25/2014
It was a simple question. The beta contains the most up to date version. That where we have the latest fixes.
David Hervieux
I understand that David - as in my original I have been updating the software every month on average now with the 'latest fixes' for a couple of years.
What specifically about this beta that you want me to install has a fix to do with my issue or can we skip to the part where we actually start to do diagnostics?
So you are aware - with the first error that has always existed - I am able to replicate this by doing the following: RDP with an embedded window onto a Citrix/Terminal Server Session, wait for the user login to time out, then attempt to connect to the session again.
The problem that we have in the stack trace is that we don't have any entry point to handle the error. What I mean is that it's in the .NET Framework. I have a potential fix (no guarantee) and it will be in RDM 10.0.1.0. I hope to release it tomorrow. I will let you know as soon as it released.
David Hervieux
I can see myself that all you need to do is handle the error that has come up in the stack trace - This is great, as it has only started happening from the version I am on.
My main concern is about the constant crashes from embedded RDP sessions that seems to have made no progress over the years of updates - how can we get verbose diagnostics to be able to provide you the information you need to handle the error on this?
Hi,
I have updated RDM this morning and we have a potential fix for your crash. Let me know if it still happen.
David Hervieux
Unfortunately the latest update did not fix the issue with RDM crashing when using embedded mode and trying reconnect to a rdp server.
How can I get more verbose debugging for you to fix this?
'An unhandled Microsoft .NET Framework exception occurred in RemoteDesktopManager.exe [139200].'
When I attempt to launch New instance of Microsoft Visual Studio 2010 I get invalid license and requires reinstall - do you have any other ways that you would like me to get information to you?
If it makes any difference - if I restart any server and reconnect the crash does not occur.
Unfortunately that's the problem. In this version I have a full error handler enabled and it does not seems to use it. This means that the crash is in native code and not in our code. I suspect that it happens in the Microsoft ActiveX. I know that this could happen if you enable the RDP plugin in the session (thinprint for example). Do you use any of these extension?
Could you double check for the logs perhaps we have something different with this version?
David Hervieux
We did a test on one of our machines for thinprint and screwdrivers - but this environment has nothing to do with anywhere that RDM touches.
Is there a registry tree thatI can list if there are any plugins appropriate?
It's located in Software\Microsoft\Terminal Server Client\Default | Addins
David Hervieux
There are no keys listed under default | Addins.
Ok. However just be sure we could try to disable the add-ins in the RDP entry. What about the log?
David Hervieux
I have checked HKCU (as previously I checked just HKLM) and we are using one plug in.
C:\Program Files\Citrix\MetaFrame Password Manager\DVC.dll
The log is clear, and I have disabled loading plug-ins within the test sessions - I will let you know of any changes.
Hi David,
This seems to be seriously reducing any crashing - is there a way to do a change-all on RDP sessions (around 160) without going into them all individually?
I will add a global setting for that. This will be in the next release.
David Hervieux
Thanks David - I am on vacation for two weeks, so I'll update when I return.
Hi David,
I have installed 10.0.4 and changed the setting over to false for embedded sessions to use extentions - this seems to have fixed the issue.
I will post if there are any changes to this.
Regards,
Sam
Do you mean all the web sessions?
David Hervieux
This is for Embedded RDP Sessions crashing.
Hi Sam,
Are you running RDM Agent on the destination machine?
Regards,
Stéfane Lavergne
No - RDM Agents do not run on any of the RDP destinations