RDM stability problems after upgrading from RDM 10 to 12
Disabled
Hi folks
I already posted a concern with SQL deadlocks when idle. But it's not the only concern after upgrading from RDM 10 to 12.5.3.
Various users (max 25) on 6 different Terminalservers (Server 2008 R2, physical and virtual) report errors, crashes and hangs every few hours they did not have with version 10.
One is Error creating window handle:
Win32Exception - Error creating window handle.
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Timer.TimerNativeWindow.EnsureHandle()
at System.Windows.Forms.Timer.TimerNativeWindow.StartTimer(Int32 interval)
at System.Windows.Forms.Timer.set_Enabled(Boolean value)
at System.Windows.Forms.Timer.Start()
at Devolutions.RemoteDesktopManager.Managers.ThreadManager.Push(Action action, Int32 delay)
at Devolutions.RemoteDesktopManager.Managers.ApplicationManager.Exit(Boolean saveOptions)
at Devolutions.RemoteDesktopManager.Managers.LogManager.c49ec70c34ae4dc097a6c814c17c3e79e(Object c19f185fd70cefc696ba148af1c4faf54, ThreadExceptionEventArgs c84494660d2f38a3af31b5922482c6286)
at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
at System.Windows.Forms.Timer.TimerNativeWindow.OnThreadException(Exception e)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at Devolutions.RemoteDesktopManager.Program.Main(String[] args)
Another is Parameter is not valid: Argument exception (Sorry, no details.) While this is happening, the navigation pane is empty (crossed with thin red lines). We then have to close RDM and start again.
Further users are reporting that sometimes RDM hangs when logging off an embedded RDP Session. This happened before but was fixed at a point in RDM 10. Now it's back.
I just heard from a colleague that 1-2 times a week RDM hangs (Not responding) so he has to kill the process. Then the Visual Studio Just-In-Time Debugger appears. An unhandled Microsoft .NET Framework exception occurred in RemoteDesktopManager64.exe [18532].
We already tried to delete the user's Devolution folder in AppData (Roaming, redirected to home folder). We also made an antivirus exception and "trusted process" entry. SQL availability group is stable. But still RDM does not behave. Other software running on these Terminal Servers don't appear to have any problems.
Is there any "big picture" you see in this? Thanks for your help
All Comments (6)
Hello Daniel,
What happen after you get the first error about the window handle? Do you need to close RDM? It seems that your Terminal Server is unable to allocate more Window handle but I have no explanation why. Have you changed the auto refresh like we mentioned?
Regards
David Hervieux
Disabled
Error creating window handle: My colleagues report that RDM closes itself when confirming the error message. Afterwards sometimes the navigation panel has disappeared and they have to delete the .lyt file and restart RDM again.
I may have missed your counsel regarding auto refresh. Where did you mention it? And what did you recommend? (Sorry for that.)
Another report from my colleagues: Sometimes the Dashboard is behaving in a strange way. For example: The tiles under Administration disappear and reappear again. (One after another. Sometimes slow, sometimes fast.) That's no big deal but I mention it anyway.
Daniel
I think it was in a email reply about the deadlock. You can go in File->Data Sources and change the Auto refresh to maybe 60 secondes.
Regards
David Hervieux
Disabled
Dear David
Thanks for your answer and sorry for the delay.
We changed auto-refresh to 120s. The problems now don't appear that often. But they still appear.
Is it true, that all application data is saved under %AppData%\Devolutions\RemoteDesktopManager if the software is installed on a terminal server? This would explain our RDM behaviour. Our %APPDATA% Folder is redirected to a network location. So the %APPDATA% folder is not available locally. This is bad because our network location is in another domain behind a firewall. So every time a refresh occurs (or other communication to the offline.mcdf2 file happens) all this happens on this network location. I think this decreases performance so much that RDM gets unstable.
Is there any possibility to force RDM to save the cache-file under %localappdata% even on terminal servers?
Thanks
Daniel
Hello,
The setting we have would store the offline cache in the application folder, which isnt a good idea in your case.
The only solution would be to use the portable (XCOPY) deployment model so all of the local data is stored in another folder.
Could you read Portable (USB) and give it a try?
Best regards,
Maurice
Disabled
Dear Maurice
We are using the portable installation of RDM 12.6.6 for quite a while now. The RDM configuration directory is set to %LOCALAPPDATA%\RDM. Like this there are no errors, no not-responding windows, it is just working, even with Auto-refresh set to 15.
Meanwhile our network and storage configuration has been improved as well. So we are able to use the "original" installation as well without errors. The problem here is that the slightest network congestion or problem with filer performance results in RDM hanging or throwing errors. So we keep using the portable variant.
Thank you very much for your help!
Daniel