Red X instead of Tree View

Hello,

That problem occurs once in a while and is indeed related to the layout, but its highly unusual that in his case it comes and goes.

Please have him open %LOCALAPPDATA%\Devolutions\RemoteDesktopManager\ and delete the *.lyt files that are present.

Best regards,

My colleague deleted the *.lyt files. But now it happend again. He then closed RDM and opened it again. There was no red cross but no content in the tree view either. With Ctrl+F5 and reopening the treeview will eventually come back.

He's not the only one with that problem. I can confirm the red X problem. It happened once. RDM was openend. I did not do anything with it and suddenly a small red X appeared above the tree view. (Unfortunately I did not make a screenshot of it.)

Do you have any clue why this is happening? What are the mechanics behind this?

Daniel

Could you verify if you get anything in the application log right after the crash?

Regards

Hi David

I've just encountered again the red X. But this time the ribbon bar was gone, not the navigation pane.

In the windows application log there is no error or warning. Everything's fine.

In the RDM Log I can only see these entries. (But I'm not sure if it happened exactly then because I was not in front of my pc when it happened.)

[16.03.2016 15:15:40 - 11.1.0.0 64-bit]ERROR 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()

[16.03.2016 15:15:40]ERROR SILENT 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()

Seems like an issue with our third party UI component we use. I will try to update it for the next version.